Capabilities / Programs

Program management

Cancel a program and release unused reserves.

Implementation boundary

BSC adaptation

Existing cancellation/expiry plans still reconcile actual fixed refunds. The new finite program grant also executes no-argument close with separately owner-signed allowClose, canonical treasury refund and readonly recovery after revoke/expiry/flags-off. Remaining: Automatic community/independent airdrop activation/commit/claims/close signing is outside finite program v1 and remains unimplemented; existing exact-owner preparation/payment evidence is separate. Production fixed program signer/state-callback HTTPS+separate secrets, actual immutable vault/Portal/token/adapter identities and full history RPC, funded native escrow/operator gas, real EOA finite grant and explicit per-scope/model/scheduler permission; no such production run is proved locally.

Current awake evidence

actual local http d1 eip712 evm finite autonomous subset verified

Production verification: not complete. Registered model tools: cancel_program · inspect_programs · prepare_program_execution · inspect_community · inspect_funded_program_execution · execute_funded_program. Registration does not mean enabled or actually run.

Original typed tools

cancel_program

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.

Back to registry