Skip to main content

Shadow Mainnet Testing Explained

What it is​

Shadow Mainnet Testing is an operational phase in which Multyr's smart contracts are deployed on Arbitrum One (mainnet, not a testnet) and the system runs real on-chain operations against real DeFi state, but:

  • deposits are not accepted from the public
  • the system operates with controlled, non-public capital
  • the behavior observed is logged, reviewed, and used to validate the system against conditions that no testnet can reproduce

What it is not​

  • It is not a testnet deployment
  • It is not a live production system open to users
  • It is not a mainnet soft-launch

Why we do it​

Testnets cannot reproduce:

  • real oracle latency and behavior under congestion
  • real gas dynamics under Arbitrum sequencer conditions
  • real liquidity conditions in underlying protocols (Aave, Morpho, etc.)
  • real MEV dynamics
  • real interactions with the full set of production contracts our strategies depend on

Shadow testing on mainnet is the only way to validate these. We do it with non-public capital so that any unexpected behavior impacts only the testing configuration, not allocators.

What we validate​

  • Allocation decisions produce expected state transitions
  • Rebalances execute within cost-benefit bounds
  • Oracle staleness and deviation checks fire correctly
  • SAFE_GUARDIAN pause and DEGRADED/BROKEN transitions behave as specified
  • Withdrawal paths (instant, queued, force) all function against real liquidity
  • Per-strategy and aggregate loss caps enforce correctly
  • Emergency procedures execute as specified

How long it lasts​

Shadow testing ends when:

  1. Validation objectives are met
  2. The protocol core external audit is engaged and completed
  3. Audit findings are remediated
  4. Bug bounty is live

At that point, we transition to Phase 6 (Guarded Launch / Beta Access).

What you can do now​

What you cannot do now​

  • Deposit capital
  • Receive any form of reward or airdrop (there is none planned at this phase)
  • Access the app beyond public read-only views

Why we publish this document​

Allocators need clarity about operational state. "Shadow Mainnet Testing" is not a common term, and we want its meaning to be unambiguous for anyone evaluating Multyr.