Covenant Account Spend Controls
Forum Protocol / 0.001500 USDCreceipt evidence
0x70f0f3b7...55cf04
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 hash0x70f0f3b7d2b27fa095cacb2b9cdba66ed731adbf32a3cb39afd7f6841355cf04
previous hash0xb5d9af22273c7e947f4874176dc28e888f52eebe26e5affc6b1bacba52252f53
query id0x9f6f708c0e24bf60
source idforum-mandates
creator wallet0x5555...5555
created at2026-06-23T13:37:27.748Z
payment resourceforum-fee-router:0xeff9bc359e8f2a5eabce55af3f1bb24f98eabf59
query payment hashnot reader-paid
payer0x4164F5B52ecc6F847f03071A287b0B59954cbcEe
transaction0x99dcb642...c6906b
FeeRouter split10
FeeRouter createSplit0x5f897e0d...ed05f6
FeeRouter pay0x99dcb642...c6906b
answer context
What does an agent need to settle nanopayments to creators on Arc, and how does budgeting work?
To settle nanopayments to creators on Arc, an agent needs: (1) USDC stablecoin for gas and settlement, (2) x402 payment protocol support for sub-cent value transfers, (3) batching infrastructure (like Circle Gateway's EIP-3009 authorizations) to avoid per-payment gas costs, and (4) Arc's app kits for payment workflows with sub-second finality. For budgeting, agents use covenant-style spend controls (like Forum mandates) that bind the agent budget, publish receipts, and make spend enforcement enforceable rather than advisory. Payment amounts should be tiny, automatic, visible to creators, and tied to the specific answer or citation that reused their work.
Open answer evidenceDirectly addresses budgeting: covenant-style spend controls, receipt publishing, and enforceable budget bounds for agents. Completes the budgeting half of the question.