Available · no wallet
Practice with virtual USDG
Trade the four pinned USDG routes with 10,000 virtual USDG. Quotes are pinned to one canonical chain head; fills and PnL stay in this browser.
Open Virtual TradingOpen execution infrastructure
DeFi,in oneaction.
OpenZaps turns a multi-step DeFi workflow into one bounded Zap. Compose the route and its execution policy, review the wallet confirmation, then Zap now, on a cadence, or on a price move. The Zap contract enforces the signed bounds onchain.
What is a Zap
A Zap compresses a sequence of onchain actions into one transaction.
5 manual actions
- 01Approve USDG
- 02Swap USDG → aeWETH
- 03Approve aeWETH
- 04Swap aeWETH → 0xZAPS
- 05Settle to wallet
One ZapUSDG → 0xZAPSone signed step · minOut enforced
The problem
DeFi is composable.
Its interfaces are not.
Every protocol works. Composing them by hand is the part that does not: allowances, quotes, tabs, and settlement scattered across surfaces that were never designed to be one workflow.
- 01Too many tabs
- 02Repeated approvals
- 03Fragmented liquidity
- 04Inconsistent interfaces
- 05Manual routing
- 06Unnecessary gas
- 07Hidden execution complexity
- 08Poor discoverability
OpenZaps threads them back together — one route, one signature.
Recently shipped
More ways in. The same hard boundary.
Practice without a wallet, ask for a workflow before committing, or connect one executor to terms you sign. Every surface says exactly when authority begins—and what remains a candidate.
Available · human review
Request a bounded Zap
Describe one workflow. We map its targets, assets, recipient, trigger, limits, recovery, and forbidden authority—with no wallet or integration commitment.
Request a ZapLive · owner-signed
Connect one executor
Pin an executor address inside a standing intent. The agent may choose when to submit an eligible run; it cannot change the route or its terms.
Connect an agentLive
Recurring 0xZAPS stack
The v3.2 stack is live on Robinhood Chain: creation, execution, and permanent-halt canaries passed with onchain receipts. The contracts remain unaudited.
See the release mapOne action, many protocols
Start from an intent. The route does the walking.
A Zap begins with what you hold and what you want. OpenZaps composes the pools, vaults, and settlement underneath into a single bounded policy — inspectable before it is signed.
- USDG
- Uniswap v4aeWETH/USDG pool
- aeWETH
- Uniswap v40xZAPS/aeWETH pool
- 0xZAPS
- sendowner wallet
- Token exit
- Blocks composed
- 4
- Signed steps
- 1
- Manual actions replaced
- 5
- Gas constant
- 233,000
- Slippage cap
- 50 bps
Compose execution policy
The route says what. The policy sets the limits.
Three execution controls now live in the block catalog. Add them together as one policy stack, tune them on the canvas, and carry the resolved values into the signed Zap now or Automate intent.
maxGas
3,000,000 gasExecution gas limit
Caps the gas available to a signed Zap. A Zap outside the budget reverts.
maxFeePerGas
10 gweiGas price cap
Rejects execution when the transaction gas price exceeds the signed ceiling.
executor
Anyone / OwnerExecutor access
Keep automation open for liveness, or restrict submission to the owner wallet.
Gas limit and gas price cap bind Zap now and Automate intents. Owner-only executor access is live in v3/v3.1/v3.2 automation. The v1.1 one-shot handoff discloses that it cannot restrict the submitter.
Example Zaps
Executable paths through DeFi.
Six blueprints from the catalog. Hover a card to see the blocks and protocols underneath; open one and the builder loads this exact chain — live routes sign and Zap today, designs compile and save.
Preview an execution
Compile a route. Watch it check itself.
The same compiler that powers the builder, executing here. Pick an intent, set an amount, and preview the checks a Zap performs before anything is signed.
compiled route
- 01Wallet balance
- 02Slippage cap
- 03Swap
- 04Send to recipient
simulation · ready
- Connector fitEvery block accepts the shape the block above it emits.
- Block maturityEvery block in this chain is on the live adapter set.
- SlippageSlippage is bounded at or below 1.00%.
- Guard coverage50% guarded. Missing: Time window. Drop them anywhere below the source.
- AuthorityThe signed policy is the only authority — bounded by its guards and revocable at any time.
- status
- warn
- signed steps
- 1
- gas constant
- 233,000
- guard cover
- 50/100
- design hash
- 0x80dcd109…
Output amounts are quoted live at sign time, never estimated here.
Verified 0xZAPS utility
Trade it. Use the app. Inspect the first fixed fee campaign.
OpenZaps can buy 0xZAPS through its pinned aeWETH → 0xZAPS route. Every Zap contract created by the current app converts its visible 0.00001 ETH creation fee into 0xZAPS atomically. A connected wallet holding 100,000+ 0xZAPS also gets auto-refreshing quotes, more saved Zaps and receipts, and receipt JSON export. The first 0xZAPS fee rewards campaign is fixed to a seven-day Aug 3–10, 2026 staking window. It was funded at launch with 50 of 100 tokenized Clanker fee shares and is configured to use time-weighted stake to allocate campaign-accounted WETH to eligible deposits during that window. Its harvest path was configured for Clanker fees, while direct WETH transfers can also be synchronized. Check /rewards for the current phase and later claim deadline. Every core workflow stays open without holding or staking the token.
Live routeaeWETH → 0xZAPS
Pinned Uniswap v4 pool, one bounded policy execution.
Every creationFee → 0xZAPS
0.00001 ETH, converted atomically with a reviewed floor or the whole creation reverts.
100,000+Holder conveniences
Auto-refresh quotes, 50 saved Zaps, 100 receipts, JSON export.
1,000,000+Operator convenience
Raises the app's saved-zap limit to 100.
50 / 100 fee sharesLaunch allocation
Seven-day Aug 3–10, 2026 staking window; /rewards shows the current phase and later claim deadline.
Ownership alone grants no governance, automatic staking benefit, fee right, revenue claim, yield, equity, or return. The first campaign was limited to eligible deposits made during its fixed Aug 3–10, 2026 staking window; /rewards shows the current phase and later claim deadline.
Why OpenZaps
Built like infrastructure, not an interface.
- 01
One transaction
Once approved and funded, a bounded route executes its protocol hops and settlement in one transaction.
- 02
Permissionless
Anyone designs, shares, and executes Zaps — creation is open to any caller, and no signature but yours can move funds. Zaps execute only through governance-allowlisted adapters and tokens.
- 03
Composable
Typed blocks snap into chains; shapes must match, so what compiles is what can execute.
- 04
Transparent
Every Zap's policy, provenance, and executions are public and re-verifiable on /explore.
- 05
Bounded
Target, recipient, calldata, amounts, gas: fixed at signing. Execution cannot exceed the policy.
- 06
Standing
One signature can authorize a whole series. The Zap enforces the interval, the total number of runs, and a floor priced from live spot, so it keeps running without keeping your keys online.
Protocol integrations
OpenZaps does not replace protocols. It makes them easier to compose.
Bright nodes carry deployed, bounded routes today. Dim nodes are typed into the catalog — designs compile against them now and deploy when their adapters ship.
Developers
Build from one typed DeFi catalog.
The block catalog, compiler, and share-token codec are MIT TypeScript — the same modules rendering this page. Compose a chain, compile a verdict, ship a link.
src/lib/blocks.ts · MIT · executes in this page
import { compileChain, encodeChain, makeNode } from "@/lib/blocks"; const chain = [ makeNode("wallet-balance", "src", { asset: "USDG", amount: "25" }), makeNode("guard-gas-limit", "gas", { maxGas: 3_000_000 }), makeNode("guard-gas-price", "fee", { maxFeeGwei: 10 }), makeNode("guard-executor", "executor", { access: "Anyone" }), makeNode("guard-slippage", "cap", { bps: 50 }), makeNode("swap", "leg", { into: "0xZAPS" }), makeNode("send", "out"),]; const verdict = compileChain(chain);const link = `/zap?d=${encodeChain(chain)}`;// every chain is a shareable, executable linkverdict
- status
- warn
- gas
- 233,000
- guardScore
- 50
- hash
- 0xbc98caf7…
- Wallet balance (asset USDG, amount 25)
- Execution gas limit (maxGas 3000000 gas)
- Gas price cap (maxFeeGwei 10 gwei)
- Executor access (access Anyone)
- Slippage cap (bps 50bps)
- Swap (into 0xZAPS, venue Uniswap v4, amount )
- Send to recipient (recipient owner wallet)
POST /api/policies/simulate — deterministic policy simulation over HTTP
Agent execution
Agents should express intent, not assemble transactions.
A Zap is the contract between you and your agent: it can decide when to execute, and nothing else. An eligible executor can submit the Zap it owes, while the chain refuses every Zap it does not.
agent intent
The agent can hold the trigger. It cannot change what the trigger does: target, calldata shape, recipient, and asset are welded in before signing.
routeUniswap v4 aeWETH → 0xZAPS
adapter0x04f62dA4…Ed602C
constraints
- Recipient is welded to the owner wallet at signing
- Slippage capped at 50 bps, signed into the execution intent's minimum-out
- Amounts bounded to uint128 by the router
- Execution gas ceiling 3,000,000
- Execution gas price capped at 10 gwei
simulation
- Connector fit
- Block maturity
- Slippage
- Guard coverage
refuses
Refuses any pool but the one welded into its constructor, any calldata beyond a bounded minimum-out, and any chain but 4663.
Security & transparency
Every abstraction remains verifiable.
Owner-signed execution
Only the owner ever signs. A one-shot Zap is sent from the owner's wallet; a recurring or price-triggered Zap can be sent by any executor, and the Zap re-checks every bound before it settles. Nothing executes custodially.
Policy fixed before signing
Target, recipient, asset, and calldata shape are welded into the Zap. Execution cannot redirect them.
Deterministic simulation first
Every design compiles through the same checks before signing — fit, caps, guard coverage, gas constants.
Minimum-out enforced onchain
The slippage cap (10–500 bps) sets the minimum output signed into each execution intent — the Zap reverts the trade if net output lands below it.
Bounded amounts and gas
Amounts are capped at uint128; execution carries a 3,000,000 gas ceiling and a 10 gwei fee cap.
Recovery path
Funds stranded in a Zap are recoverable by the owner at any time — no permission needed.
System metrics
9 blocks1 signed step
compiled from the Triggered Zap in blueprint
- typed blocks
- 32
- adapter contracts live on chain 4663
- 9
- blueprints in the catalog
- 26
- deployable today
- 14
- route kinds
- 6
- policy step ceiling
- 16
Social Zaps
Every strategy becomes a link.
A designed chain encodes into a URL-safe token. Send it to anyone: the builder decodes it, compiles it, and — if it reduces to a live route — signs and Zaps it.
- 01Design a chain
- 02Encode it into a link
- 03Share it anywhere
- 04Anyone executes it
Attribution and fee-sharing for published Zaps are on the roadmap — links themselves work today.
OpenZaps FAQ
DeFi Zaps, immutable policies, and wallet control.
Start with the protocol model, then inspect the developer and security docs, the source-verified zap explorer, and the 0xZAPS token page.
What is a DeFi zap?
A DeFi zap packages multiple supported protocol steps into one wallet transaction. OpenZaps executes only routes backed by allowlisted adapters and tokens; approval, Zap creation, and funding can require separate wallet confirmations.
Does every OpenZap require only one transaction?
The bounded route executes its protocol hops and settlement atomically in one transaction after setup. Token approval, Zap creation, and funding can each require a separate wallet confirmation.
Can an AI agent change my OpenZap policy?
No. The user wallet or Safe creates the authority and signs the policy. An eligible executor can submit only the transaction permitted by those immutable targets, assets, recipients, amounts, calldata constraints, and deadlines.
How can an owner stop or recover from an intent?
Recovery is lineage-specific. Live v1.1, v3, and v3.1 owners can invalidate unused signed authority and use the supported emergency-exit path for tracked assets; the v3.2 deployed candidate additionally exposes a one-way permanent policy halt. No control can undo a confirmed execution.
Does OpenZaps support every DeFi protocol?
No. Live execution is limited to source-backed routes whose adapters and tokens are explicitly allowlisted. Additional protocols require reviewed adapters and tests before they can carry funds.
Are onchain actions on OpenZaps reversible?
No. Deposited funds are at risk and onchain actions are irreversible: once an execution lands, nothing in the interface can undo it. Risk disclosures are collected on the legal page.
One Zap is enough.
Execute across DeFi without navigating every layer beneath it.