Tokens launched here earn.
The loop, as it stands
Fees, payouts, buybacks and burns are counted from the site's event log, which begins at block 786,110 (Sep 14, 2026). The first launch is older (block 770,811), so anything before the log began is not in them: they are floors, marked ≥. The stake is read from the chain and is complete.
Read at finalized block 1,474,973, runtime 225. The stake is the vault's staking ledger on chain; fees, payouts, buybacks and burns are sums over the site's event log. Each step is one figure because each step is one on-chain event: FeeNoted → Staked → Rewarded → Compounded, which both buys and burns.
The launches
One row per treasury. Each token's page carries the same figures live.
| Token | Treasury | Fees in | Staked | Floor | Buybacks / yr | LNRG accrued | Bought back | Burned | Last compound |
|---|---|---|---|---|---|---|---|---|---|
| TRSLTrading | active | 1.3004 VTRS | 1.2499 VTRS + 0.0505 VTRS pending | 0.0₆6 VTRS at graduation · 4.00% | ≈ 0.0124 VTRS run-rate at this stake | 0 LNRG | 0.0057 VTRS | 2.65K TRSL | block 1,467,237 1962 compounds · Nov 1, 00:02 UTC |
| IMGTTrading | active | 0.1875 VTRS | 0 VTRS + 0.1875 VTRS pending | 0.0₆6 VTRS at graduation · 4.00% | 0 VTRS | 0 LNRG | 0 VTRS | 0 IMGT | never |
| GRADGraduated | active | 7.5757 VTRS | 7.5757 VTRS + 0.0000029 VTRS pending | 0.0₆6 VTRS 4.00% of spot | ≈ 0.0757 VTRS run-rate at this stake | 0.00000039 LNRG | 0.0014 VTRS | 96.42 GRAD | block 1,462,217 8 compounds · Oct 31, 15:40 UTC |
| TESTFLOWTrading | active | 0.025 VTRS | 0 VTRS + 0.025 VTRS pending | 0.00092 VTRS at graduation · 4.00% | 0 VTRS | 0 LNRG | 0 VTRS | 0 TESTFLOW | never |
Floor is the locked pool's, not the treasury's: the price the pool would quote after every token outside it had been sold into it, VTRS reserve × token reserve ÷ supply². Graduation seeds the pool with 20.00% of supply and locks the LP forever, so the floor starts at 4.00% of the graduation price and rises as supply is burned or sold in. It is what the pool already holds, priced at its own worst case — not a promise, and the only number on this page a holder can count on. Each token's page shows it live.
Buybacks a year is a run-rate: the launch's staked value × the measured rate above. It is what today's numbers extrapolate to — the stake grows with every trade, the rate moves with the exchange rate, the validators and any slash — and it needs the broker to hold VTRS. Not a promise, and not paid to anyone.
5 of the 9 launches on this chain were created before the treasury existed. Their terms were snapshotted at creation with a treasury share of 0, so nothing from their trades reaches the vault; a snapshot never changes.
The difference is who has to be trusted
Staking yield that buys a token back is not new. The closest thing that exists is the Bonk validator on Solana: it commits all of its commission and MEV to buying and burning BONK, and has kept that commitment. It depends on an operator who chooses to keep it and can stop — retarget the commission, change the rule, or shut the validator down — and nothing on the chain would prevent it. Here the same loop is runtime code: no key, no authority, no call that moves the funds to a chosen account. A step still has to be triggered, but anyone may trigger it, the call pays whoever does, and it can only do the one thing. That is the whole difference, and it comes down to three facts you can check.
No key.
The vault is an account the runtime derives from the pallet's name, not from a private key. There is no multisig, no upgrade authority and no team wallet behind it; the only code that can move what it holds is the runtime itself, which changes by the same chain-wide upgrade that changes the staking rules. The Bonk validator's commission lands in an account its operator holds the key to; the buyback is that operator's decision each time. A program on Solana can hold the stake instead, in a PDA that is keyless too — but a PDA does what its program says, and a program does what its upgrade authority says, so whether that authority has been burned is a fact to verify per program, per version. Here there is no key and no authority to verify.
No exit.
Routing the slice, bonding it, selling the yield and buying and burning the token are consensus code. The pallet has 8 calls; anyone may send 6 of them, governance the other 2, and none names an account that receives funds. Governance can set the terms and choose the validators. It cannot withdraw, redirect or unbond — there is no call that would. The one transfer to a person is the bounty a call pays whoever sent it, bounded by a term below. Bonk's buyback is a transfer its operator signs, from a wallet that could as easily send the funds anywhere else; a program-held version on Solana is an instruction some authority signs. Either way there is a party who could decide otherwise, and the commitment lasts as long as they do. Here there is no party to decide: the only thing that could stop the loop is a chain-wide runtime upgrade, in the open, by governance.
- compound(launchId) — anyone
- finalizeRetirement(launchId) — anyone
- harvest() — anyone
- retarget() — anyone
- retire(launchId) — anyone
- setTargets(targets) — governance
- setTerms(terms) — governance
- stake(launchId) — anyone
The chain's own yield.
The vault cooperates with validators exactly as any VTRS holder does and is paid the same reward — LNRG, a separate liquid asset, era by era, with the principal untouched. That is what makes the loop sellable: the yield is sold for VTRS and burned into the token without ever unbonding, and what the sale and the burn do is fixed in the runtime — whoever sends the call only decides when. Bonk's yield is validator commission, which reaches the operator as SOL they then spend; the buying and the burning are jobs one party runs, and stop when that party does. A program holding stake on Solana has it harder still: protocol rewards accrue into the stake account itself, so spending yield means deactivating stake and waiting out the cooldown — yield and principal are one pot and every buyback is an unstake. A liquid-staking token moves the question one contract over: the yield arrives as appreciation of the same token, so taking it means selling a slice of the position through a program with its own authority.
What it does not do
- It guarantees no price. A buyback is whatever the yield buys at the venue's price at the time, in slices capped at 0.50% of price impact, which bounds what a sandwich could take from any one of them.
- The yield is whatever staking yields. It moves with the chain's reward rate and the validators' performance; a slash on a target reduces every launch's stake by the same fraction. No rate is promised, and this site computes no APY.
- A dormant launch is retired by a person, never by the keeper. After 90 days without a trade anyone may call retire; the keeper reports it and does not act. The principal unbonds over 5 eras and is then burned into the venue in the same capped slices, until it is gone. Retirement is one-way; a token that revives keeps trading with its slice going to the protocol.
- Launches from before the pallet carry a treasury of 0. Their terms were snapshotted when they were created (5 of 9 here), and a snapshot never changes — for them or for anyone.
- The terms are governance's. The slices, the dormancy rule and the keeper bounds can change for future launches. A creator chooses nothing; a change never touches an existing launch's snapshot.
- Selling the yield needs a buyer. LNRG is sold to the chain's energy broker for VTRS. When the broker is short, the unsold LNRG waits in the vault, attributed to its launch, until it is not. Slow, not lost.
Terms, live
From chain state on every load. The slices are snapshotted into each launch; the rest bound the keeper.
Keeper running as 0xf7f0…E2d2 · last tick at block 1,474,973 · last action payout_stakers era 14749 at block 1,474,925 · 0 unclaimed eras