A MODEL · NOT A READING

If this holds

three numbers, one float

Every other dashboard here is read from the chain and is wrong only if the chain is. This one is not read from anywhere: it is arithmetic on three numbers you choose. Pick a token, set the revenue, the share of it that buys and burns, and a price — then see what that does to the float over a week, a month and a year.

Protocol revenue, per day$1,000,000Share that buys and burnsdocs say 80% — measured 60–84%80%PONS price, held stilllive$0.4010

$800,000 a day buys and burns 1,995,251 PONS$272,726,457 market cap now

	1 week	1 month	1 year
Burned	$5,600,000	$24,000,000	$272,726,457
Tokens	14.0M	59.9M	680.2M
Of today's market cap	2.1%	8.8%	100.0%
Float left	666.2M	620.3M	float gone
Forward rate on that float	109%	117%	—
Price to hold today's market cap	$0.4094	$0.4396	—

The share of TODAY'S float burned grows in a straight line — at a fixed price the same dollars buy the same tokens every day. What climbs is the rate against what is left: 107% a year against the float today, — against the float a year from now.

The last row is an identity, not a target: with a smaller float, the same market cap has to sit on fewer tokens. At these settings that is $0.4010 today and — in a year — — — and it says nothing about whether the price will get there. It is also an UPPER bound, because the burn above it was priced at a fixed $0.4010: if the price actually climbed on the way, the same dollars would buy fewer tokens, less float would go, and the price needed to hold the cap would be lower than this.

This combination consumes the entire float inside a year, which no market allows: long before the last token there is nobody left to sell one. The figures below are clamped at the float and are past the point where the model means anything.

At this rate the entire float is gone in 341 days.

float and market cap from the collection of 2026-10-05