Tokens as infrastructure, not hype

A token earns its keep when the network breaks without it. Everything else is decoration.

Try the test on a few tokens you know. If ETH disappeared tomorrow, Ethereum stops. Validators have nothing to stake, gas has no denomination, and the chain has no economic floor. LINK? Chainlink oracles stop relaying prices because node operators stop getting paid in the asset whose accuracy they guarantee. MKR? MakerDAO loses its backstop for DAI and governance turns into opinion rather than decision. Each of these tokens has a job. Remove the token, remove the job.

Now try it on the launches that filled the last cycle. Most fail the test. The token existed to coordinate one behaviour: buy it, hold it, wait for the number to go up. That is not coordination. That is a shared spreadsheet hoping to become a Schelling point.

LooksRare is the canonical case. The protocol rewarded users for trading on the marketplace. Users traded with themselves. Hacken's analysis puts wash trading at around 90% of volume at peak, with users acquiring $LOOKS rewards worth more than the trading fees they paid, then dumping the tokens. The protocol paid people to simulate using the product.

Airdrops often fail the same test. Reward wallets for existing, give the token no post-distribution function, and recipients sell on day one. The protocol has subsidised the creation of its first cohort of sellers. The polite industry framing is "misaligned incentives." The operating framing is that the team paid strangers to become a headwind on the chart.

Good token design starts from the behaviour side. Pick the behaviour the network needs and cannot manufacture any other way. Validators signing blocks. Liquidity providers accepting inventory risk. Oracle nodes reporting prices under threat of slashing. Curators vouching for content with skin in the game. Any of those behaviours has a cost that has to be paid for. A token makes sense when it is the cheapest honest way to pay for it.

The question every founder needs to answer, before tokenomics, before distribution, before the launch post on X: what specific behaviour does this token pay for, and what breaks if nobody performs it? If the answer is "we need liquidity" or "we want a community," the token does not exist yet. Those are outcomes, not jobs.

Once the behaviour is defined, the rest of the design follows. Supply is a function of how many actors need to be paid over what horizon. Distribution goes to the actors doing the work, not to the team's Twitter mutuals. Vesting reflects the timescale over which you need the behaviour sustained. Emissions taper as the network starts paying its own costs from usage. MiCA now pushes EU-regulated platforms to verify reasonable vesting mechanisms for team and insider allocations, which sharpens the conversation on distribution without solving the design problem.

Narrative matters after the design works, not before. The strongest Web3 narratives come from protocols where the token passed the behaviour test early and accrued a story over years of operation. ETH's story is the decade of operation. Chainlink's story is the oracle network that survived three bear markets while paying its operators in its own token. Those stories were not marketing. They were what happened.

The weakest narratives come from projects that did it backwards. Story first, behaviour never. The token was announced, the launch was staged, the memes went out, and the actual job the token was meant to do was missing or confused. When those projects got delisted, rug-pulled, or quietly retired, the retrospective read the same every time: the token was a wrapper around a hope.

If you are about to launch one, the cheap test is this. Draw the protocol without the token on the whiteboard. If it still works, you do not need the token. Ship the protocol. If the protocol breaks, mark the exact point of failure. That is where the token's job lives. Design from that point outward. Everything further from it is decoration.