# OpenZaps

> OpenZaps turns supported DeFi workflows into bounded Zaps: immutable policy capsules that a human or AI agent can simulate, submit, and monitor without discretionary wallet authority. A Zap is the deployed contract; one execution of it is a run. A supported route can execute its protocol hops and settlement in one transaction after any required approval, Zap-creation, and funding confirmations. 0xZAPS is live on Robinhood Chain through a creator-verified Clanker V4 market (contract 0xDd90bFa4adC7F4401E611AbaC692D939F9F4CB07).

Key facts:
- Production v1.1, v3, and v3.1 contracts are live on Robinhood Chain (chain ID 4663). Supported swaps, stitched routes, full-range aeWETH/USDG liquidity, the ozUSDG ERC-4626 receipt, recurring series, and price triggers are exposed through source-backed, allowlisted adapters. The contracts remain pre-external-audit, and deposits carry funds-at-risk warnings. An earlier Base mainnet factory is historical only and is not used by the production app.
- A separate v3.2 recurring-stack lineage is deployed and active on Robinhood Chain: its creation, execution, and permanent-halt canaries passed with onchain receipts, and the app, relay, and executor lanes are open. It remains unaudited. The v1.2 exact-owner-pull and permanent-halt lineage remains source-ready, undeployed, and not live.
- Token ownership alone confers no yield, equity, revenue claim, governance, automatic staking benefit, or protocol access guarantee. A separately identified Aug 3–10, 2026 campaign was funded at launch with 50 tokenized Clanker fee shares and is configured to allocate campaign-accounted WETH by time-weighted stake during that fixed window. Its harvest path was configured for Clanker fees; the site contains no sponsor-wallet WETH funding flow, while the contract can also account for WETH sent directly to it. Current principal, phase, and claim deadline are published at `/rewards`. Live app-level holder utilities also exist: wallets holding 100,000+ 0xZAPS unlock auto-refreshing quotes, extended saved-Zap and receipt history, and receipt JSON export in the app (1,000,000+ extends history further). Core workflows are never token-gated.
- Execution authority is bound in EIP-712-signed policies: fixed adapters, spend ceilings, recipients, deadlines, and postconditions, plus owner-only nonce invalidation and emergency asset recovery.

## Pages

- [Home](https://www.0xzaps.com): what a Zap is, the authority model, security posture, FAQ
- [DeFi Zap builder](https://www.0xzaps.com/zap): design, quote, and simulate supported policy-bound routes without a wallet; connect only when owner signing, contract creation, funding, execution, automation, or recovery requires it. One route with five surfaces — Start, Compose, Zap now, Automate, and Connect — selected by `?view=start|design|sign|automate|connect` and reached from the app sidebar. Connect prepares one executor address; it gains no authority until the owner signs matching terms in Automate
- [Request a Zap](https://www.0xzaps.com/request-a-zap): submit one workflow for a free, human-reviewed authority map covering targets, assets, recipient, trigger, limits, recovery, and forbidden authority. No wallet, deposit, signature, or integration commitment
- [Explore](https://www.0xzaps.com/explore): the live feed of creations, executions, and recoveries read from Robinhood Chain logs, every Zap the factory deployed, and the verified contract set — one page
- [My zaps](https://www.0xzaps.com/profile): browser-local designs plus source-backed Zap and automation records associated with the connected owner
- [Fee rewards](https://www.0xzaps.com/rewards): the fixed 50-share, seven-day 0xZAPS staking campaign; stake or withdraw principal, claim campaign-accounted WETH, run permissionless upkeep, and inspect the immutable release manifest
- [Fee-share wrappers](https://www.0xzaps.com/feeshare): a term-bound coupon strip and a WETH-to-0xZAPS auto-compounder over the same tokenized fee shares; contracts are source-ready and not deployed, so the surface fails closed
- [Developer docs & security](https://www.0xzaps.com/docs): policy schema, simulation API, templates, execution lifecycle, and the security model (threat model, controls, production gates) at /docs#security
- [Agent Kit](https://www.0xzaps.com/agent-kit): published TypeScript SDK and read-only MCP server for compiling exact policy and unsigned EIP-712 artifacts; neither package signs nor broadcasts
- [Learn](https://www.0xzaps.com/learn): source-reviewed product updates and RSS-confirmed DeFi Tutorials, with drafts withheld until publication evidence exists
- [Release evals](https://www.0xzaps.com/evals): dated release-evaluation evidence and its covered source revision
- [Roadmap](https://www.0xzaps.com/roadmap): current live capabilities, proposed route expansion, submission tooling, and hardening gates
- [0xZAPS token](https://www.0xzaps.com/token): verified contract, official Clanker market, FAQ
- [0xZAPS automation fee pot](https://www.0xzaps.com/pot): source-backed pot balances, conversion records, participant credits, rounds, and payouts
- [Virtual Trading](https://www.0xzaps.com/virtual-trading): paper trade 0xZAPS and aeWETH with 10,000 virtual USDG, canonical Robinhood Chain route quotes, and a browser-local ledger without connecting a wallet or risking real funds
- [Risk disclosures](https://www.0xzaps.com/legal): onchain irreversibility, token risk

Every verified factory-created Zap has a canonical detail page at `https://www.0xzaps.com/explore/{checksummed-address}` with crawlable policy, provenance, lifecycle, and onchain execution evidence.

## Discovery

- Sitemap: https://www.0xzaps.com/sitemap.xml
- Robots: https://www.0xzaps.com/robots.txt
- Web app manifest: https://www.0xzaps.com/manifest.webmanifest
- OpenSearch descriptor: https://www.0xzaps.com/opensearch.xml
- RSS updates feed: https://www.0xzaps.com/feed.xml

## Official links

- X (Twitter): https://x.com/0xzaps
- Discord: https://discord.com/invite/openzaps
- DeFi Tutorials: https://defitutorials.substack.com
- GitHub: https://github.com/0pen-Zaps/openzaps
- Verified contract source: https://robinhoodchain.blockscout.com/address/0xFC775017b25d2458623E2f3E735A4B750dD8b4E4?tab=contract
- Token market (Clanker): https://www.clanker.world/clanker/0xDd90bFa4adC7F4401E611AbaC692D939F9F4CB07
- Explorer: https://robinhoodchain.blockscout.com/token/0xDd90bFa4adC7F4401E611AbaC692D939F9F4CB07

## API

- POST https://www.0xzaps.com/api/policies/simulate — deterministic policy simulation; never broadcasts and never requests wallet authority
- GET https://www.0xzaps.com/api/health — public protocol status
- GET https://www.0xzaps.com/api/protocol/activity — live Zap creations, executions, and recoveries aggregated from Robinhood Chain logs (rows verified against the factory's ZapCreated set)
- GET https://www.0xzaps.com/api/protocol/pot — onchain lottery-pot balances, ticket counts, and rounds; returns 503 rather than a zero when the RPC reads are unavailable

Not financial advice. Always verify the token contract address on this site before trading.