burneh
Crypto

Coordinated actions that land together, or not at all.

When an operation spans several steps or several wallets, the danger is the middle failing and leaving you half-done. We bundle the actions so they're atomic: all of them land in one block, or none do. Submitted privately, so it isn't front-run, and receipted end to end.

Start a build
1 signatureatomicprivate relay

Check the payouts you want, then submit. They land in the same block together, or the whole thing reverts and nothing moves.

Build a bundle4 of 4
total
7.5 ETH
signatures
1 not 4
block #21,450,126pending
Nothing has moved yet. The whole bundle lands in this block together, or none of it does.

Watch the third step revert.

A four-step operation where step three fails. Run it the way most people do, one transaction at a time, and again as a single bundle. Same failure, very different outcome.

01approvequeued
02swapqueued
03add liquidityqueued
04stakequeued
outcome
press run to see it play out.

Sent separately, the two that already went through stay through. You're holding a broken position with gas already spent, and someone has to fix it by hand.

The public mempool is a shop window.

Anything sitting there can be watched and sandwiched before it's mined. We submit the bundle straight to the builder, so it stays invisible until it's already on-chain.

public mempoolexposed…
watching the mempool…

Your swap gets wrapped: bought ahead of, then sold into. You pay the worse price and the searcher keeps the difference.

private bundlesealed…
invisible until it's on-chain…

Sent straight to the builder, the bundle never appears in the public queue. There's nothing to see, so there's nothing to sandwich.

Built for the operations you actually run.

Bundling is an operations tool. It makes coordinated actions across wallets you own atomic, private, and gas-efficient.

Batch payouts

Pay every contributor, grantee, or vendor in one atomic transaction, receipted.

Coordinated treasury moves

Rebalance across a set of wallets you control without leaving gaps mid-way.

Migrations

Move positions from an old contract to a new one, all steps or none.

Multisig execution

Propose, collect signatures, and execute a bundle as a single unit.

where we draw the line

To be clear about what this is: it coordinates wallets you control for operations you run. We don't build tooling to fake demand or slip past the per-wallet limits on someone else's launch. That's the exact thing the mint and launch contracts we build are designed to stop.

Coordinated actions that land together, or not at all.

Atomic bundles, private submission so they can't be sandwiched, gas batched, and receipted end to end. For the operations you run across wallets you control.