Locked vs Burned Liquidity: What Creators Give Up at Graduation

Burning liquidity at graduation is sold to buyers as protection, and it is protection. It is also the moment the creator's LP fee stream is destroyed, permanently, and almost nobody prices that before they launch.

Those are the same fact seen from opposite sides of the trade. A burn makes the position unwithdrawable by making it unreachable, and unreachable is indiscriminate: it does not distinguish the principal a buyer wants immobilised from the fees a creator was promised a share of. Both go.

So the choice between burning and locking is a design decision with an arithmetic consequence, and TrustSwap's own launchpad, Bullcheese, which launches on 16 September 2026, the day Arc's public mainnet opens, takes the other branch of it. What follows is the mechanism on both sides, a worked example in USDC with every assumption labelled, and the honest case for burning anyway.

A burn is a one-way transfer, and the accrued fees leave with the principal

The two dominant pool designs handle fees differently, and that decides what a burn destroys.

In the constant-product design, trading fees are added to the pool's reserves and belong to LP token holders in proportion to their share. There is no separate fee balance; the only way to realise fees is to redeem the LP tokens. Burn those tokens and the principal and every fee it earned become unredeemable together. The fees do not stop accruing — they accrue to nobody.

Concentrated liquidity looks more forgiving. Fees are credited to the position and paid out by an explicit collect call from its owner, separate from the principal, and that separation is what makes claimable-fee designs possible. But a burn removes the owner: send the position to a dead address and no account exists that can make the call. The accounting still runs, the balance still grows, and nobody can collect it.

A worked example in USDC, with every assumption labelled

These assumptions are chosen to be small and checkable, not to project what any token will do.

Assumption one: a 1% pool fee tier, one of the tiers Uniswap offers for volatile pairs. Assumption two: $250,000 of cumulative trading volume across the position's first 90 days — a deliberately modest figure for a token that trades at all. Assumption three: the creator's contractual share of trading fees is 75%.

The arithmetic is one line. One per cent of $250,000 is $2,500 in trading fees accrued to the position over the period, and the creator's claim on that is 75% of $2,500.

Now run the same token through a burn at graduation. Every fee accrued before the burn and after it sits in a contract with no owner able to collect. The creator's share is unchanged as a percentage and worthless as a number, because the base it applies to is unreachable. Whatever the venue advertised on the way in, the burn sets what the creator can realise from the LP fee stream to zero from that block onward.

Three caveats matter more than the arithmetic. This is not an earnings estimate and no venue can offer one: a token that never trades produces nothing, and most trade far less than $250,000. A small single-digit percentage of bonding-curve tokens ever reach a DEX at all, by most published estimates, so for most creators on a curve the question never arises because graduation never does. And a fee stream is not a return on anything — it is a share of other people's trading activity, which can stop at any time.

A vault lock changes who can move the principal, not who can collect the fees

A lock does the same job by a different route. The position moves to a locking contract that holds it until an unlock timestamp, and Team Finance's lock flow sets that date at lock time and publishes the record publicly. After expiry the depositor claims through the claims dashboard.

The principal is immobilised either way. What differs is that a lock leaves an owner in place, and an owner can be permitted to call one function and not another. Burned liquidity earns you nothing, forever. Locked liquidity keeps paying. Bullcheese's vault separates fee collection from withdrawal: liquidity stays locked through Team Finance's audited contracts, and the fee stream stays claimable. The creator takes 75% of trading fees during the lock, and after 90 days the creator can relock the position and keep the whole fee stream.

The buyer's question is not what was promised but what the contract permits

"Locked isn't burned, so what stops a rug?" is the right question and it has a mechanical answer. Withdrawal is gated by an unlock date in contract state, not by a policy on a website, and fee collection is a different function with different permissions. The lock's unlock date is readable on-chain, by anyone, before a single token is bought.

So the buyer's check is a state read rather than an act of trust. The lock record carries an amount, a contract, a depositor and an unlock date, all on-chain, none dependent on the launch venue continuing to exist. The buyer is not asked to believe a founder, only to read a contract.

How to check a Team Finance lock without taking anyone's word for it

Start from the token or pool address rather than a link someone sent you. Team Finance publishes a public page per locked asset — the team.finance/view-coin/ pattern followed by the contract address — showing the amount locked and when it unlocks. The lock transaction is on Arcscan, and the position it moved should be the one the pool holds.

Read three fields carefully: the unlock date, because "locked" with a date next week is technically true; the amount, because a lock covering a fraction of the liquidity is not a lock on the pool; and the depositor, because a lock deposited by an unrelated wallet is not evidence about the token. How to verify a liquidity lock on Arc walks the sequence with the failure modes attached.

The strongest argument for burning is that it asks nothing of you at all

The case for burning deserves better than the dismissal it usually gets.

A burn is one irreversible state change any buyer can verify in seconds by looking at where the LP went. There is no contract to audit, no expiry to diarise, no admin key, no upgrade path, no counterparty still around in six months with a decision to make. A lock replaces that single fact with things a buyer has to evaluate: whose contract, audited by whom, for how long, with which permissions, and what happens at expiry. Every added component can be wrong. And the thing that makes locking attractive to creators — that they are still in the picture, still earning, still holding a decision about the unlock date — is exactly what the burn was designed to remove.

The honest answer is that burning buys its simplicity by destroying the asset that pays creators to stay involved with what they built. That is a real trade and some projects should take it. But the simplicity only counts if the buyer performs the check, and checking a burn means reading an address on an explorer — the same class of action as reading an unlock timestamp on one. A lock enforced by audited contracts, with a record on a page that loads without the venue's help, is not a weaker fact. It is a longer one.

Some launchpads on Arc will tell you their liquidity is locked. The question worth asking now is which of them publish unlock dates without being asked — and which creators discover, at their first fee claim, what their venue actually meant by the word.

Bullcheese is a permissionless launch venue. Tokens launched on it are created by anyone, carry no endorsement, and can go to zero. Nothing here is financial advice.