Multi-socket, non-blocking EPP: how the engine fires in parallel

Every script in the engine runs multi-socket and non-blocking. This is the architectural core of its catching performance.

A blocking connection would send one EPP command and wait for the reply before doing anything else. Non-blocking, multi-socket operation means the engine opens many EPP sockets at once and streams commands across all of them without stalling on any single response. When a name releases, that translates into many well-timed create attempts in parallel rather than a single serial one.

The more parallel sockets your hardware can sustain, the more attempts you can make in the critical release window — which is why heavier catching benefits from more capable servers.