Capabilities / Treasury
Burn tokens
Remove acquired tokens from circulation.
Implementation boundary
BSC adaptationSeparate owner-only supply_burn and dead_transfer plans use actual exact-owner execution, current reserve/ledger locks and canonical per-transaction economic attribution. Supply reduction requires exact treasury debit and totalSupply decrease; DEAD requires unchanged totalSupply. Remaining: No autonomous burn dispatcher/standing grant or automatic purchased-principal-to-burn binding; no inferred selector fallback. Existing program BURN is DEAD transfer. The specifically verified current FlapV3 implementation in the cited proof has no public supply-burn selector: DEAD/zero-style retirement transfers do not reduce totalSupply. Keys or deployment parameters cannot repair that protocol incompatibility. Do not generalize to other versions/implementations. Chosen real Flap token must actually support reviewed supply-reducing burn; void/different return requires explicit independent call-policy review.
Current awake evidence
actual local http or sqlite evm subset verified
Production verification: not complete. Registered model tools: No autonomous model dispatch registered. Registration does not mean enabled or actually run.
Original typed tools
burn_own_token
Published limits / Solana reference
{
"section_declares_no_treasury_spending": true
}Original capability specification ↗These are source-reported limits. BSC values and venue limits require calibration.
AWAKE