Skip to Content
Customisation

Customisation

Every protocol depends on things outside its own contracts: oracles, bridges, keepers and the third-party protocols it integrates with. On a Stagenet, these behave as they do on mainnet, through Mainnet Replay. Customisation goes further. We build tooling with your team that simulates those dependencies, so you can put them into any state and see how your protocol behaves when they move, slow down or fail.

Each customisation is built for your application. Talk to us about what you need to simulate.

DeFi protocol state and activity, on demand

Put the third-party protocols you integrate with into the state you need, when you need it, and run realistic activity through them. For example:

  • Push a lending market to full utilisation, or change its interest rates.
  • Drain a pool’s liquidity, or move its price.
  • Run trading, lending, borrowing and liquidity flows from simulated users.
  • Stage a rush of withdrawals from a vault or market.

For real activity in place of simulated activity, a Stagenet can replay selected mainnet transactions. See transaction replay.

Oracles

Control the prices your protocol reads. For example:

  • Set a price feed to any value, or move it gradually over a period.
  • Simulate a crash or a depeg: ETH down 40% in an hour, or a stablecoin trading at $0.95.
  • Let a feed go stale, or stop it updating altogether.

Bridges and cross-chain messages

Test flows that cross chains. For example:

  • Deliver cross-chain messages between Stagenets, such as deposits from Ethereum to Base.
  • Delay messages by minutes or hours, or drop them.
  • Pause a bridge, or fail a relay partway through.

Keepers and other services

Simulate the off-chain services your protocol relies on. For example:

  • Run liquidators, keepers and relayers against your Stagenet.
  • Slow them down, or switch them off.
  • Take an L2 sequencer offline, as seen by the contracts that check its status.

Example scenarios

  • A lending market crash. Drop the collateral price 40% over an hour, push borrow utilisation to 100% and switch off one of the liquidation keepers. Check that liquidations still clear and the protocol stays solvent.
  • Thin liquidity for a trading integration. Move prices across the pools your integration routes through and drain half their liquidity. Check that quotes, slippage limits and fallbacks still protect users.
  • A cross-chain vault under stress. Delay withdrawal messages by six hours while the vault’s main asset depegs. Check that accounting stays correct on both chains and no withdrawal is paid twice.
  • A stale oracle. Stop a price feed updating while the market moves. Check that the protocol pauses or rejects stale prices instead of acting on them.
Last updated on