Read It Like You're 85: The Case for a Plain-English Stamp on Token Contracts
Photo: grandmother looking confused at laptop screen financial documents, via as2.ftcdn.net
There's a moment familiar to anyone who has walked a relative through their first token purchase. You get past the wallet setup. You get past the seed phrase speech. Then your mom, or your uncle, or in my case your 84-year-old father-in-law from Ohio, squints at the screen and asks the question that ends every conversation: "What does all this fine print actually say?"
And the honest answer, more often than not, is: nobody's entirely sure.
The Readability Problem Nobody Priced In
Traditional finance has spent decades building disclosure machinery. Mutual fund prospectuses, for all their flaws, follow standardized formats. FINRA rules force brokers to communicate risk in ways regulators can audit. Mortgage lenders got the "know before you owe" treatment after 2008.
Crypto, meanwhile, has produced thousands of token launches where the governing document is a smart contract written in Solidity and the marketing material is written by — increasingly literally — a language model optimizing for hype. Neither was designed to be understood by the person actually clicking the mint button.
"The gap between what a contract does and what a retail buyer thinks it does is the single biggest consumer-protection issue in this space," says a former SEC enforcement attorney I'll call Dale, who now consults for DeFi projects and asked not to be named discussing clients. "And nobody's measuring it."
What Would a 'Grandma Test' Actually Look Like?
That question sent me down a rabbit hole. If the industry won't get a disclosure mandate, could it get something like a voluntary standard — the crypto equivalent of the Good Housekeeping seal?
I brought the idea to Dr. Priya Raman, a computational linguist at a Midwest university who studies how ordinary readers process financial text. Her take: the problem isn't just jargon. It's structure.
"Legal crypto documents bury the three things that matter — what can go wrong, who controls the keys, and what happens if the team disappears — under twelve paragraphs of roadmap optimism," she told me. "A readability test has to check whether those three facts appear early, in plain sentences, with the risk stated before the promise."
From those conversations, a working checklist emerged. Call it the family dinner test. A project passes if:
- The one-sentence summary is actually one sentence. A buyer should be able to state what the token does without using the words "revolutionary," "ecosystem," or "synergy."
- Risks come before rewards. Not in a linked appendix. On the first screen.
- The admin keys are explained in human terms. Who can change the contract, and can they take your money? Yes or no.
- No sentence over 25 words in the risk section. Long sentences correlate with buried caveats.
- A fifth-grade reading score on the risk disclosure. Not the whole document — just the part that tells you how you can lose everything.
The Objection: Simplicity Isn't Simple
Pushback came fast when I floated this to founders. Smart contracts do complicated things. Compressing that complexity into plain English, they argue, either oversimplifies or misleads.
Raman doesn't buy it. "Pharmaceutical labels handle molecules. Insurance disclosures handle actuarial tables. Complexity is never an excuse — it's a design constraint." The trick, she says, is layering: a plain-language summary up front, with the full technical spec one click deeper for people who want it.
Dale is more skeptical, but for a different reason. "Voluntary standards only work when there's a market penalty for skipping them," he says. "Right now, the market rewards hype density, not clarity. A readability badge is worthless if the projects that fail it raise more money."
Where AI Cuts Both Ways
Here's the twist for a site like ours: the same generative tools flooding launchpads with boilerplate whitepapers could also be the thing that fixes this. Every major model can now rewrite a risk disclosure at a fifth-grade reading level in seconds. The technology to pass the family dinner test is free and sitting on every founder's desktop.
What's missing is the incentive. And that, ultimately, is the argument of this piece: clarity is a choice, and right now the industry keeps choosing not to make it.
Until a launchpad, exchange, or auditor starts refusing to touch projects that flunk a basic readability screen, the fine print will keep doing what fine print does best — staying fine.
My father-in-law eventually bought a small bag of ETH anyway. He asked me to explain the gas fee, I did my best, and he nodded along the way you do when a teenager explains TikTok. "So nobody has to tell me the truth in words I understand," he said, "and that's legal?"
Yeah, Pops. That's legal. For now.
The checklist above is a starting point, not legal advice. If a project publishes something that passes it, send it our way — we'll keep a running tally.