A dashboard fills. Wallets arrive for a drop or a grant. The count is treated as a town. The crowd is the first story. The week after the last reward is not.
A grant can seed a pool that people actually use. It can also rent balances that leave when the emission ends. I read a campaign the way a stall lease is read: who paid to stand there, and who is still there when the rent stops.
- A crowd is the first reading
- TVL that walks
- Grants that buy a week
- Log I kept for a pool called SEED
- A crowd that stays
- Count who remains after the week
A crowd is the first reading
The problem is easy to name. A foundation spends tokens to pull deposits. The first reading treats the new TVL and the new wallet count as users who chose the product. Many of those wallets are there for the emission. That is a job, not a town.
Is the first reading always false? No. Some campaigns leave a smaller, slower pool that still routes swaps after the drop. The first reading fails when the curve of deposits matches the emission calendar, when the same addresses appear in the next farm the week after, or when “community” is counted on day one of the claim.
My claim is narrow. An airdrop or a grant is a transfer. Retention is a later fact: who is still depositing, swapping, or governing after the transfer stops. Mixing them turns a payroll into a census.
Opinion, not a law for every launch: a leaderboard of claimers is a queue. The pool two weeks later is the room.
TVL that walks
Mercenary capital is a plain phrase. Liquidity sits where the reward is highest this week. It can move in one transaction. TVL that arrived for a rate is allowed to leave when the rate ends. That is not a scandal. It is the job the capital was hired to do.
Question I keep on the page: what share of the peak TVL is still there after emissions fall by half? If the document will not show that window, the growth sentence is early.
Exception: a grant that pays for a public good — an explorer, a keeper, a docs push — may not show up as TVL at all. Do not score it with a pool chart. Score it with whether the good still runs.
Grants that buy a week
Ecosystem funds often buy a burst. A market maker or a farm program posts size. Screenshots look busy. The week is real. The year is a different object.
Observation from public explorers: addresses that claim, dump into the pool, and exit leave a print of transfers. I have lined a claim transaction next to an exit the same day. That pairing is a fact on a page. It is not a verdict on every claimant.
Condition: if rewards vest, the walk can be slower. Vesting changes the clock. It does not, by itself, change why the wallet came.
Log I kept for a pool called SEED
I keep a log for a made-up pool I call SEED. Before the grant: 20 units of TVL. During the four-week emission: 120. Two weeks after the last reward: 28. Claim wallets: 4,000. Wallets that still had a position after day 14: 310.
Question in the margin: what did the grant buy? Answer I could defend: a hundred extra units for a month, and a long tail of three hundred wallets. Not four thousand residents.
Was I looking at a live book? No. SEED is a page. The experience was putting peak and tail on one line. A reader can repeat that pairing on any public pool without taking a position.
Exception I left in the log: if SEED’s swap fees after the grant cover the LP without new emissions, the tail is a product fact. Until that fee line exists, the tail is only a smaller crowd.
A crowd that stays
The first reading works when the tail is close to the peak, when the same addresses keep using the tool after the claim, and when fees—not a second grant—pay the remaining liquidity. It works for that window.
It fails when day-one TVL is framed as proof the product found a town. It fails when a second grant is treated as retention because the chart went up again.
I do not treat a drop in TVL as a command to act. I treat it as a reason to keep hired size and leftover size on two lines.
Count who remains after the week
The solution that holds under the conditions above is a short split, not a slogan.
Write down TVL and active wallets at the start, at the peak, and at a date after emissions fall. Write down whether the leftover earns fees. Note repeat addresses from other farms if a public explorer shows them. If a report will not give the tail date, the community sentence is not ready to stand.
If two dashboards disagree on “active,” say so and stop before the town becomes certain.
The spare thought on the desk is small. A crowd can be real on claim day. The stall can still empty when the rent stops. I count who remains first. I do not call the peak a town because the first reading said the queue had already moved in.
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