Zap Pilot
Backtest

Track record: Verification

Verification

Each day, a snapshot of one reference address is published to IPFS under a CID derived from its content. Every snapshot links to the previous CID, so the history is tamper-evident. Snapshots are unsigned today: no official signer is configured, so the chain shows that the record was not edited, not who published it.

Backtest mode — the checks below describe the committed backtest dataset, not a published snapshot. Switch to Snapshots above to check the published snapshot chain.

Strategy logic verification

Recompute one DMA exit using the research Vyper slice on Arbitrum Sepolia. This covers version 1’s exit rule, not the production strategy.

Open the On-chain Calculator →

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, once snapshots are signed, their signatures. For full content-hash verification and metric recomputation, use the CLI:

pnpm track-record:verify

This walks the full CID chain, validates schema, recomputes performance metrics, and checks CID content hashes. Until snapshots are signed it reports the official signer as none.