Roadmap

Ship the primitive without widening the trust boundary.

OpenZaps can become the wallet primitive for agent-native DeFi, but only if each release keeps execution authority explicit, inspectable, and revocable.

Release path

Now

Review console

Template builder, deterministic policy hashes, simulation checks, local audit log, dry-run receipts, and revoke controls.

Next

Wallet-reviewed creation

Connect wallet, prepare EIP-712 typed data, show exact approvals, and generate factory transactions without automatic broadcast.

Audit

External security gates

Third-party audit, formal verification, testnet soak, adapter manifests, governance runbook, and incident drills.

Beta

Hermes private execution

Allowlisted submitters, private submission, monitoring receipts, alert delivery, and owner self-submit fallback.

Network

Reusable policy market

Policy template registry, agent reputation, eval results, SDK publishing, and pool.fans / CliqueClaw integrations.

Non-negotiables

  • ERC-20 first until callback and multi-asset accounting risks are reviewed.
  • Protective zaps stay blocked until oracle, liquidity, and liquidation risk controls are externally reviewed.
  • Every fee must be visible in the typed policy before signing.
  • Every automation needs pause, revoke, audit, and self-submit fallback paths.