Zap Pilot

Architecture

The data, strategy, plan, signing and protocol trust boundaries.

The strategy computes an advisory allocation. The app does not independently plan transactions; the wallet controls signing.

Service boundaries

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

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

Live Morpho, GMX v2, Hyperliquid and LI.FI adapters only encode actions that are already decided; they never choose a strategy.

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.

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.

Trust boundaries

Live There is no Zap Pilot vault or custody contract. The venues themselves are pooled third-party protocols with their own risks.

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.

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.

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

Hosted now, your machine later

Planned Your own machine runs your rules around the clock, inside limits you set, and calls you in when something falls outside them.

In development A Mac app that checks for drift every six hours and notifies you. It asks the hosted engine for the decision, never signs, and is not available to download yet.

Planned Strategy evaluation and planning on hardware you control.

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

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