Built-in Networks

Every workspace opens with 14 networks already loaded — eleven EVM networks and three Solana clusters. The same set is reachable two ways: as typed static constants on the Network class (Network.Ethereum, Network.Base, …), and as the BUILTIN_NETWORKS registry keyed by slug. Both come from the main entry:

import { Network, BUILTIN_NETWORKS } from "wative-core";
import type { NetworkConfig } from "wative-core";

Network.<Name> statics

Each accessor is a shared, read-only Network instance. They are the same objects a fresh workspace loads, so ws.networks.bySlug("base") and Network.Base describe the same chain (though a workspace may override any of them locally with update()).

Network.Ethereum.chainId;        // 1
Network.ArbitrumSepolia.chainId; // 421614
Network.Solana.vm;               // "svm"
Network.Base.symbol;             // "ETH"

The Network class also exposes a few helpers over this set:

BUILTIN_NETWORKS

BUILTIN_NETWORKS is a frozen Record<string, NetworkConfig> keyed by slug — the plain-data source the static constants are built from. Use it when you want the configuration values without constructing a Network:

BUILTIN_NETWORKS["base"].chainId;   // 8453
BUILTIN_NETWORKS["solana"].vm;      // "svm"
Object.keys(BUILTIN_NETWORKS).length; // 14

NetworkConfig

interface NetworkConfig {
  readonly slug: string;
  readonly name: string;
  readonly chainId: number;
  readonly vm: ChainVM;
  readonly rpcUrl: string;
  readonly nativeCurrency: {
    readonly name: string;
    readonly symbol: string;
    readonly decimals: number;
  };
}

Solana chain ids (changed in 2.4.7)

Solana has no EIP-155-style chain-id space, so the library assigns each cluster a stable numeric id for lookups such as byChainId:

Related