Covenant Account Spend Controls
Forum Protocol / 0.001500 USDCreceipt evidence
0xe40dab62...3e8d02
paid to creator0.001500USDC
forum routed
Forum Protocol
This receipt binds a source payment to the answer that used it. The previous hash links it into the append-only attribution ledger.
receipt hash0xe40dab62a46a7d86a022901c9c2a1f270267120dc99fbd3b61178c525a3e8d02
previous hash0xe829c7e1675cb61ade357b27547654541c98b3ceb302830730e13f93ecfee2a7
query id0xcfa83524563443f2
source idforum-mandates
creator wallet0x5555...5555
created at2026-06-23T14:54:41.275Z
payment resourceforum-fee-router:0xeff9bc359e8f2a5eabce55af3f1bb24f98eabf59
query payment hashnot reader-paid
payer0x4164F5B52ecc6F847f03071A287b0B59954cbcEe
transaction0x85a672cc...b8c392
FeeRouter split25
FeeRouter createSplit0xb87e1855...24ab94
FeeRouter pay0x85a672cc...b8c392
answer context
How do Forum covenant mandates enforce agent spend control on Arc?
Forum covenant mandates enforce agent spend control on Arc through enforceable budget bounds and receipt publication. Forum-style mandates bind an agent's budget, publish cryptographic receipts of all transactions, and make spend controls enforceable rather than advisory. This works on Arc because Arc is designed for stablecoin-native settlement with USDC, sub-second finality, and app kits for payment workflows. When combined with x402 payment protocols (which enable sub-cent nanopayments), agents can make granular, auditable purchases while staying within their mandated budget envelope. The receipts are published on-chain or in a verifiable ledger, making violations transparent and enforceable by the protocol or governing entity.
Open answer evidenceDirectly answers the core question: explains how Forum-style mandates bound agent budgets, publish receipts, and make spend controls enforceable instead of advisory.