Portfolio rules you can read, not fear and greed

Your strategy. Your machine. Your wallet.

Zap Pilot is building a self-hosted runtime for programmable portfolios.

  • LiveOpen-source reference strategy
  • LivePositions at your own address
  • LiveChecked before you sign
  • PlannedRuns on your machine
Zap Pilot01 / 10

The problem

Self-custody secures the keys. The portfolio process still belongs to someone else.

  • Do it by hand, and every rebalance is a manual, emotional call.
  • Hand it over, and you deposit into a product’s vault and accept its house strategy.
  • Either way, the rules aren’t yours to read, test, or replace.
Self-custody shouldn’t stop at the keys.
Zap Pilot02 / 10

Solution

Own the strategy, the machine, and the wallet.

Your strategy

Rules you can read, test, and replace.

Today

  • LiveOne reference strategy, DMA/FGI Portfolio Rules, is evaluated daily; each decision shows the rule that fired and the raw signals.

Next

PlannedWrite your own rules and backtest them against the same benchmark.

Your machine

The runtime runs on hardware you control.

Today

  • Evaluation and planning run on Zap Pilot-hosted servers.
  • In developmentA Mac app that checks for drift every few hours and notifies you. It never signs.

Next

PlannedStrategy evaluation and planning on your own machine.

Your wallet

Assets stay at your address. You sign every batch.

Today

  • LiveDeposits go straight into Morpho, GMX and Hyperliquid positions you hold; no Zap Pilot vault; every batch is checked before you sign.

Next

PlannedA policy you set — limits, allowlists, a kill switch — checked before anything is signed.

Zap Pilot03 / 10

The runtime

One loop. Every stage labeled with what runs today.

  1. 01StrategyLiveDMA/FGI Portfolio Rules, the reference strategy
  2. 02TargetLiveadvisoryA target allocation and the rule that fired
  3. 03Current portfolioLivePositions at your address, refreshed daily
  4. 04Rebalance planPlannedThe gap between target and positions, as transactions
  5. 05Policy validationLiveBuilt-in checksPlannedYour policy
  6. 06ExecutionLiveDeposits you signPlannedUnattended
  7. 07VerificationIn developmentUnsigned daily snapshotsResearchOne rule on-chain

PlannedDeterministic first. AI, if added, stays optional and bounded by your policy.

Zap Pilot04 / 10

Reference strategy

DMA/FGI Portfolio Rules: signals, not emotion.

A deterministic priority stack reads 200-day moving averages, crypto and US-equity Fear & Greed, and ETH/BTC relative strength. The first rule that fires sets the day’s advisory target — no scoring, no blending, no overrides.

SignalJobOutcome
200-DMATrend filterRisk-on or defend
Fear & GreedSentiment filterBuy weakness, defend froth
ETH / BTCCrypto rotationETH tilt or BTC tilt

PlannedTarget spans S&P 500, BTC/ETH and stablecoins; the S&P 500 sleeve has no adapter yet.

See the five rules in priority order
Zap Pilot05 / 10

Backtest · reference strategy

DMA/FGI Portfolio Rules vs DCA Classic

500-day strategy snapshot as of 2026-10-10. DMA/FGI Portfolio Rules vs DCA Classic, daily signal evaluation, 43 simulated trades.

Indexed growth

Reference strategy vs DCA Classic

Reference strategy vs DCA ClassicIndexed 500-day equity curve from 2025-05-29 to 2026-10-10. The reference strategy finishes at 173.65 and DCA Classic finishes at 89.61.50100150200173.6589.612025-05-292026-10-10
Indexed to 100. Shaded band marks the observed max-drawdown range across the backtest window.
DMA/FGI Portfolio RulesROI +73.65%Max DD −9.83%43 trades
DCA ClassicROI −10.39%Max DD −40.85%498 trades

PlannedThe backtest’s S&P 500 sleeve has no executable adapter yet.

Read the backtest method

ROI vs DCA

+84.04pp+73.65% vs −10.39%

Strategy ROI

+73.65%500-day window

Calmar ratio

5.07vs DCA: −0.19

Sharpe ratio

2.00vs DCA: −0.20

Max drawdown

−9.83%vs DCA: −40.85%

Hypothetical backtest: it fills each trade the day after its signal, assumes a yield on stablecoin balances only, and includes an S&P 500 sleeve Zap Pilot can't execute yet. Past performance does not guarantee future results. Backtest window: 2025-05-29 to 2026-10-10, as of 2026-10-10.

Zap Pilot06 / 10

Wallet

Today: deposits you sign. Next: rebalances you sign.

  • LiveNo Zap Pilot vault. Positions sit at your address inside the venues themselves, so you can also manage them there. Those venues are pooled third-party protocols with their own risks.
  • LiveChecked before you sign. Approvals are capped, never unlimited; routed swaps must meet a minimum received; a batch that fails simulation can’t be signed.
  • LiveOne batch where your wallet supports it. EIP-5792/7702 wallets sign one all-or-nothing batch; others approve and execute step by step.
  • LiveHyperliquid key stays on your device. Hyperliquid deposits use an agent key created and stored on your device. You approve it once, and that approval may not expire.
  • PlannedUnattended only behind your limits. Rebalancing without you will require on-chain scoped permissions: allowed targets, spend caps, expiry, and revocation you control.

Today Live

  1. 01 · Choose amount and mix
  2. 02 · Plan built
  3. 03 · Checked & simulated
  4. 04 · You sign
  5. 05 · Settles at your address

Next

  1. LiveStrategy target
  2. PlannedPlanner
  3. PlannedYour policy
  4. PlannedYou sign; later, scoped permissions
  5. In developmentVerified & recorded
Zap Pilot07 / 10

Roadmap

What runs, what’s next, what’s later.

Now

  • LiveReference strategy
  • LiveMarket signals
  • LivePortfolio tracking
  • LiveDCA Classic benchmark
  • LiveDeposit plans
  • LivePre-sign checks
  • LiveWallet signing
  • LiveProtocol adapters
  • LiveNo Zap Pilot vault
  • LiveDevice agent key
  • LiveOpen source
  • ResearchOn-chain rule check
  • In developmentWithdrawals
  • In developmentMac drift check
  • In developmentSnapshot chain

Next

  • PlannedStrategy interface + backtesting your own rules
  • PlannedRebalance planner
  • PlannedPolicy engine
  • PlannedLocal runtime
  • PlannedAdapter hardening, including tokenized S&P 500

Later

  • PlannedDeterministic unattended rebalancing within scoped permissions
  • PlannedStrategy publishing, versioning, pinning and verifiable track records
  • PlannedOptional AI exception layer

Sequence, not dates.

Zap Pilot08 / 10

Why now

The wallet became programmable.

Shift · 01

Wallets can batch

EIP-5792 and EIP-7702 let one signature approve an all-or-nothing batch of calls.

Shift · 02

Exposure lives at your address

Lending, liquidity and market-making positions can be held by your own address, with no intermediary account in between.

Shift · 03

Rules can be checked, not trusted

Open code, daily public backtests, and one rule recomputed on testnet.

Research
Zap Pilot09 / 10

Help us make the portfolio process as self-custodied as the assets.

Book an intro callEmail founderJoin the waitlist
Self-custody · no Zap Pilot vaultLiveDeposits on mainnetOpen source