DeFi,
in one
action.

What is a Zap

A Zap compresses a sequence of onchain actions into one transaction. It is a bounded script: a start state, an ordered list of calls, and a set of guards that, if violated, revert the entire execution atomically.

Core concepts

• Intent — the high-level "what": Swap, Provide LP, or Exit LP.
• Route — the "how": ordered list of pools, adapters, and vaults.
• Policy — the "rules": minOut, slippage cap, deadline, recipient lock.
• Capsule — pre-sign simulation that replays the route against the latest block.
• Execution — one signature, one atomic transaction onchain.

Intent types

• Swap — token A in, token B out, through any number of hops.
• Provide LP — single-sided or balanced entry into a Uniswap v4 position via the OpenZaps vault.
• Exit LP — burn ozRANGE shares, remove liquidity, swap back to any token, settle to recipient.

Route compilation

Given an intent the compiler:

• Reads the current reserves of every supported pool on Robinhood Chain.
• Enumerates valid 1–3 hop paths between the from and to tokens.
• Ranks by output after fees, price impact, and gas.
• Encodes the winning path into a single execute() calldata blob.

Policy guards (always enforced)

• minAmountOut — revert if output is below this value.
• deadline — revert if block.timestamp exceeds this.
• recipient — output tokens can only go to this address.
• maxPulled — router can pull at most this amount of the input token.

Capsule simulation

Before anything is signed, the route runs inside a local EVM fork against the latest block hash. The capsule reports:

• Exact input consumed and output produced.
• Intermediate balances after each hop.
• Gas used at each step.
• Any revert — with the exact step and reason.

Execution flow

1. User signs one Permit2-style message (policy + route hash)
2. Relayer submits execute(policy, route, signature)
3. Router validates policy against signature
4. Router pulls input (bounded by maxPulled)
5. Route runs step by step
6. After last step: if output < minOut → REVERT
7. Output swept to recipient (locked by policy)

Supported protocols

Uniswap v4 (hooks + CL pools), Morpho (supply/borrow loop), Aave v3, Compound v3, Aerodrome AMM, Canonical bridge, Wrapped native, OpenZaps vault (ozRANGE LP accounting).

Network

Robinhood Chain · Chain ID 4663.

FAQ

Is OpenZaps a custodian?
No. The router never holds idle balances; every Zap ends with a sweep to the recipient address encoded in the policy.

What if one step fails?
The whole transaction reverts atomically. No half-executed state is left onchain.

Can I build my own Zap?
Yes — every route is a public struct; the builder UI is one possible frontend. You can submit raw calldata directly to the router.

Core

Adapters

Tokens

Pre-audit

OpenZaps is currently unaudited. Assume bugs exist; use only with amounts you are prepared to lose.

Permissionless execution

Routes execute atomically. If any guard fails the entire Zap reverts — no partial state is left behind.

Allowances

The router pulls only the amount specified in the policy. Some ERC-20s still require unlimited approval due to token standard limitations.

Third-party protocols

OpenZaps routes through Uniswap v4, Morpho, Aave, Compound, Aerodrome, and canonical bridges. Each carries its own risk.

Robinhood Chain

Deployment target: Robinhood Chain · Chain ID 4663.

No financial advice

This is developer infrastructure. Nothing on this site is investment, tax, or legal advice.