Zap Pilot— rules engineZap Pilot
Pending first snapshot

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.

Loading verification data…

Methodology

Pricing time
Daily valuation at 00:00 UTC using Chainlink or equivalent oracle.
Price oracle source
Primary: Chainlink price feeds. Fallback: last known price, flagged in snapshot.
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 oracle prices, summed per asset, then per pillar.
Stablecoin depeg handling
Stablecoin positions valued at 1.0 USD unless oracle reports deviation >0.5%, in which case the oracle price is used.

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.