Pre-Solved Token Pool
How the hottest domains hit 50ms solve times.
The pattern
For the hottest domains, VexSolver runs dedicated background workers that continuously solve against the target and push the resulting tokens into a bounded channel buffer. When a customer request arrives, we pop a pre-solved token from the buffer in microseconds and return it immediately. You get the token in the time it takes to acknowledge the request over TCP.
How it flows
Worker 1
solving →
Worker 2
solving →
Worker 3
solving →
Token Buffer
bounded channel
5 / 8 ready
Customer
POST /api/solve
Pop
instant
< 50ms
Fallback cascade
The pool workers use blocking sends on the buffer, so they only solve as fast as customers consume — there is no wasted proxy quota on tokens no one will use. If the pool empties under load, requests transparently fall through to:
- Pool hit — ~50ms (hot path)
- Replay — 2-4 seconds (template cached)
- Cold capture — 5-8 seconds (new site)
You never see an error, only a slightly slower response.
Which domains get a pool?
Pools are provisioned automatically for any domain with sustained traffic (30+ requests/hour). Pool size and worker count scale with demand.