# Fork environments

> Fork six EVM networks at a pinned block or capture live Solana account state: impersonate any sender, override balances, share the state with your team.

Platform

Fork Ethereum, BNB Chain, Polygon, Arbitrum, Optimism or Base at any block, or capture live account state on Solana (SVM). Impersonate any sender and override balances — with no private keys and no exposure to live assets.

Fork environment panel showing a pinned mainnet fork with impersonated sender

Fork environments

## Real chain state, without touching the real chain

Every session runs on isolated chain state — pinned to a block on the EVM networks, captured live on Solana. That's what makes findings reproducible — and what makes it safe to reproduce one end to end.

- Scope: Six EVM L1s and L2s, plus Solana
- Pinned to: a block you choose (EVM networks)
- Keys: none; senders are impersonated
- State: saved with the session

- Fork **six EVM L1s and L2s** at any block, and **capture account state on Solana** — no setup on your side
- **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

Pinned state

## Mainnet moves on. The fork keeps the block you chose.

1. 22,847,310
2. 22,847,311
3. 22,847,312
4. 22,847,313

### Mainnet

- continues
- untouched
- read-only

### Trilocore fork

- sender override
- balance override
- transaction replay
- storage mutation

Per ecosystem

## What is captured, restored and reproduced

The two ecosystems do not work the same way, and the difference is in how history is addressed rather than in how much we cared: an EVM archive node makes state addressable by block, so a fork pins to the block you choose; Solana's standard RPC exposes current account state, so a session captures it live as your program touches it. Reconstructing a past Solana slot would take a different class of archival infrastructure, which is not what we run.

### EVM — six networks

State is read from an archive node, so the whole environment is addressable by block number.

- Captured: accounts and storage at one block
- Pinned to: a block you choose
- Restored: snapshot and revert, in session
- Reproduced: same block, same result

### Solana

Solana's standard RPC exposes current account state rather than an arbitrary historical slot, so accounts are fetched live from the cluster as your program touches them.

- Captured: accounts, on first read
- Pinned to: not available — state is live, not historical
- Restored: a session reopens on its captured account set
- Reproduced: the captured account set travels with the session
- Status: available

## One saved state is the shared ground truth.

[01ReproduceA finding is replayed on the same state it was found on — the pinned fork on EVM, the captured account set on Solana — it either reproduces or it is not reported.](https://trilocore.com/platform/auditing-ide) [02RehearseWork-in-progress contracts deploy against real protocol state before they ever see mainnet.](https://trilocore.com/platform/contract-ide) [03Re-deriveAnyone on the session can recompute a result from the same saved state and get the same answer.](https://trilocore.com/platform/analysis-engine)

## Fork the chain you work on.

Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base and Solana. Pin a block on any EVM network, capture live account state on Solana, impersonate a sender, and share the exact state with your team.

[Launch app](https://app.trilocore.ai/) [Platform overview](https://trilocore.com/platform/)

---

[Canonical HTML version](https://trilocore.com/platform/fork-environment)