A float looks small. A cliff date arrives. Transferable tokens are treated as coins that already hit the book. The quiet percentage was the first story. The locked pile was not.
A cliff can hold a team in place for a year. It can also open several buckets on the same morning. I read a vesting table the way a lease is read: not as a price, as a calendar of when keys change hands. The page still printed a thin ring of coins in public hands. The schedule under it did not match that ring.
- Quiet float is the first reading
- One door or a drip
- What circulating is allowed to mean
- Table I opened on a Tuesday
- A cliff date that stays only a date
- Count the keys before you count the day
Quiet float is the first reading
The problem is simple to state. A launch table shows a modest share already moving. That share is called circulating. The rest sits in lockups with names like team, early backers, or ecosystem. The first reading treats the modest share as the whole room.
Is that reading wrong on every project? No. After most of a supply has already vested, a later date can be a small step. The first reading fails when the locked share is large, when two or three buckets share one calendar day, and when circulating is defined more narrowly than “can be sent.”
My claim is narrow. A cliff does not invent coins out of air if those coins were minted at genesis and parked. It changes who is allowed to move them. New minting is a different tap. Mixing the two inflates the story or shrinks it, depending on which number you wanted to win.
Opinion, not a rule for every chain: the pie chart on page four is a costume. The vesting appendix is the room.
One door or a drip
A cliff is a stretch with no release. Then a door opens. Some schedules open a quarter of a bucket on that morning. Some open the whole bucket. After that, the remainder may drip by day, week, or month.
Linear vesting is the drip. The same quantity becomes movable on a steady clock. A document that says “linear monthly” is not the same object as a document that says “linear each block.” One is a small door twelve times a year. The other is a thin stream that never makes a headline.
Does a drip press supply? It can, if the daily slice is large next to what already moves in a day. It can also vanish into noise if the slice is small and the recipients stake, hold, or keep the coins in a treasury that does not sell. The schedule tells you the keys. It does not tell you the hands.
Hybrid is the common furniture. Twelve months of nothing. A first slice. Then two or three years of drip. The failure mode I watch is not the drip. It is two cliffs stacked on one date so the door is wider than any single label admitted.
What circulating is allowed to mean
Circulating, total, and max are not one noun.
Circulating is the stock treated as movable now. Total is what already exists, including coins that cannot yet be sent. Max is a cap, if the design has one. A wide gap between circulating and total is not a scandal by itself. It is a reason to open the calendar.
Unlock is not the same act as a sale. A contract that lifts a transfer limit has done one job. The next job — send, stake, lock again, sit — belongs to an address. I have watched explorer rows where a cliff passed and the coins moved into another multisig, not onto a book. That row is not a character reference. It only keeps two verbs apart: unlocked, and sold.
A short model helps, and it has a limit. Event dilution can be written as U divided by C, where U is the quantity that becomes movable on that date and C is circulating just before the date. If U is 90 million and C is 150 million, the ratio is 0.6. That is a structural sentence about stock. It is not a sentence about a print. The limit: the ratio assumes the stated C is honest, and circulating figures are often argued over. If a dashboard counts staked coins one way and an official post counts them another way, the same U produces two different stories. Say which C you used.
On a drip, a rough yearly rate is the daily slice times 365, then divided by current C. As C grows, the same slice becomes a smaller percentage. That is arithmetic, not a forecast.
Table I opened on a Tuesday
I keep a scratch page for a made-up token I call ALPHA. Max 1,000 million. Circulating at the start of the exercise: 150 million. Team and early backers share a twelve-month cliff. On that morning the table releases 40 million from one bucket and 50 million from the other. Same date. After that, 12.5 million a month for twenty-four months.
Question I wrote in the margin: what actually changes at sunrise? Answer I could defend: transferable stock can rise from 150 million to 240 million if every unlocked coin is counted as circulating that day. The ratio is sixty percent of the prior float. The drip that follows is about 12.5 million a month against a larger C, so the monthly percentage falls even if the absolute slice does not.
Was I looking at a live book? No. ALPHA is a worksheet. The experience was the act of lining the buckets on one line and noticing the doors coincided. That is the kind of mistake a pie chart hides. It is also the kind of mistake a reader can repeat on any public appendix without taking a position in the asset.
Exception I left on the same page: if the team slice cannot be sent until a second contract says so, the calendar date is not the circulating date. Read the lock contract, not only the appendix prose. I have opened a public explorer, searched a vesting address, and found a release timestamp that did not match the marketing sentence by several days. The contract won. The sentence lost.
A cliff date that stays only a date
A cliff date is just a date when the recipients already hold, restake, or move coins into another lock. It is just a date when U is tiny next to C. It is just a date when the only bucket opening is a treasury that does not sell under its own policy — though policies change, and a policy is not a lock.
The first reading (“the float is the room”) works after most keys have already been handed over. It works when later events are smaller than one percent of circulating, if that circulating figure is stable and defined the same way twice. It fails when the quiet ring was a costume for a large, aligned door.
I do not treat a large ratio as a command to act. I treat it as a reason to keep the two verbs apart and to ask who received the keys. Recipients matter. A drip into a broad user set is not the same furniture as a door that opens for a short list. That is structure. It is still not a print.
Count the keys before you count the day
The solution that holds up under the conditions above is a short checklist, not a slogan.
Write down C and the definition that produced it. Write down each bucket, its cliff, its drip, and whether two doors share a morning. Compute U divided by C for the next discrete event. Keep minting on a separate line. Keep burns on a separate line if they exist; future burns are often a wish. Then look, on a public explorer, whether the lock address can actually send on that morning.
If a document will not name the dates, the page is not ready to stand. If a dashboard and a document disagree, say so and stop the sentence before it becomes certain.
The spare thought I leave on the desk is small. The quiet float can be true for a while. The cliff date is still on the wall. I count the keys first. I do not count the day as a sale because the first reading said the room was already empty.
The articles on this site are not investment recommendations or financial advice. They are structural analysis based on on-chain data and project documents.
Comments
Post a Comment