The plum trees were blooming all at once.

In the past few weeks, the city had decided, finally, to commit to spring. The trees that had been flirting with bloom for weeks were suddenly, fully, in flower - pink and white in every park and along every side street, the kind of bloom that makes you stop on the sidewalk for a second and reorient your sense of what month it is. Old men in the parks set up small folding stools beneath the trees and looked up. Office workers ate their bento on benches that had been empty for months. A small festival of human relief, before the cold could come back one more time.

We met at the bench.

It was the first time we had met at the original bench since November. The wood was sun-warmed for the first time in months. The pond was fully unfrozen, with two koi visible near the surface, lazy and unconcerned. Moolah was already there when we arrived, sitting upright with what looked like a printed PDF on the bench beside her. Three printed PDFs, actually. Stapled. With sections highlighted.

"Today," she said, "we read a whitepaper. Together. Because every other lesson I have given you about how this system works will not protect you if you cannot read this kind of document, and almost no one I know - including most of the people working in this industry - bothers to read them properly. Sit."

We sat.

She handed me the top document. It was a token launch announcement for a protocol I had vaguely heard of - a small DeFi project planning to release its governance token in three weeks. The document was thirty-one pages. Charts. Tables. Long paragraphs in the kind of corporate prose that uses six words where one would do.

"You're going to read this," Moolah said. "And while you do, I am going to tell you what to look for. Because tokenomics - the design of how a token is supplied, distributed, and unlocked - determines almost everything about whether a project is going to make its holders money or take their money. Most of the answers you need are in this document. They are written in plain language. They are also, usually, surrounded by enough other text that almost nobody finds them."

"What am I looking for?"

"Five things." She held up a paw and counted them off. "Total supply. Circulating supply. Allocation. Vesting schedule. And unlock cliff."

"Walk me through them."

She settled in.

"Total supply is the number of tokens that will ever exist. Some tokens have a fixed supply - a number that will never change, like Bitcoin's twenty-one million. Some have a capped supply that increases on a schedule until it reaches a ceiling. Some have uncapped supply - they will keep being printed forever, with the rate set by governance. Each model has different long-term implications. A fixed supply means the value of each token rises if demand grows. An uncapped supply means new tokens dilute existing holders, often sharply. The first question to answer about any token is: what's the total, and is it fixed?"

I flipped to the relevant section. The document said total supply: 1,000,000,000. One billion tokens. Not capped, exactly - the document mentioned that additional emissions may be authorized by governance to fund ongoing development. I underlined that sentence.

"Good. You've found the first lie. Additional emissions means uncapped, with a polite face on it. The total can grow whenever the holders agree, and the holders are mostly the early insiders. Note that. Continue."

"Circulating supply is the number of tokens currently in public hands - being traded, held by retail, available on the market. The rest of the total is held by the project, the team, investors, locked in vaults waiting to be released. The gap between circulating and total can be enormous. If a project says its market cap is fifty million dollars based on a hundred million circulating tokens, and the total is one billion, then ninety percent of the supply is not circulating yet. It will, at some point, become circulating. When it does, the price tends to fall, because supply is going up and demand may not."

I flipped. The document said initial circulating supply at launch: 80,000,000. Eight percent of total. I wrote that down. 92% locked at launch.

"Allocation is who gets the tokens. Look for a pie chart. There is always a pie chart. The pie chart will tell you what percentage went to the team, to investors, to advisors, to the treasury, to community rewards, to the public sale, to the airdrop. The shape of this pie tells you everything about who this project is being run for."

I found the pie chart. Twenty percent to the team. Eighteen percent to investors. Five percent to advisors. Twenty percent to the treasury. Twenty-two percent to community rewards. Ten percent to the public sale. Five percent to an airdrop.

"What do you see?"

"Forty-three percent of the total supply is going to insiders," I said slowly. "Team, investors, advisors. Almost half."

"Good. And how much to the actual public?"

"Ten percent in the public sale. Five percent in the airdrop. Fifteen percent total."

"So roughly three times more is going to insiders than to the public who will buy this token after launch. That ratio is, unfortunately, on the moderate end of what's normal in this industry. It is not unusual to see fifty percent or more going to insiders, with retail getting almost nothing. Those projects are, in essence, designed to enrich their creators at the expense of their later buyers. Sometimes the project is also good. Often it isn't. The pie chart tells you what you're walking into."

I wrote in the notebook. Insider allocation = the silent majority. Forty-three percent here. Often more elsewhere.

"Now," Moolah said. "Vesting. The most important section, and the one most users skip. Insiders' tokens are usually subject to a vesting schedule - they don't get all their tokens at launch. They get them over time. The cliff is the period during which they get nothing, after which a chunk unlocks all at once. The linear schedule is what happens after the cliff - tokens released gradually over months or years."

I flipped. The document had a small table.

Team allocation: one-year cliff, then linear vesting over three years. Investor allocation: six-month cliff, then linear vesting over two years.

"Read those numbers carefully," Moolah said. "Tell me when the team and investors will start receiving tokens, and how much per month after that."

I did the math in my notebook. Team gets nothing for a year. Then over the next three years, twenty percent of total supply is released linearly - about five point six percent of total supply per year, or roughly half a percent per month. Investors get nothing for six months. Then over the next two years, eighteen percent of total supply is released - nine percent per year, three quarters of a percent per month.

"After the first year," I said, "between the team and investors, more than one percent of total supply is being released into the market every month."

"Correct. Now - what is the circulating supply at that point?"

I scrolled. The document had a chart. By month thirteen, circulating supply was projected to be about two hundred million tokens. Twenty percent of total.

"Twenty percent."

"So a one-percent-of-total-supply release each month, against a circulating supply of twenty percent, means new selling pressure equal to five percent of the float every single month. Every month. For years. That is a brutal headwind. The price has to grow faster than that, every month, just to stay flat. Most don't. Most projects, by the end of their unlock schedule, have lost most of their value, because the early holders have been steadily selling into a market that cannot absorb them."

I wrote that in the notebook in capital letters. VESTING UNLOCKS = MONTHLY SELLING PRESSURE. CHECK THE SCHEDULE BEFORE BUYING.

"And cliffs - single-day unlocks where a large chunk releases at once - are the worst. There are projects where, on a specific date, ten or fifteen percent of total supply unlocks for insiders all at once. The chart of those tokens almost always shows a sharp drop on the unlock day, because insiders sell aggressively, and there is no buyer base big enough to catch the volume. You can predict these drops weeks in advance, if you bother to read the schedule. Almost no one does. The information is publicly available in the document. The information is, by all rights, free."

"Why doesn't anyone read these?"

"Because they're long, and dull, and full of legalese, and the price of the token has been going up, and the social media is exciting. The whitepaper is the nutrition label on the back of the cereal box. Nobody reads it. Everybody should. The cereal is sometimes mostly sugar. The label, if you read it, will tell you."

She tapped the printout.

"There are other things to look for. Treasury allocations - how much of the total supply is held by the project itself, and what governance rules apply to spending it. Burn mechanisms - whether tokens are removed from circulation when used. Staking incentives - whether holders are rewarded for not selling, which can mask inflation. Liquidity provisions - how much liquidity the team has committed to the trading pools, and for how long. All of this is in the document. Written out, in the cool dry tone of a corporate filing, for anyone who cares to look."

I flipped through the rest of the document with new eyes. The numbers I had glanced past on the first read now jumped out at me. The footnote that said the treasury could be deployed at the discretion of the foundation. The line, near the end, that said the project reserves the right to modify the emission schedule subject to governance approval. The chart in the appendix showing that, at year five, fewer than half the originally promised tokens would be in retail hands.

"This is depressing."

"It's clarifying. You can now read this document in twenty minutes and tell me, with reasonable accuracy, whether this token is likely to be a good long-term hold. Twenty minutes. The information is free. Most people who buy this token at launch will not have spent twenty minutes."

"And what do you think of this one?" I asked. "Specifically."

"I think it's mediocre," she said. "Not the worst I have seen this month. Not the best either. The insider allocation is high. The vesting is reasonable. The team has shipped a working product. The treasury controls are weak. I would not buy at launch. I would consider buying after the first major unlock, if the price has corrected and the protocol is still showing real usage. That is a hypothetical. I am not telling you to buy anything. I am telling you that I read the document and have a view, and that my view is informed by the same five things I just taught you to look for. Total. Circulating. Allocation. Vesting. Cliff. That's the whole framework."

I wrote it down one more time in capital letters across a fresh page.

The breeze came up. A few plum petals drifted down past us. A small group of school children walked past on the path, a teacher pointing up at the trees.

"That's the end of Part Three," Moolah said.

"Of what?"

"Of your education. You now understand the deeper machinery. Oracles. Bridges. Layer 2s. MEV. Derivatives. Tokenomics. You can read a project, see how it's built, and judge whether you trust it. You won't always be right. But you will be informed."

"And next?"

She looked across the pond. The koi were still visible. The afternoon was getting long. Somewhere across the park, a temple bell rang once.

"Next," she said quietly, "we tell the stories I have been promising you all winter. The disasters. The hacks. The weekends. The losses that taught the industry everything it knows. Spring is here, and it is time."

"Where do we start?"

"At the beginning. With a single bug, in a single contract, in the summer of 2016, that nearly killed Ethereum in its cradle. They called it The DAO. We will start there. And then we will work our way through the history of every catastrophe that mattered, in order, and by the time we are done you will understand why this industry is the way it is. Bring the notebook."

I always brought the notebook.

She slipped off the bench and padded toward the pond, but this time, before sliding in, she paused at the edge and looked back at us. The afternoon light caught the top of her head. She looked, for a moment, very old.

"Some of these stories are going to be hard to hear," she said. "I want you to know that in advance. I am going to tell them anyway."

She slipped into the water.

End of Part III. Next: Part IV begins with Episode 21 - The DAO Hack (2016): The Original Sin.