Skip to Content
Overview

Staging

contract.dev offers teams private EVM testnets, called Stagenets, that replay mainnet state and transactions, with custom simulation tooling built around your application.

A Stagenet holds a real chain’s production state (contracts, liquidity, prices and accounts) and keeps it up to date as new blocks land, in an environment only your team uses. It can also replay selected mainnet transactions, so real user and DeFi activity runs on it when you need it. Your contracts run against the same protocols, liquidity, prices and activity they will meet in production.

Staging is available on request and set up to your requirements. Talk to us to get started.

Capabilities

CapabilityDescription
Full EVM compatibilityOn supported chains.
Mainnet replayMainnet state kept up to date as new blocks land, and selected mainnet transactions replayed for real user and DeFi activity. See Mainnet Replay.
Full JSON-RPCThe standard JSON-RPC API. Existing applications, wallets and development tools connect unchanged.
Block explorerTransactions, contracts and activity on your Stagenet.
Testing toolsFund wallets, send transactions as any address and set state directly. See Testing tools.
CLI and SDKManage and drive Stagenets from scripts, CI and coding agents.
CustomisationSimulated oracles, bridges and third-party protocol activity, built for your application. See Customisation.

What teams use Stagenets for

  • Staging releases. Deploy an upgrade or a parameter change and see how it behaves against current mainnet state, and against your users’ real transactions, before it goes live.
  • Testing integrations. Call the real deployments of the protocols you integrate with, such as their pools, markets and oracles, instead of mocks.
  • Reproducing incidents. Recreate what happened on mainnet against current state, then test the fix.
  • Long-running staging environments. Give frontends, QA, partners and integrators a testnet that still looks like mainnet weeks later.

Working with a Stagenet

Point Hardhat, Foundry, viem, ethers.js, wallets, deployment scripts and frontends at the Stagenet’s RPC URL, and deploy with your normal scripts. Your contracts don’t change.

A Stagenet has its own chain ID, so wallets add it as a separate network. Transactions pay gas in the chain’s native token, such as ETH on an Ethereum Stagenet. The testing tools below fund your wallets.

Testing tools

Every Stagenet comes with tools for putting accounts and contracts into an exact state:

ToolWhat it does
Funded walletsCreate a funded wallet, or top up any address with native tokens or any ERC-20.
ImpersonationSend transactions as any address, such as a protocol’s admin, a multisig or a large holder, without its private key.
State overridesSet an account’s balance, code, nonce or storage directly.
Function overridesMake a contract function return a fixed value without changing its code.

These tools set one value at a time. For realistic, changing conditions such as oracle updates, bridge messages and third-party activity, see Customisation.

Stagenets, forks and public testnets

EnvironmentGood forAs a staging environment
Local forkFast one-off tests against a snapshot of mainnet.Fixed at one block, on one machine, with nothing for the team to share.
Public testnetRehearsing a public deployment, and testing frontends and wallets.Liquidity, prices, oracles and activity differ from mainnet, and the protocols you integrate with may not be there.
StagenetStaging before mainnet.Private and long-lived, follows mainnet state, and shared by your team.

How we set it up

  1. Tell us what you need to test: the chains, the protocols you depend on, and the scenarios that worry you.
  2. We set up your Stagenets and connect them to your existing stack: deployment scripts, CI and frontends.
  3. We build the simulations and tooling your team needs.
  4. Your team tests with the tools it already uses, over JSON-RPC, and drives Stagenets from the CLI and SDK.

Learn more

  • Mainnet Replay — How a Stagenet keeps following mainnet, replays selected transactions and keeps your changes.
  • Customisation — Simulated protocols, oracles and bridges, with example scenarios.
Last updated on