EVM Perp Sandbox
The open, inspectable counterpart to Hyperliquid's closed perp engine.
An open take on the EVM perp market Hyperliquid dominates: CLOB matching, funding, a liquidation scanner, insurance fund, and ADL on a Reth-based stack — all exposed as a scenario surface you can inspect, replay, and fork before you commit to a rail.
Not transaction simulation against a live, deployed protocol — that is the operations layer. This is the engine itself: open, runnable, and forkable, before you build one.
Sandbox · Scenarios · Source
What you can do here
Open OpenHL — CLOB, funding, liquidation, insurance fund, ADL — and read every primitive in source.
Run crash, ADL, oracle, and margin scenarios — each emits a verifiable pass/fail report.
Turn a design dial (like maintenance margin) and watch the outcome shift — proof it bends to your needs.
Adopt the open source, or take it further with a custom build or hosted access.
- 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 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.
Make EVM Perp Sandbox your own.
Tell us what you are building. We will set up a private demo, run the scenarios at your own dial values, and map the path to adopt, customize, or host it.
Request early access →We read every submission ourselves · No auto-funnel