Zap builder A block only seats where the shapes match. Every DeFi activity here is a block that declares its connectors: a source emits a shape, a settlement block takes one, and everything between does both. A joint seats only when the shape leaving the block above is the shape the block below takes, so dragging cannot assemble a mismatched chain. A shared link can still carry one, and the readout names the joint that does not fit.
Start from a blueprint One kind of zap each. The one marked deployable is the only shape the live contracts can carry. Load any of them, then rebuild piece by piece.
Live route The one chain today's contracts can carry: aeWETH into 0xZAPS. 4 blocksdeployable Recurring DCA Buy the same size every week, straight to your wallet. 6 blocks LP autocompound Provide liquidity, stake it, and fold the rewards back in. 8 blocks Claim & compound Harvest what has accrued and buy more of the asset. 6 blocks Leverage loop Supply, borrow, and re-supply inside a bounded LTV. 8 blocks Bridge & deposit Move to another chain and park it in a market. 6 blocks Guarded exit Unwind a position back to stables when the band breaks. 8 blocks
Blocks Drag into the chain, or tap to drop it in the first slot that fits.
All Sources Swap & route Lend & borrow Liquidity Yield Bridge Guards Settlement
Wallet balance Pull a fixed amount from the owner wallet. Recurring deposit Draw the same amount on a cadence. Pending rewards Start from whatever has accrued. Swap Exact-input swap through an allowlisted adapter. Split Fan one balance into a weighted basket. Bridge Move the balance to another chain. Supply Deposit into a lending market. Borrow Draw a loan against the supplied position. Draw to wallet Realise the borrowed balance as tokens. Add liquidity Deposit into a pool and take the position. Remove liquidity Burn the position back into tokens. Stake position Deposit the LP into a gauge or farm. Accrue rewards Let the receipt build a claimable balance. Harvest Claim the accrued rewards as tokens. Wrap / unwrap Convert between native and wrapped. Slippage cap Bound the worst acceptable fill. Spend ceiling Designed to cap total outflow. Not enforced onchain. Price band Designed to hold execution inside an oracle band. Not enforced onchain. Time window Designed to bound when execution may happen. Not enforced onchain. Human gate Designed to require a signature per run. Not enforced onchain. Private submission Designed to route around the public mempool. Not enforced onchain. Send to recipient Settle to a fixed address. Hold in zap Leave the position inside the capsule. Hold position Park an LP position in the capsule. Loop back Feed the output into the next run. This canvas designs zaps. It does not deploy them. A chain that seats here compiles and simulates. The only one the live contracts can carry is a single-step aeWETH ↔ 0xZAPS swap, with the recipient forced to the owner and the relayer fee cap at zero. Anything else saves as a design, and the panel on the right names which one you have.
Wallet balance WETH · 0.05 live ↑ ↓ ⧉ ✕
ERC-20
Slippage cap 50bps live ↑ ↓ ⧉ ✕
ERC-20
Swap 0xZAPS · Uniswap v4 live ↑ ↓ ⧉ ✕
ERC-20
Send to recipient owner wallet live ↑ ↓ ⧉ ✕
Needs a review ≈233,000 gas (estimate) · 4 blocks
Guard coverage 50%
No Time window — this chain signs a standing authority, so it never expires on its own. Add Connector fit Every block accepts the shape the block above it emits. Block maturity Every block in this chain is on the live adapter set. Slippage Slippage is bounded at or below 1.00%. Guard coverage 50% guarded. Missing: Time window. Drop them anywhere below the source. Authority The signed policy is the only authority — bounded by its guards and revocable at any time. Design fingerprint 0x25427f43…427f43 ⧉
A local checksum (FNV-1a) that tells two designs apart. It is not the onchain policy hash: a deployed capsule commits to a keccak256 hash of its ABI-encoded policy, so this value will not match anything on a block explorer.
Deploy on Robinhood Chain → This design reduces to the live route. The app page opens with aeWETH → 0xZAPS, 0.05 aeWETH, and a 0.50% signed slippage cap filled in. You create, fund, and sign there. Nothing is submitted from here.
The builder compiles and simulates. It cannot sign, fund, or submit a transaction. The one route the app page can deploy is the bounded aeWETH ↔ 0xZAPS capsule.