Skip to main content
Submit a single user-signed transaction. nexroute acknowledges synchronously with the deterministic transaction hash, then forwards the transaction through private partnerships. Where a profitable on-chain backrun exists, it is appended atomically behind the user transaction; otherwise the user transaction is forwarded alone. The partner-signed transaction is forwarded byte-for-byte; nexroute does not re-sign or modify the payload. Once a hash is returned, delivery is committed.

Request

POST to your Capture endpoint with a JSON-RPC 2.0 envelope.

Params

params is a single-element array containing the request object.

Example

Response

A JSON-RPC envelope echoing the request id. result is the 32-byte transaction hash. Once returned, delivery is committed.

Errors