Bundle Mechanics & Fees
Last updated
This page describes how MEV bundles are processed on BNB Smart Chain (BSC), including bundle execution flow, fees, prioritization, and validity requirements. It is intended for searchers submitting MEV bundles via bloXroute’s MEV solution.
Searchers submit MEV bundles to the Cloud API.
Builders combine submitted bundles with mempool transactions to construct candidate blocks.
Validators accept and commit the block offering the highest total reward.
Searchers share MEV profits with both the validator and bloXroute.
We have introduced a dynamic fee mechanism that improves bundle landing speed and prioritization. To enable it:
Send a BNB payment to the bloXroute dynamic fee smart contract:
&#xNAN;0x6374Ca2da5646C73Eb444aB99780495d61035f9b
Include the following field in your bundle submission payload:
"mev_builders": { "all": "" }The dynamic fee payment can be made via:
Internal transaction transfer (may require a custom smart contract), or
An additional regular transaction included in the bundle
A single BNB payment covers both validator and bloXroute fees. Dynamic fees are weighted higher than gas fees, improving bundle prioritization.
Bundles are prioritized using the following high-level formula:
Private transactions are those created by the searcher and not visible in the public mempool. Higher dynamic fee payments increase bundle priority and encourage competitive bidding among searchers.
All bundles must satisfy a minimum effective gas price of 0.05 gwei, calculated over private transactions only:
Enterprise plan users (and above) may submit bundles below 0.05 gwei, including 0 gwei bundles, provided the requirement above is met. This allows Enterprise users to redirect gas savings toward higher dynamic fee payments when competing for the same opportunity.
Last updated
Bundle Score = (Private TX Gas Fees × 0.9) + Dynamic Fee Payment(Gas Fees + Dynamic Fee Payment) / Gas Used ≥ 0.05 gwei