Base
Searchers can connect to a WebSocket feed of private pending transactions on Base, allowing them to submit backrun bundles into a short, competitive auction window.
An API key is required. Keys authenticate the WebSocket connection and may be rate-limited or revoked if rules are violated.
Auction Mechanics
Each eligible transaction opens a short auction window (up to ~100ms). The unsigned transaction is sent via WebSocket to searchers, and searchers may send one or more bids to win the right to backrun the transaction.
At auction end, the highest-paying searcher is sent the raw signed transaction and may broadcast it, along with their backrun, directly to the sequencer. After some time, Nova also broadcasts the transaction and backrun to the sequencer, guaranteeing inclusion.
Latency is critical, and colocation in AWS us-east-1 is strongly recommended.
Refund Rules
Searchers must return at least 75% of realized profit to the refund address:
An example of this can be seen here.
This refund must be an explicit ETH transfer included in the backrun transaction itself. Profit is evaluated per bundle based on on-chain execution.
Any form of sandwiching against protected transactions results in an immediate ban.
Monitoring and Enforcement
The system continuously monitors:
Sandwich behavior
Profit share compliance (≥ 75%)
Revert rates, especially during competitive auctions
Latency and submission patterns
Violations may result in reduced flow, artificial websocket delays, or a permanent ban, depending on severity and persistence.
WebSocket Connection
Connect using your API key:
The protocol uses JSON-RPC 2.0 over WebSocket. If the connection drops, clients must reconnect and resubscribe. No state is preserved across reconnects.
Transaction Subscription
After connecting, you must explicitly subscribe to receive transactions:
The stream emits pending transactions eligible for backruns. Messages are delivered in the order they arrive at the server. No ordering or completeness guarantees are provided beyond that.
Responses contain individual transactions with signature fields stripped:
If your bid wins the auction, you will receive the signed raw transaction bytes
Submitting Bids
Bids are submitted over the same WebSocket connection using eth_sendBundle:
txs- an array where the first element is the target transaction hash (as received in the auction notification), and the second element is your signed backrun transaction in raw hex form. Only one backrun transaction is supported per bundle.bid- your bid amount in wei. This is used to rank backruns during the auction.replacementUuid- optional. If provided, any previous bid with the same UUID will be replaced, allowing you to update your bid during the auction window.
Note: Auctions may extend beyond the current flashblock. If the auction window spans a flashblock boundary, the winning backrun will be included in the next flashblock.
Last updated