WARD
Confidential agent-spending treasury protocol.
Results
Two spend paths, cleartext and private via MagicBlock, with view keys so an auditor can read private spends without exposing them on-chain
Problem
AI agents spending on behalf of a treasury need spend limits and auditability, but fully public on-chain transactions leak strategy and counterparty information.
Approach
Vault and Card PDAs hold treasury state and per-agent spend permissions. Two spend paths: cleartext for transparent flows, and private through MagicBlock's Private Payments API for confidential ones. View keys let an authorised party audit private spends without exposing them on-chain. Pinocchio over Anchor for the same CU reasons as Harvester. The dual path is deliberate: most treasury spend does not need privacy, so defaulting to private everywhere would burn compute for nothing.