SHILDO Docs / Networks

Networks

Shildo routes liquidity across leading EVM chains with Solana delivery support. Base remains the settlement hub for proof verification and state roots.

Network topology

                    ┌──────── Base ────────┐
                    │  Settlement + proofs │
                    └──────────┬───────────┘
           ┌───────────────────┼───────────────────┐
           ▼                   ▼                   ▼
      Ethereum            Arbitrum            Solana
      Optimism            Polygon             (delivery)
      Avalanche           BNB Chain

Supported chains

NetworkChain id / clusterRoleStatus
Base8453Primary settlementLive (demo)
Ethereum1Source / destinationLive (demo)
Solanamainnet-betaDestination deliveryLive (demo)
Arbitrum42161L2 routingLive (demo)
Optimism10L2 routingLive (demo)
Polygon137L2 routingLive (demo)
Avalanche43114EVM routingLive (demo)
BNB Chain56EVM routingLive (demo)

Routing model

Outer chains use local token liquidity. Proofs settle on Base. Delivery relayers mint or transfer on the destination chain after root confirmation. Shildo does not require users to bridge assets to Base for every payment. Instead relayers maintain inventory on each chain and settle net positions against the Base root periodically.

Route selection criteria

  1. Destination chain support for recipient asset
  2. Relayer liquidity depth above payment amount
  3. Estimated fee and latency
  4. Historical reliability score for relayer set

EVM to Solana path

EVM originated intents include a Solana recipient pubkey in the encrypted payload. After Base verification, a Solana relayer submits a release instruction that credits the recipient token account. Public Solana explorers show relayer activity without linking back to the EVM sender for shielded routes.

Testnets

NetworkTestnetSDK network key
BaseBase Sepoliabase-sepolia
EthereumSepoliaethereum-sepolia
SolanaDevnetsolana-devnet

RPC requirements

Integrators need reliable RPC access to Base for proof submission and to destination chains for delivery confirmation. The SDK accepts custom rpcUrl per network. Production deployments should use redundant providers with failover.

Demo wallet note

The demo wallet network panel simulates chain metrics in Supabase. Switching network in the UI is cosmetic for the prototype. Production SDK calls target real RPC endpoints configured in the client.