Bundles and blocks

If a token is created in one block and bought in the next, anyone watching the chain can buy in between, on a fresh curve, at the lowest price there will ever be. A bundle removes that gap.

What a bundle is

An ordered list of signed transactions handed to a block builder with one instruction: include all of them, in this order, in one block, or include none of them. Nobody can insert a transaction between them, because there is no "between". The builder places them adjacently or not at all.

The console uses this in three places:

• Launches. The create transaction plus every wallet's buy.
• The Bundler. Many buys of a token that already exists.
• Selling a position. The exit is the side where being read costs the most, so every wallet's sale goes into one block. See Tokens.

On BNB Smart Chain

Bundles go to 48 Club Puissant and BlockRazor in parallel. If either lands, the run wins. Between them they build most blocks on the chain.

There is a size limit, and it depends on what the deployment has configured:

The launch and bundler forms print how many transactions the current run would be, so the limit is visible before it is hit rather than after.

The bid is automatic and comes from gas rather than a separate tip transaction. A run starts at three times the current gas price and escalates by half each round, up to six rounds, then stops and reports. There is a ceiling so that a heavy create stays affordable.

On Robinhood Chain

There is no bundle market at all. The chain has a single sequencer, orders transactions first come first served, and reports a priority fee of zero, so paying more cannot move a transaction forward.

The console does not pretend otherwise. Where atomicity exists it is inside a single transaction: PONS wraps creation and every buy into one call, and Flap runs the creator's own buy inside its create. The remaining wallets follow as fast as the sequencer takes them, and the log says exactly that.

One address, one transaction

A bundle is applied in order against one state, so two transactions from the same address in the same bundle carry the same nonce, and the second one is invalid. The builder does not drop it. It refuses the whole bundle, with nonce too low, at any bid, every round.

The common way to hit this is a creator wallet that is also saved in the funded wallet book: it would send the create and then a buy. The console drops it from the buys and says so in the log, because the creator has already bought inside the create transaction, ahead of everyone else.

Sending without a bundle

Turning the atomic switch off, or running on a chain that has no builder, sends the same transactions through a private relay instead of the public mempool where one exists. That hides them from anyone watching pending transactions, but it does not make them atomic: they land in whatever order the chain gives them, and something else can land in between.

When a bundle does not land

The run retries with a higher bid for several rounds, then stops and tells you, quoting the builders' own words rather than a guess. Nothing has been spent: an unlanded bundle is not a failed transaction, it is a transaction that was never included.

The usual reasons, in the order worth checking: