Arc Settlement Sketch
Arc Builder Desk / 0.002200 USDCreceipt evidence
0x2f28928c...74eccb
paid to creator0.002200USDC
forum routed
Arc Builder Desk
This receipt binds a source payment to the answer that used it. The previous hash links it into the append-only attribution ledger.
receipt hash0x2f28928c568be532e0106322b55e4c7b4ecdd9b145f265538a6fdb326674eccb
previous hash0xe40dab62a46a7d86a022901c9c2a1f270267120dc99fbd3b61178c525a3e8d02
query id0xcfa83524563443f2
source idarc-finality-usdc
creator wallet0x3333...3333
created at2026-06-23T14:54:41.275Z
payment resourceforum-fee-router:0xeff9bc359e8f2a5eabce55af3f1bb24f98eabf59
query payment hashnot reader-paid
payer0x4164F5B52ecc6F847f03071A287b0B59954cbcEe
transaction0x47b1bd85...86bc0f
FeeRouter split26
FeeRouter createSplit0x51b4123e...f646dc
FeeRouter pay0x47b1bd85...86bc0f
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 evidenceEssential context on Arc's settlement layer: USDC-native, sub-second finality, and app kits for payment workflows—the infrastructure that makes Forum mandates enforceable on Arc.