Organic Token Bundle on Ethereum: Random Buys, Own Wallets

Why identical bundle buys stand out

A Custom Bundle on Ethereum puts the whitelist call, the open-trading call and one Uniswap V2 buy per wallet into a single Flashbots bundle. Without any variation, each wallet buys exactly its Max Tx % of supply. The result is a block with N buys of the same size right after trading opens - a pattern bundle scanners are built to flag.

TokenBundle has two features aimed at that signal: randomized buy amounts, and wallets you import yourself instead of wallets generated and funded from one Master wallet. This guide explains what each one changes, and just as importantly, what it does not.

How a Custom Bundle executes on Ethereum

Every transaction in the bundle is signed in advance and simulated with eth_callBundle on the Flashbots relay before anything is sent. The bundle then goes to the Flashbots relay with the builders parameter naming every builder registered with Flashbots - about 19 from Flashbots' public builder registry, such as Titan, beaverbuild, rsync, bloXroute, Quasar and Loki - and directly to Titan, Beaver and rsync. It is retried for each of the next 10 blocks.

The bundle is all-or-nothing in one block. If it is not included, nothing in it is spent (the service fee is paid once from the Master beforehand and is not charged again on a retry). Each wallet's buy is priced in order against the post-open pool with a 3% tolerance. Requests are signed with a stable key so the sender builds reputation with Flashbots, which prioritizes reputable senders when busy.

Randomize buy amounts: varying each wallet's size

The "Randomize buy amounts" setting takes a value from 0 to 50%, with a default of 15. Each wallet then buys a random amount between (100 - x)% and 100% of its Max Tx target. With the default of 15, every wallet buys somewhere between 85% and 100% of its target, so the bundle no longer shows N identical buys.

Wallets are still funded for the full target, so a wallet that draws a smaller amount simply keeps the unused ETH. Buy sizes also remain capped by the token's own Max Tx, so randomization only ever moves amounts down from the target, never above it.

Import my wallets: avoiding a shared funding source

Generated wallets are funded through Distribute, which is one Multicall3 transaction from one Master wallet. That is efficient, but it links every funded wallet on-chain to the same Master. Anyone tracing where the buyer wallets got their ETH finds one common source.

"Import my wallets" lets you paste your own private keys instead - with or without the 0x prefix, up to 100 of them. They are encrypted and stored the same way as generated wallets and buy in the order you pasted them. If those wallets were funded from elsewhere, the common funding source disappears from the trail.

Imported wallets that already hold ETH count toward funding. "Skip (already funded)" checks balances, so you do not have to send ETH to wallets that already have enough.

Generated vs imported wallets compared

What on-chain observers can still see

It is worth being direct about the limits. In an atomic bundle, all buys still land in the same block, right after the open. Anyone looking at that block can see a cluster of buys immediately following the open-trading call, regardless of their sizes or where the wallets were funded from.

Randomized amounts and imported wallets reduce the signal; they do not remove it. They make the pattern less obvious to simple scanners that look for identical sizes or a single funding wallet, but they do not make a same-block bundle indistinguishable from independent buyers arriving over time.

Practical setup for a less uniform bundle

• Set Randomize buy amounts between 0 and 50%; the default of 15 already breaks identical sizes.
• Import wallets you funded from different sources rather than relying only on Distribute from one Master.
• Use Skip (already funded) so imported wallets with enough ETH are not topped up again.
• Check each wallet's Max Tx % against the token's own Max Tx, since buys are capped by it.
• Remember the bundle only spends if it lands, so a missed block costs nothing.

FAQ

• Does randomizing buy amounts make a bundle undetectable? No. All buys still land in the same block right after the open, and observers can see that; randomization only removes the identical-size pattern.
• Do randomized wallets get less ETH? No. Wallets are still funded for the full Max Tx target, and each one buys a random amount between (100 - x)% and 100% of it.
• How many wallets can I import? Up to 100 private keys, pasted with or without 0x. They are encrypted and stored like generated wallets.
• Why does funding with Distribute link my wallets? Distribute is one Multicall3 transaction from one Master wallet, so every funded wallet shares that on-chain funding source.
• What happens if the bundle is not included? Nothing is spent. The bundle is retried for each of the next 10 blocks and is all-or-nothing.

Related guides