Introduction

nexroute Cashback is a backrun service for partner orderflow. It identifies MEV opportunities behind partner swap transactions and atomically attaches a backrun, monetizing flow that would otherwise leak to searchers, builders, or validators. Cashback supports three integration modes. Pick the one that matches how your stack constructs and submits user transactions.

​

Dispatch mode

Submit a fully user-signed transaction to a dedicated nexroute endpoint. nexroute acknowledges synchronously, evaluates the transaction for backrun opportunity, and forwards the bundle through private partnerships. The partner-signed transaction is forwarded byte-for-byte; the backrun is a separate transaction signed by nexroute and bundled behind it. Recommended when feasible. Faster (one round trip from partner to nexroute, then direct dispatch via private partnerships), cleaner separation of concerns (the partner submits a raw transaction and nexroute owns the backrun), and privacy by default.

​

Async mode

Send a copy of the user-signed transaction to a dedicated nexroute endpoint and dispatch it yourself, without waiting for a response. nexroute evaluates it for backrun opportunity and optimistically races a backrun in behind your transaction. Your dispatch path is untouched. Use when you dispatch, but can’t wait. Built for partners on chains with very low block intervals, where a synchronous round trip before dispatch would cost inclusion position. The trade: the backrun is best-effort rather than atomically bundled, and delivery and mempool privacy of the user transaction remain the partner’s responsibility.

​

Embedded mode

The backrun runs in the same on-chain transaction as the user’s swap. nexroute provides backrun calldata via API; the partner composes it into the user transaction. The user signs once (typically a Permit2 typed-data message), and the swap and backrun execute atomically. Use when the partner never holds the fully signed transaction. The typical reason: the user’s wallet (or another party the partner doesn’t control) signs and dispatches, so the partner can neither relay the transaction through nexroute’s endpoint nor notify nexroute of it. The backrun API call sits in the user-facing critical path, and the partner takes on backrun integration in its own transaction construction. Privacy is the dispatcher’s responsibility; if mempool exposure is a concern, the dispatcher must use a private relay.

​

Compare modes

​

Reporting

A per-transaction explorer and aggregated reporting dashboard for inclusion status and partner activity is in active development. Contact nexroute for the current status.

​

Get started