You can enable any Cosmos network that we do not currently support in our dashboard by passing an array of GenericNetwork
to the DynamicContextProvider
’s overrides.cosmosNetworks
settings.
This can be done in two different ways:
By passing an array of GenericNetwork
, it completely overrides whatever networks were received from your dashboard configurations and uses that array instead.
By passing a method with signature (dashboardNetworks: GenericNetwork[]) => GenericNetwork[]
, 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.
The following example sets Sei for the application. Remember to enable the cosmos blockchain in the dashboard
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 |
Attribute | Value | Required/Optional |
---|---|---|
decimals | number | Required |
name | string | Required |
symbol | string | Required |
denom | string | Optional |
You can enable any Cosmos network that we do not currently support in our dashboard by passing an array of GenericNetwork
to the DynamicContextProvider
’s overrides.cosmosNetworks
settings.
This can be done in two different ways:
By passing an array of GenericNetwork
, it completely overrides whatever networks were received from your dashboard configurations and uses that array instead.
By passing a method with signature (dashboardNetworks: GenericNetwork[]) => GenericNetwork[]
, 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.
The following example sets Sei for the application. Remember to enable the cosmos blockchain in the dashboard
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 |
Attribute | Value | Required/Optional |
---|---|---|
decimals | number | Required |
name | string | Required |
symbol | string | Required |
denom | string | Optional |