A burn announcement with a transaction hash attached is the strongest claim in this industry. Anybody can open it, the tokens are at an address nobody holds a key to, and the arithmetic is finished. Aster publishes one every fortnight and both transactions in its most recent post are precisely what the post says they are — this desk read them from a BSC node before writing a word about them.
And the supply anybody can trade did not move. Not because the burn was fake, small or double-counted, but because of where the tokens came from. That is a distinction the announcement does not draw, the aggregators do not carry, and the arithmetic makes unavoidable once you ask it.
What the announcement says
[ $ASTER Buyback and Burn Update ] From 2026-08-10 00:00 UTC to 2026-08-24 00:00 UTC, 99% of daily platform fees were used to buy back 4,246,162.43 $ASTER for stakers. A matching 4,246,162.43 $ASTER has been burned from the team allocation. Burn tx: https://t.co/hx7HK4HWNB A
Two burns, not one. The first is the fortnight’s matched burn: platform fees bought $ASTER for stakers and an equal quantity was destroyed. The second is a one-time reconciliation covering fees denominated in $ASTER over the two months before it. Each names its own transaction, and the post closes with two cumulative figures and a staking yield.
The cumulative figure is the one worth testing first, because it is the only number in the post this desk can check by a route that does not go through Aster. The burn destination is a public address; its balance is a chain read; and a project’s stated lifetime burn should equal what sits there.
The two transactions, and where they came from
Both transactions end at the same place: the conventional dead address, which has no key and never gives anything back. Both start at the same place too, and that is the part the announcement leaves out.
Burn | Time (UTC) | Amount | From |
|---|---|---|---|
Reconciliation | 24 Aug 05:48:45 | 2,918,425.19 | Team allocation |
Fortnight’s matched burn | 24 Aug 05:53:29 | 4,246,162.43 | Team allocation |
The sender is a multisig with eight transactions in its lifetime. CoinGecko labels it Team in its own supply breakdown for $ASTER; this desk’s register calls it team and advisors and subtracts it from the float. Two parties who do not consult each other put the same name on it, which is worth more than an explorer tag would be — BscScan carries none.
The register holds five allocation addresses for this token, and the pair of daily readings that brackets the burn settles the question on its own. Across it, exactly one of the five moved. It fell by 7,164,587.62. The dead address rose by 7,164,587.62. The other four did not move at all, and the contract’s reported total supply — eight billion — did not move either, because on this chain a burn is a transfer rather than a decrement.
Two balances moved by the same amount in opposite directions, and neither of them was circulating.
Aster says this itself
Tokenomics | Asterdocs.asterdex.com
None of the above is a discovery. Aster’s tokenomics page states the rule plainly: for every token bought back, an equal amount is burned from reserve, with the team allocation burned first. The same page says all bought-back $ASTER is distributed to veASTER stakers. Both halves of the programme are documented, and this desk found them by reading the chain and then confirmed them against the documentation rather than the other way round.
Which means the mechanism is exactly as advertised and its effect on float is still nil. Follow the tokens. The buyback takes them off the market and hands them to stakers — they are not destroyed, and a staker can eventually sell. The burn takes them out of an allocation that was never on the market and destroys them. Neither leg removes a tradeable token permanently, which is what a burn is usually assumed to do.
Why a reader is entitled to assume otherwise
Because that is what the word does everywhere else. A burn of tokens bought on the open market is the version most programmes run and the version the term was coined for: supply that was trading stops existing. Burning reserve is a different operation with the same name — it lowers the ceiling rather than the floor, and it is a real commitment about the future. It is simply not a reduction of the present.
What moved the float instead
This desk holds daily chain readings for $ASTER over the ninety-one days to 24 August, each one recording the total supply, the balance at every registered allocation, and the balance at the dead address. That is enough to take any day apart into the three quantities a float is made of, and to add them up over the window.
Allocation | Change over the window | Where it went |
|---|---|---|
Airdrop distribution vault | −95,088,036 | into circulation |
Team and advisors | −11,086,108 | burned |
Ecosystem distributor | −6,750,000 | into circulation |
Treasury | 0 | — |
Ecosystem vault | 0 | in and out the same day |
Change in circulating supply | +101,838,031 | up 4.45% |
The second row is the burn, seen from the other end. Over the same window the dead address gained 11,086,113 tokens and the team allocation lost 11,086,108 — five tokens apart on eleven million, which is two independent balances describing one movement. Nothing else came out of that allocation: it is being spent entirely on burning.
The tokens that reached the market came from two other allocations, and the larger of them by far is the airdrop vault. Nine times more supply entered circulation from there than the burn programme destroyed from anywhere — so a reader watching the burn is watching the smaller of two forces acting on the same number. That is the ordinary case rather than the scandalous one, and it is invisible unless somebody measures each account separately.
Show the figures as a table4 rows
| Month | Burned | Issued | Unlocked |
|---|---|---|---|
| Jun | $2M | $0 | $59M |
| Jul | $3M | $0 | $0 |
| Aug | $7M | $0 | $0 |
| Sep | $3M | $0 | $0 |
The index’s own twelve-month figure for this token is below, computed by the same daily pipeline that serves the ranking. Where it shows no number, the figure is being withheld rather than filled in.
A sixth of the supply sits inside Aster’s own venue
One account holds more $ASTER than any allocation except the airdrop vault, and it is not an allocation at all. BscScan tags it Aster’s deposit bridge: the tokens users send in to trade on the platform, mixed with the balances they have staked, because staking runs on Aster’s own chain and only the bridge is visible from BSC.
This desk counts it as circulating and prints it on its own line on the token’s page. Subtracting it would declare somebody else’s trading balance non-circulating, which is done nowhere on this site and by no aggregator. What cannot be resolved from this chain is how much of it is staked and therefore locked — so that is stated rather than split on a guess. Over the same ninety-one days it took in 168,060,923 tokens — more than left every allocation put together, and fifteen times what the burn destroyed.
What we could not check
The burn half of this programme is verifiable and verified. The buyback half is not, from the address Aster publishes for it.
The tokenomics page names a buyback wallet. On 24 August it held $451 across two assets. The $ASTER half of that is 25.447270978945667736 tokens, and four archive readings taken between 13 July and 24 August return that figure to the last decimal place — the balance has not moved at all in six weeks. An earlier reading on 24 June stood a third of a thousandth of a token lower, which is the only movement in it this desk can find. It has never sent a transaction.
What to use
For $ASTER, the figure that answers "will I be diluted" is the circulating supply and its direction, not the cumulative burn. The two point opposite ways over the same window and both are true. A buyback that does not burn and a burn that does not touch the float are each a real commitment about the future; neither is a reduction of the present, and quoting either as one is where the arithmetic goes wrong.
Every figure here was read on 24 and 25 August 2026. Supply figures age, and this article states its date for that reason rather than as a formality — the programme burns on a fortnightly cadence and the allocations vest continuously, so both columns of the table above will have moved, in the same directions, by the time this is quoted.
Where these numbers come from
The chain readings behind this article are the same ones that serve the net supply ranking, collected under the published methodology from the sources listed on data sources. The two transactions and the balances either side of them were read directly from a BSC node as well, because a figure that changes the reading of an announcement should not reach anybody through one path only. Nothing here is a price claim.
Figures in this article are read from the index when the page is served and carry the day they were measured. A figure the index is withholding is not shown as a number here — see the methodology.