πΌ Bundlesο
A bundle is a group of up to five transactions that execute sequentially and atomically: all of them land, in order, or none do. Bundles give you MEV protection, fast landing and revert protection.
There are two ways to send a bundle:
Direct Bundle Ingest (DBI) |
Block Engine |
|
|---|---|---|
Path |
Straight to a BAM Node |
Through the Block Engine |
Leaders served |
BAM leaders only |
BAM and non-BAM leaders |
Access |
Allowlisted; separate DBI credentials |
Authorized Block Engine key, or none |
To BAM leaders |
Direct |
Authorized key: forwarded, no BE auction |
Without a key |
Not available |
1 request/s per IP; BE auction first |
Docs |
This page and bam.dev |
Direct Bundle Ingest (DBI)ο
DBI lets an approved searcher or application send bundles straight to a BAM Node over JSON-RPC or QUIC, removing the Block Engine hop for the shortest path to BAM leader slots.
Full documentation: bam.dev β DBI
How a bundle reaches the leader: directly with DBI, forwarded by the Block Engine with an authorized key, or through the Block Engine auction without one.ο
What happens to a DBI bundleο
You submit one to five fully signed transactions, in bundle order.
The BAM Node verifies the signature on every transaction.
The bundle is simulated. Only bundles in which every transaction succeeds move forward.
Survivors enter BAMβs auction, ranked by total fees (priority fees and Jito tips) per compute unit.
Winners go to the current BAM leader as one atomic batch. If any transaction fails at execution, the whole bundle reverts.
Key pointsο
Access is allowlisted. Apply with the DBI access form. A Block Engine UUID does not grant DBI access.
Two transports, two credentials. JSON-RPC uses a Jito-issued UUID; QUIC uses an allowlisted Ed25519 keypair. Neither works for the other.
No minimum tip, but tips win. BAM ranks bundles by reward per compute unit, so a bundle that pays nothing will not land when there is competition.
Keep the Block Engine as your fallback. DBI serves BAM leader slots only and pauses during BAM Node maintenance.
Check landing yourself. DBI bundles donβt appear in the bundle explorer. Confirm with
getSignatureStatuseson your own RPC.
Learn moreο
DBI on bam.dev: endpoints, rate limits, transaction versions and troubleshooting
jito-labs/bam-dbi: Rust reference clients for JSON-RPC and QUIC
Block Engine bundlesο
To send bundles through the Block Engine with sendBundle, which also reaches non-BAM
leaders, see Low Latency Transaction Send β Bundles.