Episode 13: Metadata Before Money

Agent wallets are not the hard part. The hard part is proving what the agent was allowed to do, why it was allowed, what limits applied, what changed, and how the operator can audit or stop the next action. This episode argues that payment rails for agents need an authority rail beside them: identity, delegated authorization, policy, spending scope, provenance, receipts, expiry, revocation, and replayable audit trails. Key points: The June 2 scan found a fresh Bitcoin payment-infrastructure hook in Second's Ark and Lightning work, but not enough evidence to claim an AI-agent payment breakout. Payments make agent actions economically real, which makes ambiguous authority expensive. A May 27 arXiv paper argues agents should not be trusted to carry security-critical metadata inside their own reasoning path; control metadata needs infrastructure support. Gartner warned on May 26 that uniform governance across agents can fail, and predicted 40% of enterprises will demote or decommission autonomous agents by 2027 due to governance gaps. Bitcoin, Lightning, Ark, and Nostr are useful primitives for settlement, signed identity, events, and receipts, but they do not by themselves prove an agent had authority to act. Approval prompts should scale by blast radius: read-only, advice, spending, publishing, trading, and account changes need different controls. Audience prompt: If your agent could spend money tomorrow, what would travel with that payment: identity, authorization, policy, expiry, receipt, and stop path, or just a transaction? ⚡ Zap us on Fountain | Lightning: [email protected] Not financial advice. Just sovereign signal, no corporate noise.