← back

WARD

Confidential agent-spending treasury protocol.

Pinocchio · Solana · MagicBlock

Problem

AI agents spending on behalf of a treasury need spend limits and auditability, but fully public on-chain transactions leak strategy and counterparty info.

Architecture

Vault and Card PDAs hold treasury state and per-agent spend permissions. Two spend paths: cleartext for transparent flows, and private via MagicBlock's Private Payments API for confidential ones. View keys let an authorized party audit private spends without exposing them on-chain.

Key Decisions

Chose Pinocchio over Anchor for the same CU-efficiency reasons as Harvester. The dual-path design (cleartext vs. private) was deliberate — most treasury spend doesn't need privacy, so defaulting to private everywhere would waste compute for no benefit.