flap.sh Bundled Trade

Put the buys or sells of many wallets on one flap.sh token into a single block. The venue stays fixed to flap.sh, whether the token is on its curve or graduated.

CapacityUp to 20 wallets per bundleRun: one bundle, every trade in the same block

From

BNB

Price: –
Liquidity: –
Platform: –
Pool: –
Tax: –
Block: All in one block

Routeflap.sh only

Wallets

0/ 20

BNB

token

Out

0BNB

≈ In

–token

Progress

0/ 0

Wallets0

Per wallet (BNB)

0 wallets · 0 eligible

Wallet

BNB

token

Amount (BNB)

Status

No wallets yet. Import keys to start.

Transactions● 0 landed● 0 failed● 0 pending

TimeBndWalletBNB → tokenStatusTx

Each wallet's trade shows here once the bundle goes out, one row per wallet.

SlippageAuto1%

1%25%50%

Eligible: 0
Platform fee: …
Gas total: …
Total buy: 0 BNB

Add your bot wallets to continue.

The bot wallets pay their own amounts and gas. Your connected wallet pays the J Tools fee for the bundle, in one approval before it goes out. If the bundle isn't included, the fee stays as a credit for the next bundle of this token from the same bot wallets.

About this tool

How flap.sh Bundled Trade works

Add the wallets that should move together

Paste up to 20 private keys or load them from a file. They stay in this tab's memory, never anywhere else. Each wallet trades with its own BNB or its own tokens, and it covers its own gas.

Frequently asked questions

You choose the token, the wallets, the side and the amount mode. The J Tools server writes one transaction per wallet through the flap.sh Portal, simulates them in order as a single block, and fixes each wallet's minimum from that result. The bot wallets sign those transactions here without changes, and the bundle goes to BNB Chain builders. Either every trade lands in one block or none does.

A bonding curve with little depth reacts to every trade. When many wallets trade inside one bundle, each wallet meets the price left behind by the ones ahead of it, so the last wallet in line can see a noticeably different price from the first. The server's block simulation runs the wallets in their real order, which means each minimum reflects the price that wallet will actually meet.

Yes. After graduation the token trades on its DEX market, and the flap.sh Portal still quotes and swaps there. The desk routes the bundle through the Portal in both stages, and the token panel tells you which one applies. A flap.sh market that is closed, or a token priced in something other than BNB, is turned away before any wallet signs.

A plain PancakeSwap token or a four.meme token gets a short notice before you press anything, with a link to the PancakeSwap or four.meme version of Bundled Trade. The general Bundled Trade page accepts any supported token too. For such a token this page takes no fee and asks for no signature.

A flat 0.022 BNB per bundle, paid from your connected wallet right before signing. J Tools adds no charge inside the flap.sh trades. If the builders leave the bundle out, none of its trades run, so the bot wallets spend no gas, and the fee waits as credit for your next bundle of the same token from the same wallets.

No. They are imported into this tab and kept in its memory only: never sent to J Tools or any server, never stored or logged, and gone when you close the tab. The bot wallets sign right here. For a sale, each one approves the flap.sh Portal for exactly the amount it sells before the bundle goes out, and your connected wallet signs only the J Tools fee.

1 / 6Use ← → to turn pages

flap.sh Bundled Trade

How flap.sh Bundled Trade works

Add the wallets that should move together

What flap.sh Bundled Trade does

In short

What it does

What it costs

Bundle a flap.sh token trade in 3 steps

Add the wallets that should move together

Pick the flap.sh token and amount mode

Pay, sign and wait for three confirmations

How flap.sh bundles land on BNB Chain

Frequently asked questions

Plan a flap.sh bundle

What to do next