Fork environments — Trilocore

fork — mainnet · pinned 22,847,313

// isolated fork of real chain state
chain    mainnet (chain_id 1)
block    22,847,313 (pinned — deterministic)
sender   0xd8dA…6045 (impersonated, no key)
balance  overridden → 1,000 ETH
session  shared with @audit-team ● live
// same state, both sides — no "works on my fork"

Fork state is saved with the session — reopen an audit exactly where it stopped.

Fork environments

Real chain state, without touching the real chain

Every session runs on an isolated fork of live chain state, pinned to a block. That's what makes findings reproducible — and what makes it safe to try the exploit.

Fork any EVM L1 or L2 at any block — no per-chain integration work
Impersonate any sender and override balances — no private keys involved
Share the fork, not a screenshot: teammates join the same state, live
Deploy work-in-progress contracts against real protocol state before mainnet
Forks are isolated and disposable — break things freely

Real chain state, without touching the real chain

Fork any EVM chain.