Buyback & burn
Separate the intended budget, actual token purchase, and verifiable removal from supply.
Project purchase and burn-transfer receipts are read from Robinhood Chain. Automated allocation execution is not enabled.
Buyback & burn
The policy earmarks 30% at each stage for $OLM buyback and burn. A purchase and a burn are separate events, each requiring a transaction record.
A contract burn can reduce totalSupply. Sending tokens to an inaccessible address may leave totalSupply unchanged. A current supply reading is not a cumulative burn total.
The dashboard reads OLM receipts from its launch block. It counts confirmed purchases by the configured dev wallet and treasury separately from their transfers to the zero or dead address, once per transaction. The initial launch transaction and unrelated holder activity are excluded. Each reading shows its covered block and timestamp; an unavailable RPC is not reported as zero activity.
Required evidence
- Identify the funding source and applicable 30% allocation basis.
- Record the execution price, acquired $OLM amount, network, contract, and purchase transaction.
- Record the burn transaction and verify the token contract’s effect on supply.
- Reconcile budgets, execution costs, and any reserve before reporting completion.
Supply is not burn history
A configured token’s totalSupply reading describes its current contract-reported supply. It does not independently prove how many tokens were bought back or burned over time. Burn totals need verified event and transaction records.