OpenZapsAppchain 4663
NEW ZAP

Start with the outcome. Lock the rules after.

Choose how you want to Zap. Every path ends in a Zap contract with an immutable route, a wallet-owned recipient, and bounds you read before you sign.

DESCRIBE YOUR ZAP

Say the outcome in plain language.

A model may propose the blocks; the deterministic catalog and compiler decide what survives. No wallet action happens here.

Try: “DCA weekly” · “Buy 0xZAPS with USDG” · “Exit liquidity to aeWETH”

Run one you already trust

Saved on this device, newest first — up to three.

Or start something new

Nothing is submitted from this screen.
ZAP NOW

Zap in with one bounded authorization

Create the Zap, fund it, review the exact output floor, then sign and run it.

v1.1 · one-shot nonce
RECURRING

Repeat a fixed amount on schedule

Choose cadence, total Zaps, expiry, and slippage. Each one's floor is recomputed from live spot.

v3.1 · replaceable series
PRICE TRIGGER

Fire once after a one-sided move

Pick the price move, the validity window, and a slippage band. The floor comes from a fresh quote at signing.

v3 · revocable nonce
COMPOSE

Build the route and its execution policy

Connect the route, add gas, gas-price, and executor controls as one stack, then review the resolved bounds.

atomic policy stack · undone in one step