Zap Pilot— rules engineZap Pilot
Backtest

Verification

The Zap Pilot track record is cryptographically verifiable. Each daily snapshot is pinned to IPFS with an immutable CID derived from its content. The CID chain links every snapshot to the previous one, forming a tamper-evident history. Optionally, snapshots are signed by the Zap Pilot official EOA.

Backtest mode — the checks below describe the committed backtest dataset, not a published on-chain snapshot. Switch to Live above for an independently verifiable record.

Loading verification data…

Methodology

Pricing time
Daily valuation when the UTC snapshot workflow runs.
Price source
Spot USD token prices from LI.FI, keyed by chain ID and token address. Deterministic backfills/tests may supply an explicit price override in the snapshot tooling.
LP token valuation
Mark-to-market using underlying asset prices × LP share of pool reserves.
Pendle PT valuation
PT price from Pendle market oracle; accrued yield added separately.
Unclaimed rewards
Not included in NAV until claimed on-chain.
Gas cost deduction
Estimated gas used × fast gas price at execution time, in USD, deducted from NAV.
Cross-chain aggregation
All chain positions converted to USD using their recorded pricing source, summed per asset, then per pillar.
Stablecoin handling
Stablecoins use their live USD spot price instead of assuming a fixed 1.0 USD peg.

Full Verification (CLI)

The browser verifies CID chain linkage and signatures. For full content-hash verification and metric recomputation, use the CLI:

pnpm track-record:verify

This walks the full CID chain, validates schema, verifies signatures, recomputes performance metrics, and checks CID content hashes.