TOKENBUNDLE / BNB / BNB CHAIN

How to Launch a Token on Four.meme With Bundled Wallets

Step-by-step guide to launching a token on Four.meme with up to 30 bundled wallets: sign-in, image upload, dry-run, buy floors, the 2% fee and retries.

What you are setting up

A bundled Four.meme launch puts the token creation, your dev buy and the buys from your other wallets into one builder bundle on BNB Chain. Everything executes in one block, in the order you set, or nothing executes.

TokenBundle's Four.meme Launch supports up to 30 bundle wallets alongside the dev wallet. The token itself is created by Four.meme's TokenManager2 contract with a fixed supply of 1,000,000,000 on a bonding curve. Before you start, have these ready:

  • A dev wallet that will sign in to Four.meme, pay for the dev buy and send the TokenBundle fee.
  • The bundle wallets that will buy in the same block. Each one needs enough BNB for its buy and its gas.
  • A token name, ticker, description, image and a category: Meme, AI, Defi, Games, Infra, De-Sci, Social, Depin, Charity or Others.

Step 1: sign in to Four.meme and upload the image

The dev wallet signs in to Four.meme by signing a message of the form "You are sign in Meme" followed by a nonce. This is an off-chain signature, not a transaction, and it costs nothing.

The token image is then uploaded to Four.meme, and Four.meme's own API returns the signed launch: a createArg and a signature for createToken. That signature is bound to the dev wallet, so the same createArg sent from another wallet would revert.

Step 2: set the dev buy and the bundle buys

The dev buy happens inside createToken, and the BNB sent with it is exactly the amount signed into createArg. The bundle wallets each buy with buyTokenAMAP right after creation.

You can enter one "BNB for all" amount and press Randomize to give each wallet a random 85-100% of it, so the launch does not show identical buys. Before launch, any wallet that cannot cover its part shows "Not enough BNB" and the Launch button stays disabled until it is fixed.

Step 3: the dry-run

Before sending, TokenBundle dry-runs createToken and every bundle wallet's buy in bundle order on current chain state with eth_simulateV1. Because Four.meme creates token addresses with CREATE2, the address is known before anything is sent, and the dry-run returns it along with each wallet's exact token amount.

Each buy then gets a 5% floor based on that simulated amount, so a buy will not execute far below what was simulated.

Step 4: launch and the bundle order

Because the fee is last in an all-or-nothing bundle, it is only paid if the launch lands. The bundle is sent to both 48 Club and BlockRazor.

  • createToken from the dev wallet, including the dev buy.
  • One buy from each bundle wallet, in order.
  • TokenBundle's 2% fee (2% of the dev buy plus all bundle buys) as the last transaction, from the dev wallet.

If the launch is not included

If no builder includes the bundle within its window, nothing is spent. Four.meme's signature is single-use and time-limited, so the right move is to start the launch again, which requests a fresh signed launch, rather than resending the old one.

This flow was tested by replaying a real historical Four.meme launch on a BSC fork with our buys and fee added, and everything landed in one block.

Common mistakes to avoid

  • Funding wallets with exactly their buy amount. Each wallet also pays its own gas, so leave room for it or the wallet will show Not enough BNB.
  • Reusing an old signed launch after a missed bundle. The signature is single-use and time-limited, so start the launch again to get a fresh one.
  • Switching the dev wallet after signing in. The signature is bound to the wallet that signed in, and createToken from any other wallet reverts.
  • Forgetting the 1% Four.meme trading fee. It is taken out of each buy amount, so a wallet's buy works with slightly less BNB than you entered.
  • Expecting the same token amount for every wallet. Each buy moves the bonding curve, so later wallets in the bundle get fewer tokens for the same BNB.

FAQ

  • How many wallets can I bundle on a Four.meme launch? TokenBundle supports up to 30 bundle wallets in addition to the dev wallet.
  • Can I use the signed launch from one wallet in another? No. Four.meme's signature is bound to the wallet that signed in, and a replay from another wallet reverts with an invalid signature error.
  • When is the TokenBundle fee paid? It is the last transaction in the bundle, so it is only paid if the whole launch lands.
  • Why does Launch stay disabled? At least one wallet shows Not enough BNB for its part. Fund it or lower its amount and the button enables.
  • Does Four.meme charge a launch fee? The launch fee is 0 today, but Four.meme's own 1% trading fee is taken out of each buy amount.
BNB CHAIN EXECUTION

Coordinate your launch with TokenBundle.

Prepare wallets, review allocations and manage network-specific launch execution from one workspace.

Open BNB Chain workspace
CONTINUE READING
BNB CHAINBNB Chain Token Launch Bundler: Complete Guide
BNB CHAINFour.meme Explained: Bonding Curve, Graduation and Fees
BNB CHAINBSC Builder Bundles: How eth_sendBundle Works on BNB