EVM Perp Sandbox
A runnable perp sandbox for operators who want to own the engine.
A runnable EVM perp sandbox on a modern operator stack: CLOB matching, funding rate, liquidation scanner, insurance fund, and ADL, all exposed as a scenario surface you can inspect, replay, and fork.
Reactor is not protocol operations tooling for an existing venue. It is a pre-implementation sandbox for DeFi strategy, market structure, and risk design.
Sandbox dossier · Runnable evidence · Scenario surface
A runnable market-structure lab with fixed scenarios, explicit reports, and a source trail. This is not ops software for a deployed protocol. It is a sandbox dossier for a specific engine category before implementation.
Hyperliquid has captured EVM perp flows on a closed-source engine. The EVM Perp Sandbox is the open analog: Reth-based execution, custom EVM precompiles for the CLOB, BFT consensus, and a scenario suite that lets you stress the machine before you commit to the rail. Every piece is runnable, forkable, and auditable today.
In Fabrknt, EVM Perp is a pressure-bearing sandbox where market design, trust assumptions, and operational discipline all become legible under stress.
- ▸Reth + REVM
- ▸CLOB precompile
- ▸Funding rate
- ▸Liquidation scanner
- ▸Insurance fund
- ▸ADL
Full liquidation cascade — funding-rate stress drives margin breaches across positions, scanner emits close orders, insurance fund absorbs deficit, ADL fires on the residual.
Scenario tape · Market stress rendered as operator evidence
Every scenario emits a verifiable 5-section report — HEADLINE / TIMELINE / DELTA / OUTCOMES / NEXT. Declared outcomes pass ✓ or fail ✗ against the run's actual state.
Click any scenario marked ▶ below to load it in this player
Default maintenance margin (200 bps) — baseline outcomes scored against the declared scenario contract (9/9 outcomes ✓).
Tightened maintenance margin (500 bps) — same scenario, different dial; 8/9 outcomes ✓ with one declared outcome breaking.
Tightened maintenance margin (1000 bps) — 8/9 outcomes ✓; the same declared outcome breaks earlier under tighter requirements.
No stress — block production, funding settlement, and oracle aggregation tick along with no liquidation events. Ground-truth that the system is quiet when nothing's happening.
Genesis → first block production → first orderbook submission → first fill. Verifies the engine boots into a known-good state before any stress is applied.
Healthy ramp of open interest across multiple accounts before any stress event — the staging state every other scenario inherits.
Cascade compressed into a single block — verifies the per-block scanner pipeline handles all close orders in one consensus tick without re-entrancy.
Evaluate EVM Perp Sandbox for your team.
Tell us what mandate you are carrying. We follow up with a private demo, scenario walkthroughs against your dial values, and an advisory path once the fit is operationally real.
Request early access →We read every submission ourselves · No auto-funnel