Good question. Looking at the repo, chain configs live in src/chains/ — there are currently files for base.ts, optimism.ts, and zora.ts.

Adding Mode support would follow the same pattern. Here's a draft mode.ts based on the contract addresses from Mode's documentation:

// src/chains/mode.ts
import { defineChain } from 'viem'
import { chainConfig } from 'viem/op-stack'

export const mode = defineChain({
  ...chainConfig,
  id: 34443,
  name: 'Mode',
  nativeCurrency: { name: 'Ether', symbol: 'ETH', decimals: 18 },
  rpcUrls: {
    default: { http: ['https://mainnet.mode.network'] },
  },
  blockExplorers: {
    default: { name: 'Modescan', url: 'https://modescan.io' },
  },
  contracts: {
    ...chainConfig.contracts,
    l2OutputOracle: {
      1: { address: '0x4317ba146D4933D889518a3e5E11Fe7a53199b04' },
    },
    multicall3: {
      address: '0xcA11bde05977b3631167028862bE2a173976CA11',
      blockCreated: 5022,
    },
    portal: {
      1: { address: '0x8B34b14c7c7123459Cf3076b8Cb929BE097d0C07' },
    },
    l1StandardBridge: {
      1: { address: '0x735aDBbE72226BD52e818E7181953f42E3b0FF21' },
    },
  },
  sourceId: 1, // Ethereum mainnet
})

Re: a "documented way to expand to other superchains" — there isn't one yet beyond reading the existing chain files as a template. A short CONTRIBUTING.md section documenting how to add a new OP Stack chain (what contract addresses are required, how to test) would be a nice addition alongside any new chain PR.

I can submit a PR with the mode.ts chain config and a contributing note if the maintainers are open to it.

op-viem for mode #188

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions