Bundle Submission

Searchers can submit MEV bundles to the Cloud API, where they are validated and forwarded to Builders that are connected to BSC validators participating in Bloxroute’s MEV solution. Bundles are optimized to maximize validator rewards, ensuring efficient MEV extraction.

Purchase the Bundle Size Add-on to send bundles with more than 2 transactions.

Submission Endpoint

  • Method: blxr_submit_bundle

  • Endpoint: api.blxrbdn.com

  • Request type: HTTPS,WSS

Parameters

txs

A list of raw transaction bytes without a 0x prefix, separated by a comma.

blockchain_network

Blockchain network name. Must be BSC-Mainnet.

max_block_number

[Optional] Default: current block number + 100

min_timestamp

[Optional] The minimum timestamp that the bundle is valid on, an integer in unix epoch format. Default value is None.

max_timestamp

[Optional] The maximum timestamp that the bundle is valid on, an integer in unix epoch format. Default value is None.

reverting_tx_hashes

[Optional] A list of transaction hashes within the bundle that are allowed to revert. Default is empty list: the whole bundle would be excluded if any transaction reverts.

mev_builders

[Optional, default: bloxroute builder] A dictionary of MEV builders that should receive the bundle without delay. For each MEV builder, a signature (which can be an empty string) is required. Possible MEV builders are:

  • bloxroute: bloXroute internal builder (always enabled for all MEV bundle submission requests)

  • all: all builders

  • Other options: 48club, blockrazor, jetbldr, nodereal

no_merge

[Optional, default: False] Bundle merge can increase block value and inclusion rate.

backrunme_reward_address

[Optional] When the bundle is enrolled in the BackRunMe service, the transaction's from address collects backrun reward by default. The reward address can be overwritten with this parameter.

Examples

Response:

Last updated