Yes — once a Flap token leaves its bonding curve, its pool’s LP tokens are burned and nobody can pull that money out. Some scanners still say “not locked”.
Short answer: yes, once the token has a pool. A Flap token starts on a bonding curve run by Flap’s launchpad contract, and until the curve fills, nobody can open a pool for it. At graduation the launchpad moves the money into a PancakeSwap V2 pool and burns that pool’s LP tokens, so neither the creator nor Flap can take that liquidity back. Scanners that look only for pools paired with BNB or dollars often miss it, because Flap also pairs tokens with BTCB and others — ours did, until 19 October 2026. What the burn doesn’t cover: the tax, which can’t be changed after launch but is paid on every trade through the launch pool; liquidity other people add later; and the money still sitting on curves. Paste a Flap token’s address to see the pool, the tax and who holds the supply:
Flap, at flap.sh, is a token launchpad on BNB Chain (BSC). Every Flap token we have checked is a copy of the same contract, FlapTaxTokenV3 — Flap’s tax token — with a fixed supply of 1 billion, and the whole supply is minted to Flap’s launchpad contract, not to the creator. Their addresses all end in 7777.
On the curve you buy from and sell to the launchpad contract; the price rises with every buy and falls with every sell. The token can’t be sent into its launch pools at this stage — their addresses are written into the token when it is created — so nobody can start trading it on an exchange early. The token’s owner is the launchpad contract, and its only powers over the token are to start and finish the move to the pool.
When the curve fills, the token graduates. The launchpad moves the liquidity into a PancakeSwap V2 pool and burns the pool’s LP tokens by sending them to the burn address 0x…dEaD. The pool is paired with whatever the launch chose: BNB, or another token — among the Flap tokens we checked, BTCB (Bitcoin on BNB Chain), QQQB, BNCB and SPCXB. After graduation the token has no owner at all.
The money in a PancakeSwap V2 pool belongs to whoever holds the pool’s LP tokens, and only they can take it out. A Flap launch pool’s LP tokens sit at the burn address, which nobody controls, so the liquidity Flap put in stays in the pool for good. On six of the seven graduated Flap tokens we checked, 99.87–100% of the launch pool’s LP tokens were burned; the seventh, MERA, is explained below.
Nothing else can reach that liquidity either. The token’s code can’t be replaced: each Flap token is a fixed copy of the FlapTaxTokenV3 template, whose code is published on Sourcify and BscScan and has no upgrade function. After graduation the token has no owner, and it never had a pause switch, a blacklist or a way to mint more.
Our data source, like many scanners, finds a token’s pool by searching its pairs with BNB and dollar tokens. A Flap token paired with BTCB, QQQB or another token has no such pair, so the scanner finds no pool to read and reports the liquidity as not locked, while the real pool has its LP tokens burned. Our free check did the same: until 19 October 2026 it said “Liquidity locked: No” for five Flap tokens. One of them, FLORK, had about 1.76 BTCB in its launch pool with 99.99% of the LP tokens burned. We now read Flap’s launch pool directly; the mistake is logged on our corrections page.
A Flap tax token charges a tax on buys, on sells, or on both. The rates are written into the token when it is created, and the token has no function to change them: the creator can’t raise the tax later, and can’t lower it either. Among the eight Flap tokens we checked, buy taxes were 0–3% and sell taxes 1–3%.
Where the tax is charged matters. For a while after graduation it applies in every pool registered when the token was created; after that, only in the main launch pool on PancakeSwap V2. Trades through any other pool pay no tax — and a swap app may route your trade through one. That is why scanners can show a Flap token’s tax as 3% one day and 0% the next: they measure it through whichever pool they find.
The tax has an end date, also set at launch. Once it passes, the next sale into the launch pool switches the tax off for good. On seven of the eight Flap tokens we checked, the tax runs for 100 years after graduation — in practice, forever; GM’s ends on 29 September 2027.
The token doesn’t keep the tax. A separate tax contract, created with each token, sells it, keeps a share for Flap and sends the rest where the launch set it: on FLORK and GM, to holders as dividends; on hooks and MERA, to a single wallet. That contract’s code isn’t published, and its owner is Flap’s launchpad contract, so we can tell you where the money goes today — not that this can never change.
| Contract | What it does | Address |
|---|---|---|
| Launchpad (portal) | Runs every bonding curve, creates the pools; owner of each token until graduation | 0xe2ce6ab80874fa9fa2aae65d277dd6b8e65c9de0 |
| FlapTaxTokenV3 | The code every Flap tax token runs; can’t be changed | 0x024f18294970b5c76c0691b87f138a0317156422 |
| ProxyAdmin | Can replace the launchpad’s code | 0xb2480c2d17bf4510701c4def374de6d22e039bd4 |
| ProxyAdmin owner | Flap’s Safe multisig, 3 of 4 signers; not a timelock | 0x1f96bc88f0794060433be5f3ec9159a9c4f08a3b |
| Fee receiver | Gets Flap’s share of the tax — the same address on each token we looked at | 0x8a08d98cbb218fceb318ecf3abc1ba43d8a7ab0e |
A Flap tax token is an ERC-20 with a fixed supply of 1 billion, minted once when it is created. It has no pause switch, no blacklist, no function to mint more and no function to change its tax, and its code can’t be replaced. Its only owner rights — starting and finishing the move to the pool — belong to Flap’s launchpad contract until graduation; after that, the token has no owner. Every Flap tax token runs the same code, so our check reads the tax from the token itself and, where our data source is silent, fills the contract rows from that code — the source column then says “Flap token code”.
0x024f18294970b5c76c0691b87f138a0317156422 and the contract name FlapTaxTokenV3. The 7777 ending alone proves nothing — anyone can create an address like that. Our check looks at the code, not the ending.state: 0 means the token is still on its curve, 1 that it is moving to its pool, 2 or 3 that it trades in its pool with the tax on, 4 that the tax period is over. For a token on its curve, our check’s “Liquidity locked” line reads “Not in a pool yet — Flap bonding curve”.buyTaxRate and sellTaxRate are the rates in hundredths of a percent: 300 is 3%. After graduation, taxExpirationTime is the moment the tax ends, as a Unix timestamp. Our check shows the rates in the Buy tax and Sell tax rows.mainPool is the launch pool. Open that address on BscScan — the pool is a token too, its own LP token — and look at its Holders: the burn address 0x…dEaD should hold almost all of it; if it doesn’t, someone has added liquidity since. Our check reads the same share, for example “99.99% burned”, and says what the pool is paired with.FLORK graduated into a PancakeSwap V2 pool paired with BTCB. On 19 October 2026 that pool held about 1.76 BTCB, and 99.99% of its LP tokens were burned — yet our data source saw no lock, because it didn’t find a BTCB pool. FLORK charges 3% on buys and sells through its launch pool; after Flap’s share, the tax goes to holders as dividends.
hooks is paired with BNB, so scanners do see its pool: 99.9% of the LP tokens are burned. Its tax is also 3% each way, and after Flap’s share it goes to a single wallet.
솜사탕 was still on its curve on 19 October 2026: no pool yet, 25 holders, and 83.5% of the supply still in Flap’s launchpad contract — tokens nobody had bought. Our check reads “Not in a pool yet — Flap bonding curve” and names the launchpad as the owner.
Is Flap liquidity locked forever? The liquidity Flap puts in at graduation, yes: its LP tokens are burned, and a burn can’t be undone — there is no unlock date because there is no lock to end. Liquidity other people add later is theirs. A token still on its curve has no pool yet.
Is “burned” better than “locked”? For the pool, yes: a lock ends on a date, a burn never does. It says nothing about the tax, the holders or whether anyone will keep buying.
Can a Flap creator rug pull? Not by pulling the launch pool — its LP tokens are burned. But a creator who bought cheaply on the curve can sell, and if the tax goes to a wallet, that wallet collects from every trade. Look at the tax, where it goes and who holds the supply.
Why does a scanner say “liquidity not locked” for a Flap token? Because it didn’t find the launch pool. Flap pairs many tokens with BTCB, QQQB or other tokens instead of BNB, and a scanner that searches only BNB and dollar pairs misses them. Our check reads Flap’s launch pool directly.
Why does the tax show 3% one day and 0% the next? The tax is charged only on trades through the token’s launch pool. A scanner that tests a trade through another pool sees no tax. The rates themselves can’t change.
Can a Flap token become a honeypot later? The token has no switch for it: no pause, no blacklist, no owner after graduation, and a tax that can’t be raised. A tax can still be set high at launch, so read it before you buy — our check also tests whether the token can be sold.
Who gets a Flap token’s tax? Its tax contract — taxProcessor on BscScan — sells the tax, keeps a share for Flap and passes the rest on as set at launch: to a wallet, to holders as dividends, or a mix. Dividends wait in another contract, also owned by Flap’s launchpad; where its code is published, it lets that owner redirect any holder’s payouts and withdraw what it holds.
Is every token ending in 7777 a Flap token? No. The Flap tokens we have seen all end in 7777, but anyone can create an address with that ending. Check the code: a Flap tax token is a minimal proxy of FlapTaxTokenV3, 0x024f…6422.
Does a burned pool make a Flap token safe? No. It means the launch liquidity can’t vanish in one transaction. The tax, who bought first and who holds the supply decide the rest.