Mayavi

Phase 4 · design-partner preview

Run a forked-mainnet simulation.

Submit a registered scenario, watch the EVM step loop execute on real mainnet bytecode, and pull the report with bit-exact validation against on-chain truth.

Start a runView runs

What ships in this dashboard

5 EVM + 1 SVM
registered scenarios
Vesting cliff · multi-cohort · Aave borrower · depeg cascade · launch replay + Solana cliff replay.
delta == 0
5/5 swaps bit-exact
Validated against Uniswap V3 Quoter and the EIGEN airdrop replay. Tolerance gaps documented honestly.
Forked mainnet
real revm bytecode
pyrevm against pinned-block state — same EVM that runs Aave today, not a Python re-implementation.
Seconds to minutes
end-to-end runs
Vesting cliff ≈ 20 s; multi-agent depeg cascade ≈ 2 min on commodity hardware.

How a run flows.

Five stages, one forked-mainnet kernel, deterministic per pinned block. The same pipeline runs on a laptop, on Modal A10G, and on the deployed dashboard.

  1. Step 1
    Mainnet RPC
    Alchemy fork pinned to a specific block.
  2. Step 2
    Forked EVM
    pyrevm wraps revm; storage cache + snapshots.
  3. Step 3
    Scenario
    Multi-agent scheduler, configurable cohorts.
  4. Step 4
    Validate
    Bit-exact swap match against on-chain Quoter.
  5. Step 5
    Report
    HTML + PDF; KPIs, cohort tables, lifecycle data.

Run lifecycle.

Each submission progresses through four states. Reports gate to complete; non-terminal or failed runs return 409 on the report endpoint.

Queued

Submission accepted; the FastAPI BackgroundTask has not picked it up yet.

Running

Forked EVM is executing the scenario step loop; partial state persists per step.

Complete

Scenario finished cleanly; report HTML + PDF available for download.

Failed

Setup or step raised an exception; the error message and stack trace are persisted.

Where to next.

Every page below is hot-linkable; bookmark a scenario submission form for a workflow you re-run weekly.

Scenarios
Browse the 6 registered scenario types and submit a new run via the schema-driven form.
Runs
Paginated history (newest first); each row links to the run detail with embedded report and PDF download.