Zap Pilot

How the runtime works

The sequence from market observation to your wallet and its capability status.

Each day it reads the market, runs an open-source reference strategy, and shows where every step stands.

Observe

Live It weighs price against the 200-day average, ETH against BTC, and fear and greed.

Live 200-day moving averages, crypto and US-equity Fear & Greed, and ETH/BTC, shown in the app next to each decision.

Evaluate

Live Five rules, checked in order. The first rule that fires sets the target.

Live DMA/FGI Portfolio Rules is evaluated daily on Zap Pilot-hosted servers and produces an advisory target allocation with a decision packet.

Target

Live That sets the target. Rebalance plans are the next part to build.

Planned An adapter for the S&P 500 sleeve the reference strategy models. Deposits keep it at 0% until one exists.

Plan

Live Deposits you start yourself go straight into positions you hold: the Spark USDC vault on Morpho (Base), GMX v2 GM pools (Arbitrum) and Hyperliquid HLP, routed through LI.FI.

Planned Turn the gap between a strategy target and your positions into transactions you review and sign.

Check

Live Approvals are capped, routed swaps must meet a minimum received, and a batch that fails simulation can’t be signed.

Live Every plan fails closed unless approvals are capped (never unlimited) and routed swaps meet a minimum received within 1% slippage; a batch that fails Tenderly simulation is rejected. HyperCore follow-up steps are not simulated.

Planned Limits, allowlists and a kill switch you set, checked before anything is signed.

Sign

Live Nothing moves until you sign, with no Zap Pilot vault in between.

Live EIP-5792/7702 wallets sign one atomic batch; other wallets sign step by step. Privy wallets also sign an EIP-712 intent bound to the batch.

Live Hyperliquid deposits use an agent key created and stored on your device (browser storage on the web). You approve it once, and that approval may not expire.

Verify

In development Daily IPFS snapshots linked into a chain. They are unsigned and track a single reference address.

Research Version 1’s cross-down exit rule is compiled to Vyper on Arbitrum Sepolia with a pinned runtime codehash, so a recorded exit can be recomputed.

Unattended runs

Planned Rebalancing without you, only inside scoped on-chain permissions you can revoke.

Planned Ordinary EIP-7702 delegation is not a scoped session key. Unattended sessions require restricted on-chain targets and methods, spend caps, expiry, revocation and prototype/audit review.