Try it Live

Run Chain examples in the interactive playground

BrandedChain

Tree-shakeable functional API for Chain operations with optimal bundle size.

Overview

BrandedChain is the functional layer underlying the Chain class. It provides:

Zero-overhead type wrapping for chain configuration objects
Tree-shakeable individual function exports
Data-first unopinionated methods taking chain as first parameter
Bundle optimization through selective imports

Primary benefit: When using tree-shakeable imports, you can include only the specific chain lookup functionality you need, or import individual chain objects to minimize bundle size.

Type Definition

export type Chain = {
  name: string
  chain: string
  chainId: number
  networkId?: number
  shortName: string
  rpc: string[]
  nativeCurrency: NativeCurrency
  infoURL?: string
  explorers?: Explorer[]
  [key: string]: any
}

Plain JavaScript object with chain configuration. No special branding beyond TypeScript type safety. Defined in: primitives/Chain/ChainType.ts

Available Functions

All Chain functionality available as tree-shakeable functions:

Constructors

import { from, fromId } from 'tevm/BrandedChain'
import { mainnet } from 'tevm/chains'

const chain1 = from(mainnet)
const chain2 = fromId(9)

See Constructors for details.

Chain Lookup

import { fromId, byId } from 'tevm/BrandedChain'

// Function-based lookup
const quai = fromId(9)

// Record-based lookup
const flare = byId[14]

See Chain Lookup for details.

Data-First Pattern

All BrandedChain functions follow data-first pattern:

// BrandedChain: chain is first parameter (where applicable)
from(chain)
fromId(id)

// vs Chain class: uses static methods
Chain(chain)
Chain.fromId(id)

This enables functional composition and partial application:

import { fromId } from 'tevm/BrandedChain'

// Function composition
const getChainName = (chainId: number) => fromId(chainId)?.name

// Array methods
const chainIds = [9, 14, 1776]
const chains = chainIds
  .map(fromId)
  .filter((chain): chain is Chain => chain !== undefined)

chains.forEach(chain => {
  console.log(chain.name)
})

Tree-Shaking Strategies

Strategy 1: Import Specific Chains (Smallest Bundle)

Best for: Applications using a fixed set of known chains.

import { quai9, flr14, ronin2020 } from 'tevm/chains'

// Only these 3 chains in bundle
const chains = [quai9, flr14, ronin2020]

function getChain(chainId: number) {
  return chains.find(c => c.chainId === chainId)
}

const quai = getChain(9)

Bundle size: ~1KB (only the chains you import)

Strategy 2: Import Registry Functions (Larger Bundle)

Best for: Applications with dynamic chain selection.

import { fromId, byId } from 'tevm/BrandedChain'

// Full chain registry in bundle
const quai = fromId(9)
const flare = byId[14]

// Supports any chain ID at runtime
function getChain(userChainId: number) {
  return fromId(userChainId)
}

Bundle size: ~150KB (entire chain registry with 800+ chains)

Strategy 3: Hybrid Approach (Balanced)

Best for: Applications with common chains but occasional dynamic lookup.

import { quai9, flr14, ronin2020 } from 'tevm/chains'
import { fromId } from 'tevm/BrandedChain'

// Common chains available without lookup
const COMMON_CHAINS = [quai9, flr14, ronin2020]

function getChain(chainId: number) {
  // Try common chains first
  const common = COMMON_CHAINS.find(c => c.chainId === chainId)
  if (common) return common

  // Fall back to full registry
  return fromId(chainId)
}

Bundle size: ~150KB (but common chains fast-path)

Strategy 4: Code Splitting (Best of Both)

Best for: Large applications with route-based chain usage.

// Common chains in main bundle
import { quai9, flr14 } from 'tevm/chains'

// Lazy load registry for admin panel
async function loadFullRegistry() {
  const { fromId } = await import('tevm/BrandedChain')
  return fromId
}

// User-facing pages use common chains
function getUserChain(chainId: number) {
  if (chainId === 9) return quai9
  if (chainId === 14) return flr14
  return null
}

// Admin pages can load full registry
async function getAdminChain(chainId: number) {
  const fromId = await loadFullRegistry()
  return fromId(chainId)
}

Bundle size:

Main bundle: ~1KB
Admin bundle: +150KB (loaded on demand)

Bundle Size Comparison

Import Strategy	Bundle Size	Flexibility	Use Case
Specific chains only	~1KB	Low	Fixed chains, production apps
`from()` only	~1KB	Low	Wrapper around chain objects
`fromId()` or `byId`	~150KB	High	Dynamic chain selection
Hybrid	~150KB*	Medium	Common + dynamic
Code splitting	1KB + 150KB†	High	Large apps, route-based

* Full registry included † Loaded on demand

Usage Examples

Minimal Bundle (Fixed Chains)

import { quai9, flr14 } from 'tevm/chains'
import { from } from 'tevm/BrandedChain'

// Wrap with Chain class if needed
const quai = from(quai9)
const flare = from(flr14)

console.log(quai.name)  // "Quai Mainnet"
console.log(flare.name) // "Flare Mainnet"

Dynamic Chain Loading

import { fromId } from 'tevm/BrandedChain'

function loadChain(chainIdFromUser: number) {
  const chain = fromId(chainIdFromUser)

  if (!chain) {
    throw new Error(`Unknown chain ID: ${chainIdFromUser}`)
  }

  return chain
}

// Supports any registered chain
const chain = loadChain(9)
console.log(chain.name) // "Quai Mainnet"

Multi-Chain Application

// app.ts - Main bundle with common chains
import { quai9, flr14, ronin2020 } from 'tevm/chains'

export const SUPPORTED_CHAINS = [quai9, flr14, ronin2020]

export function getChain(chainId: number) {
  return SUPPORTED_CHAINS.find(c => c.chainId === chainId)
}

// admin.ts - Admin panel with full registry
import { fromId } from 'tevm/BrandedChain'

export function getAllChains() {
  return Object.values(byId)
}

export function findChain(chainId: number) {
  return fromId(chainId)
}

Functional Composition

import { fromId } from 'tevm/BrandedChain'
import type { Chain } from 'tevm/BrandedChain'

// Compose functions
const getChainName = (id: number) => fromId(id)?.name ?? 'Unknown'
const getChainSymbol = (id: number) => fromId(id)?.nativeCurrency.symbol ?? '?'
const getChainRpc = (id: number) => fromId(id)?.rpc[0] ?? ''

// Use in pipelines
const chainIds = [9, 14, 1776, 2020]

const names = chainIds.map(getChainName)
const symbols = chainIds.map(getChainSymbol)
const rpcs = chainIds.map(getChainRpc)

console.log(names)   // ["Quai Mainnet", "Flare Mainnet", ...]
console.log(symbols) // ["QUAI", "FLR", ...]
console.log(rpcs)    // ["https://...", ...]

Type-Safe Chain Operations

import { fromId } from 'tevm/BrandedChain'
import type { Chain } from 'tevm/BrandedChain'

function requireChain(chainId: number): Chain {
  const chain = fromId(chainId)

  if (!chain) {
    throw new Error(`Chain ${chainId} not found`)
  }

  return chain
}

function processChain(chain: Chain): void {
  console.log(`Processing ${chain.name}...`)
  console.log(`RPC: ${chain.rpc[0]}`)
  console.log(`Symbol: ${chain.nativeCurrency.symbol}`)
}

// Type-safe pipeline
try {
  const chain = requireChain(9)
  processChain(chain)
} catch (error) {
  console.error(error.message)
}

When to Use BrandedChain vs Chain

Use BrandedChain When:

Bundle size critical (mobile, embedded)
Fixed chain set (production apps)
Tree-shaking important
Functional style preferred
Direct imports from tevm/chains

Use Chain Class When:

Dynamic chains needed
Convenience over size
Traditional API preferred
Prototype methods desired

Interoperability

BrandedChain and Chain are fully compatible:

import { Chain } from 'tevm'
import { fromId } from 'tevm/BrandedChain'
import { quai9 } from 'tevm/chains'

// BrandedChain functions work with Chain class
const chain1 = Chain(quai9)
const chain2 = fromId(9)

// Both are plain objects with same structure
console.log(chain1.chainId) // 9
console.log(chain2?.chainId) // 9

Re-exports from tevm/chains

BrandedChain re-exports all chains from tevm/chains:

import {
  // Re-exported chains
  quai9,
  flr14,
  injective1776,
  ronin2020,
  moca2288,

  // Re-exported utilities
  getChainById,
  chainById,
  allChains,

  // BrandedChain functions
  from,
  fromId,
  byId,
} from 'tevm/BrandedChain'

This provides a single import path for all chain-related functionality.

Chain - Main Chain class documentation
Constructors - Creating chains
Chain Lookup - Looking up chains by ID
Metadata - Chain properties
tevm/chains - Chain registry source

Overview

Getting Started

Core Concepts

Skills

JSONRPCProvider

Contract

Primitives

Cryptography

EVM

Utils

Guides

Examples

Swift

Zig

Developer Documentation

Generated API (TypeDoc)

Try it Live

​BrandedChain

​Overview

​Type Definition

​Available Functions

​Constructors

​Chain Lookup

​Data-First Pattern

​Tree-Shaking Strategies

​Strategy 1: Import Specific Chains (Smallest Bundle)

​Strategy 2: Import Registry Functions (Larger Bundle)

​Strategy 3: Hybrid Approach (Balanced)

​Strategy 4: Code Splitting (Best of Both)

​Bundle Size Comparison

​Usage Examples

​Minimal Bundle (Fixed Chains)

​Dynamic Chain Loading

​Multi-Chain Application

​Functional Composition

​Type-Safe Chain Operations

​When to Use BrandedChain vs Chain

​Use BrandedChain When:

​Use Chain Class When:

​Interoperability

​Re-exports from tevm/chains

​Related

BrandedChain

Overview

Type Definition

Available Functions

Constructors

Chain Lookup

Data-First Pattern

Tree-Shaking Strategies

Strategy 1: Import Specific Chains (Smallest Bundle)

Strategy 2: Import Registry Functions (Larger Bundle)

Strategy 3: Hybrid Approach (Balanced)

Strategy 4: Code Splitting (Best of Both)

Bundle Size Comparison

Usage Examples

Minimal Bundle (Fixed Chains)

Dynamic Chain Loading

Multi-Chain Application

Functional Composition

Type-Safe Chain Operations

When to Use BrandedChain vs Chain

Use BrandedChain When:

Use Chain Class When:

Interoperability

Re-exports from tevm/chains

Related