Skip to main content
Async mode is built around a single commitment to the partner: what you notify is used to build a backrun behind your transaction, and for nothing else.

​
Privacy

  • Notified transactions are never broadcast, to the public mempool or anywhere else. Dispatch is yours alone
  • Notified transactions are used solely for backrun construction; they are not shared with third parties
  • No party, nexroute included, front-runs a notified transaction. The backrun targets the position directly behind it
  • The dedicated per-partner endpoint is not visible from the public internet (see Authentication)
Because you dispatch the transaction, its mempool exposure is determined by your broadcast path. If mempool privacy matters, dispatch through a private relay.

​
Non-interference

  • nexroute never holds, delays, re-signs, or modifies a notified transaction; it never enters nexroute’s routing pipeline
  • The backrun is a separate transaction signed by nexroute’s wallets, submitted independently through private partnerships
  • A backrun that misses its position or reverts has no effect on your transaction

​
Delivery

Async mode carries no delivery guarantee, by design: nexroute never dispatches your transaction, so inclusion is entirely determined by your own broadcast path. The acknowledgment hash confirms the notification was accepted for backrun analysis, nothing more. If you want delivery, privacy, and backrun handled by nexroute in one move, use Dispatch mode.

​
Network

  • Per-partner IP allowlist enforced at the network layer
  • HTTPS and secure WebSocket (wss://) supported on the same endpoint
  • TLS termination at the endpoint; in-flight encryption end-to-end from partner to nexroute