Multi-Layer Network

Last updated: 2026-06-28

Cortensor uses a multi-layer strategy across L2 and L3 environments. The goal is to support fast iteration, inexpensive execution, and a path from shared L2 deployments toward a dedicated COR-gas appchain.

flowchart TB
  Dev["Developer and operator testing"]
  Testnet0["Testnet-0<br/>Arbitrum Sepolia path"]
  Testnet1["Testnet-1<br/>COR-gas L3 path"]
  MainnetLite["Mainnet-Lite<br/>Arbitrum mainnet path"]
  MainnetFull["Mainnet-Full<br/>COR L3 appchain path"]

  Dev --> Testnet0
  Dev --> Testnet1
  Testnet0 --> MainnetLite
  Testnet1 --> MainnetFull
  MainnetLite --> MainnetFull

Network Terms

Term	Meaning
Testnet-0	Arbitrum Sepolia path for fast iteration.
Testnet-1	COR-gas L3 rollup path.
Mainnet-Lite	Arbitrum mainnet production path.
Mainnet-Full	COR L3 sovereign appchain path.

Network Strategy

The network path is framed as a progressive migration:

Phase	Role in the strategy
Shared L2 testing	Fast iteration, easier wallet/RPC access, and lower friction for early node and app testing.
COR-gas L3 testing	Exercises Cortensor-specific gas, sequencing, explorer, and deployment patterns.
Mainnet-Lite	Production path on a shared L2 while the dedicated appchain matures.
Mainnet-Full	Dedicated Cortensor appchain path for lower-level control over AI inference data, economics, and coordination.

This model separates user-facing APIs from deployment mechanics. Web2 developers can use Portal or router endpoints without needing every chain detail; operators and Web3 developers need the full chain/RPC/contract matrix.

Deployment Matrix

Field	Why it matters
Chain ID	Needed for wallets, SDKs, and scripts.
RPC URL	Needed for nodes, dashboards, and contract clients.
Explorer URL	Needed for verification and user support.
Bridge URL	Needed for onboarding funds or gas.
Contract addresses	Needed for routers, nodes, and Web3 SDK examples.
Last verified date	Prevents stale network instructions from being reused.

Operator Impact

Area	What changes by network
Node registration	Contract address, gas token, and chain RPC.
Router session mapping	Session IDs, queue modules, default model pools, and retry policies.
Dashboard views	Network selector, explorer links, admin/write-action targets.
Portal/gateway	Managed router pool URLs, model aliases, billing/metering environment.
Documentation examples	Every Web3 example must name the network it targets.

Network Labels

Setup guides pair each network label with chain, RPC, explorer, bridge, contract, and last-updated information.