Watch: TTTRMNL, a trading terminal for Ten Thousand Tokens by TokenWorks

The transparency probe, updated with the creators' own post-mortem: the contracts worked, the network effects didn't, and the protocol runs for as long as Ethereum does. Plus the full interface argument in prose.

  • tokens
  • nft
  • burn-mechanics
  • video

The TTTRMNL promo, in under two minutes. The write-up below is the argument the video is making, in prose, because the transparency probe deserves both.

The thesis under test: radical legibility is a feature, not a leak.

tttrmnl.xyz · GitHub

The premise

Ten Thousand Tokens is an NFT protocol where each of the 10,000 NFTs can be burned, permanently, to launch its own ERC20 token. Every burn shrinks the collection and grows the token economy. Hold or burn is the whole game. Every token launched kicks fees back to the remaining NFT holders, so launching means forfeiting your share of everyone else's fees in exchange for half the creator fees on your own.

That is a genuinely novel game state, and it runs on all three of the machine's materials at once. Persistence: a burn is forever, which is precisely what makes the decision mean something. Shared state: the remaining supply is a fact every player reads identically, not a rumor. Provenance: the chain remembers who burned early, who held through everything, who launched what. Game states this rich deserve better than a mint button and a Discord. They deserve a terminal.

Why Bloomberg, on purpose

Traditional finance treats information asymmetry as the product. The terminal on the trading desk exists because seeing more than the other guy is worth $25,000 a year. Onchain systems invert the economics: everything is already public, so the edge stops being access and becomes interface. Whoever renders the shared state most legibly wins.

So TTTRMNL is a deliberate act of interface strategy (the founding essay files this under Heresy 3). A Bloomberg-grade terminal for a burn game says: this is a system worth taking seriously, here are its rules, here is its state, decide like a professional. The same data in a minting page with a progress bar would produce different behavior entirely. The interface is the strategy.

What I built

Terminal: protocol overview and live game state: supply remaining, burn rate, launch activity Simulator & Burn Center: hold-vs-burn math, per-NFT burn-readiness checklists, and scenario projections at 9k / 5k / 1k / 100 / 10 NFTs remaining Token explorer: every launched ERC20 with charts, watchlists, and per-token drill-downs (135+ launches and counting) Portfolio & Leaderboards: ERC20 holdings, cumulative launcher fees, and rankings for top burners, diamond hands, whales, early burners, and final bosses Alerts: subscriptions and an in-app feed so you don't miss the protocol moving

The leaderboards are provenance made social. "Early burner" and "diamond hands" are not marketing labels here; they are queries against history the chain already kept. Status you can verify is a different product primitive than status you assert.

Wallet connection via RainbowKit, with disclaimers that never leave the screen: estimates only, burning is irreversible, not financial advice.

The creators' own verdict

Analysis is cheaper when the builders grade their own work, and the Ten Thousand Tokens team published an unusually honest post-mortem. Read it. It is the rare crypto retrospective that names its own mistakes without a pivot announcement stapled to the end.

Their verdict, in short: the protocol failed on volume. The contracts worked, the site launched clean, 100+ tokens deployed on day one and one touched a $1m market cap, but the network effects never arrived. Ten thousand NFTs were probably too many shots on goal, so the fees accruing to each holder felt demoralizing rather than motivating. And the dynamic buy tax they borrowed from TokenStrategy (99% scaling down to 1%) was solving the opposite problem: TTT needed more buyers, not fewer, and the tax added friction exactly where the protocol could least afford it.

Through the product lens, those are three different failure types worth separating. The supply size is an economy-design miss: incentive density matters more than total surface area. The buy tax is a mechanism transplanted without asking what problem it solved in its original home, which is the crypto equivalent of cargo-culting another company's onboarding flow. And the volume problem is the honest one: they refused to over-promise, tweeted their doubts live, and the market did what markets do to projects that won't lie to it. The founding essay calls the casino a church for a reason; it tithes marketing, not mechanics.

But note what did not fail, in the team's own words: "The protocol will still exist for as long as Ethereum does, as it's fully onchain and permissionless. We hope people will still launch on it, as the mechanics still work (even if the network effects didn't.)" That sentence is why TTTRMNL exists. The game state is intact, the rules still execute, and anyone can build a better window into it. Same lesson as the OEGP resurrection: onchain, a dead platform is not a dead product. It is an open invitation.

What I learned

Legibility changes behavior. When holders can actually see the game state (how many NFTs remain, what burns are projected to do, what launched tokens are doing) they stop asking "what's the floor" and start reasoning about strategy. That held even as the protocol's volume fell short; legibility could not manufacture network effects, but it changed how the holders who stayed thought about the ones they held. The floor question is the casino's question, and it turns out people only ask it when the interface gives them nothing better to think about.

The industry-wide version of the lesson: most "degen" behavior is not a personality trait, it is a UI outcome. Give people a slot machine interface and they pull the lever. Give them a terminal and they start doing analysis. If the next cycle's products want better users, they should start by building interfaces that assume users can think. When a protocol is a game, the winning interface is the one that makes the rules visible.