What the report establishes
On 11 November 2026 at 18:39 (UTC+8), Odaily reported that Aethir had posted on X that an update to the ATH token model was live, that an ATH burn dashboard had been enabled, and that daily burns had started. This note follows that newsflash only. It does not restate later developments, and it does not treat the post as an independent measurement.
Original report: Odaily newsflash.
Figures attributed to the post
As relayed by Odaily, cumulative burns stood at 4,364,413 ATH, of which 629,516 ATH were burned in the prior 24 hours. Those amounts are project figures as reported. The newsflash does not include transaction hashes, a contract address, or a dataset that would allow the totals to be recomputed here.
Mechanism as described
Aethir’s post, via Odaily, says burn funding comes from a portion of the network fees customers pay when booking computing power. It also says that when the market is weak, floating network fees fall and the share directed to burns rises, but that this share will not exceed rewards to cloud hosts.
That is a design statement, not a demonstrated fee schedule. The source gives no percentage split, no definition of the floating fee, and no description of how the cap against cloud-host rewards is enforced.
The same report says each burn can be publicly verified, and that the dashboard shows daily, monthly, and cumulative burn totals together with full transaction records. Whether those views match on-chain execution is not checked in the newsflash.
Limits of the evidence
Documented here is a secondary report of an X post: a live model update, a dashboard, daily burns, two stated ATH totals, a fee-funded burn, and a cap relative to cloud-host rewards. Not documented are the fee formula, the measurement cut-off beyond “past 24 hours” and the cumulative total, or any audit. The claim that a weaker market raises the burn share while keeping it at or below cloud-host rewards remains an unresolved project assumption on the evidence in this source.