Choose a reusable policy template
Start from DCA, pool deposit, claim-and-compound, or a gated guarded-exit design. Every template has explicit production status.
Policy versioningOpenZaps turn approved DeFi workflows into sealed policy capsules. Hermes can simulate, submit, monitor, alert, and revoke, but it cannot choose arbitrary targets, recipients, assets, or calldata.
$0xZAPS is live through a creator-verified Clanker V4 market on Robinhood Chain. It is the community and operator coordination token for OpenZaps; the protocol remains usable without treating the token as yield, equity, or a fee claim.
The app is a production review console first: template selection, bounded policy design, simulation checks, audit history, and revoke controls before the wallet integration is allowed to touch mainnet funds.
Start from DCA, pool deposit, claim-and-compound, or a gated guarded-exit design. Every template has explicit production status.
Policy versioningSee slippage, spend ceilings, postconditions, submitter scope, human approval gates, and simulation diffs before any wallet prompt.
No broadcastEach capsule carries audit history, dry-run receipts, local revoke controls, and JSON manifests for SDK or backend integration.
Audit trailOpenZaps split creation, execution, and submission authority so you can walk away without handing an agent broad approvals or custody. Pick the surface that fits the workflow.
Assets sit inside a narrow policy capsule. Hermes triggers only the frozen action graph; you keep an unconditional withdraw and revocation path.
Recurring automationOne-shot authority binds chain, zap, nonce, deadline, recipient, fee cap, gas, and policy hash before any relayer touches it.
Infrequent executionContract wallets sign the same typed policy. Hermes stays a submitter, simulator, and monitor — never an operator with discretion.
Power usersTemplates turn successful workflows into reviewable policy manifests. Some are ready for preview, some require governance review, and protective zaps stay deferred until external risk review clears.
A user pre-commits spend, frequency, recipient, slippage, relayer fee cap, and private submission for recurring ERC-20 buys.
automationA bounded deposit policy for CliqueClaw or pool.fans launch pools, with a fixed recipient vault and no arbitrary calldata.
launchA repeatable fee-claim policy for audited reward sources, exact approvals, and balance-delta postconditions.
yieldA protective policy for liquidity or oracle-risk exits. This is deliberately blocked in v1 until protective-zap review is complete.
protectionThe v1 contracts are a complete, internally-reviewed reference implementation: 47 passing tests, an adversarial multi-agent review, and 9 internal findings fixed — including a critical clone-hijack (all documented in the linked repo). Not externally audited; we say so plainly.
v1 reference contracts deployed on Base · factory 0xc7C5…926C ↗
Use the console to design, simulate, save, dry-run, and revoke bounded policy capsules.
Not financial advice. 0xZAPS is a community token with no claim on revenue, yield, or assets; onchain actions are irreversible and the protocol is pre-external-audit.