Custom EVM networks
For adding a custom EVM networks with Wagmi see: WAGMI - adding custom networks
You can enable any EVM network that we do not currently support out of the box by passing an array of EvmNetwork
to the DynamicContextProvider
’s overrides.evmNetworks
settings.
This can be done in two different ways:
-
By passing an array of
EvmNetwork
, it completely overrides whatever networks were received from your dashboard configurations and uses that array instead. -
By passing a method with signature
(dashboardNetworks: EvmNetwork[]) => EvmNetwork[]
, you can use this callback to first receive the array of networks that was sent from your dashboard configurations, and then return the array of networks you want the app to use.
The second approach is best for making adjustments to the networks you get from our dashboard (like changing rpc urls), as well as when you want to hide some specific networks.
If you’re just trying to merge new networks with the ones from dashboard, we have a helper function that will make that easier:
Note that the order of the params for
mergeNetworks
matters: the first param takes precedence in case of a conflict.
Example
The following example sets the Ethereum mainnet and Polygon as supported networks for the application. A comprehensive list of networks can be found at chainlist.org
Type Reference
Definition
Attribute | Value | Required/Optional |
---|---|---|
blockExplorerUrls | string[] | Required |
chainId | number | Required |
name | string | Required |
iconUrls | string[] | Required |
nativeCurrency | NativeCurrency | Required |
networkId | number | Required |
privateCustomerRpcUrls | string[] | Optional |
rpcUrls | string[] | Required |
vanityName | string | Optional |
NativeCurrency
Attribute | Value | Required/Optional |
---|---|---|
decimals | number | Required |
iconUrl | string | Optional |
name | string | Required |
symbol | string | Required |
denom | string | Optional |
Was this page helpful?