White paper
The more they talk.
The less exists.
$WASTED is a Solana token that burns itself every time the internet talks about GTA. Every eligible public post on X that mentions GTA burns 100 $WASTED. Nothing can ever mint. No respawns. No reminting.
The burn
Time is cut into five-minute windows that close on the clock: :00, :05, :10 and so on. When a window closes, the worker asks X for the exact number of eligible posts made inside it. That count × 100 is the number of $WASTED burned for the window. One burn transaction per window, settled on-chain about two minutes after the close.
What counts
(#GTA OR GTA6 OR #GTA6 OR GTAVI OR #GTAVI OR "GTA 6" OR "GTA VI" OR "Grand Theft Auto") -is:retweet -is:reply
- Case-insensitive. Hashtags are exact matches, quoted terms are exact phrases, GTA6 and GTAVI are whole words.
- Bare "GTA" is not counted. It is too noisy (Greater Toronto Area, car models).
- Reposts and replies are excluded. Quote posts count.
- The rule is published and frozen before launch. Its hash is written into every window on-chain, so a silent change is impossible.
Timing
A post made at 14:01 falls in the 14:00–14:05 window and burns at roughly 14:07. The exact delay depends on when X makes the counts available, how fast the transaction confirms, and whether a backlog is clearing.
Missed windows
Windows settle in strict order. If X cannot provide a complete count for a window, the window waits and is backfilled, and the ledger says so. If a window is still uncounted after seven days it is recorded as missed, with the reason. A window can never be skipped silently.
Post & Burn
The live screen has one button: a crimson flame. It signs you in with X and posts from your own account through the $WASTED app, so authorship is a fact, not a claim. A live post burns 25,000 $WASTED instead of 100.
- The post must contain a GTA phrase from the rule above and tag @GTA__WASTED. No links.
- Once per account per 24 hours.
- Your stamp is pinned to the wall for 24 hours with your handle and −25,000, and links to the post.
- The Pyro Leaderboard ranks the top 10 Post & Burn accounts of all time. It never resets, and only accounts that posted through the site appear on it.
Under the hood a live post enters the burn program as 250 mention-units, so the per-window cap, the backlog and the empty-wallet rules apply to it unchanged, and the window record shows live posts separately for auditing. Sessions last two hours. Nothing about you is kept beyond the posts you made.
Token
| Ticker | $WASTED |
|---|---|
| Chain | Solana, launched on pump.fun |
| Supply | 1,000,000,000, minted once. Mint authority revoked; no mint function exists in the burn program. |
| Burn Wallet | 300,000,000 (30%), bought by the creator at launch and deposited into the Burn-Only Wallet. |
| Trading | 700,000,000 |
| Burn per post | 100 · Post & Burn 25,000 |
| Tax | 0% token tax. Trading and network fees are separate. |
Where the burns come from
Burns come from the Burn Wallet, never from your wallet. It is a token account owned by the burn program. It has exactly one instruction: burn. No transfer, no withdraw, no close, no key that can move it.
Creator fees
pump.fun's creator fee is split 50/50 on-chain and the split is locked once set:
50% · Operational Wallet
Runs the project: the X API bill, hosting, the worker, and the people. It never touches the burn program.
50% · Buy & Burn
Swapped for $WASTED on the market and burned in the same transaction. Nothing bought ever sits in a wallet.
One transaction, buy and burn
Every hour the worker distributes the creator fees (pump.fun pays the Operational Wallet its half on-chain) and then sends one transaction: swap the buy & burn half into $WASTED, deliver it to the program-owned buyback account, and call burn_buyback, which burns that account's entire balance. The burn is the last instruction of the same transaction, so if it cannot run the swap is rolled back with it. There is no moment where bought tokens exist and are not yet burned.
Burn Wallet (300M) → GTA mentions → burns, 100 per post
Creator fees → 50% Operational Wallet · 50% buy $WASTED → burn (one transaction, every hour)
PHASE 2 · FEE-FUNDED (after the 300M has burned)
GTA mentions keep being counted and queue as a public backlog
Creator fees → 50% Operational Wallet · 50% buy $WASTED → burn, and each burn pays the backlog down
When the 300M is gone, mentions queue and fees pay them down. Nothing is minted to cover them. Every buy & burn credits the backlog with the mentions it covered, so the ledger always shows what is owed and what has been paid. Supply only ever goes down.
The burn program
One Solana program, one vault. The worker tells it how many mentions a window had; the program decides how much it is allowed to burn and burns it.
- Burn only. The program has two instructions that move tokens,
burn_epochandburn_buyback, and both destroy them. No transfer, withdraw or close. The burn wallet and the buyback account can only shrink. - Atomic buy & burn.
burn_buybackburns the whole balance of the program-owned buyback account and fails if it is empty, so a swap that delivered nothing fails with it. It records tokens burned, SOL spent and the number of buy & burns on-chain. - Per-window ceiling. At most 2,500 mentions' worth (250,000 $WASTED) per five-minute window. Demand above the cap carries to the next window on-chain as a backlog, so nothing is lost and nothing is rushed.
- Oracle-signed, in order. Every window is signed by the oracle key and settled in strict sequence. The same window cannot be submitted twice.
- Timelocked admin. Changing the oracle key or the cap takes a 48-hour timelock, visible on-chain before it lands. No admin instruction can move tokens.
- Immutable at launch. After review and verification the upgrade authority is removed, so the rules above can never change.
- Worst case is bounded. A leaked oracle key can only burn the burn wallet faster, up to the cap. It cannot send tokens anywhere.
Oracle & the X API
The oracle is one off-chain worker. Every 30 seconds it looks for a window that has been closed for at least two minutes, fetches X's minute-granularity counts for it, requires all five buckets to be present, sums them, and submits one burn per window in order. It records every receipt to the public ledger.
Why counts, not posts
X's counts endpoint returns the exact number of posts matching the rule in a time range, in one request, for half a cent. That makes the count cheap, deterministic and reproducible by anyone with an X developer account. It also means the oracle counts aggregate posts; it does not keep a per-post list, and it cannot remove duplicate authors or coordinated spam from the count. Post & Burn is the one path where individual posts are verified, because they are published through the app.
Budget: 100 USD a month, public
| Item | Cadence | USD / month |
|---|---|---|
| Burn count, one request per window | 288 / day | 43.20 |
| Post & Burn (post + check) | on demand | up to 20.00 |
| Daily receipt, a milestone post per 1% of supply burned (max 2 a day) and four one-off moments | 1–3 / day | ~6.50–7.50 |
The worker keeps a spend meter. The rest of the month's counts are reserved up front and are never skipped. Post & Burn has its own pool and pauses first if the month runs short. The meter is published on the audit panel of the live screen.
Audit
Everything needed to check a window is public.
- The ledger. One row per window: window number, time, mentions, burned, backlog, transaction and status (OK, backfilled, exhausted, missed). Plus one row per buy & burn: SOL spent, tokens burned, transaction. Published as JSON and shown on the live screen under Ledger & audit.
- The evidence record. For every window: the window bounds, the rule and its hash, the count, the amount burned and the transaction.
- The Burn Wallet. Its address is on the live screen with a Solscan link. Its balance can only go down.
- Reproduce any window yourself. One request to X's counts endpoint, same rule, same window, add the five buckets:
curl "https://api.x.com/2/tweets/counts/recent?query=(%23GTA%20OR%20GTA6%20OR%20%23GTA6%20OR%20GTAVI%20OR%20%23GTAVI%20OR%20%22GTA%206%22%20OR%20%22GTA%20VI%22%20OR%20%22Grand%20Theft%20Auto%22)%20-is%3Aretweet%20-is%3Areply&granularity=minute&start_time=2026-11-19T00:00:00Z&end_time=2026-11-19T00:05:00Z" \
-H "Authorization: Bearer $X_TOKEN"
Compare the sum with the ledger row. The window's hash of the rule is on-chain, so you can also confirm the oracle used the published rule and not another one.
Risks, honestly
- Trust in the oracle. The program limits and records what the worker submits, but it does not independently verify X's counts. The cap, the ordering and the public ledger bound the damage; they do not remove the trust.
- X can change. Pricing, rate limits or the counts endpoint can change. If counting becomes impossible, windows are recorded as missed, not invented.
- The burn wallet can run dry. GTA mentions do not generate money. If trading does not fund enough buybacks, burns wait. Continuous burning is not guaranteed.
- Fee custody. The 50/50 split is enforced by pump.fun's on-chain fee sharing; the buy & burn transaction is built and signed by the worker. Creator-fee SOL is not protected by the burn-only vault until the moment it is swapped, at which point the tokens can only be burned.
- Software fails. A late worker shows as a late window, a failed swap as a missed buy & burn. Never put in more than you can afford to lose.
$WASTED is an independent fan-made project. Not affiliated with, endorsed by, or connected to Rockstar Games or Take-Two Interactive. "GTA" is referenced only to describe which public posts are counted. Nothing here is an offer to sell anything.