feat: add Avalanche C-Chain network support#275
feat: add Avalanche C-Chain network support#275MatiasOS merged 3 commits intoopenscan-explorer:devfrom
Conversation
Add support for Avalanche C-Chain, a standard EVM-compatible chain with high throughput. Implements network configuration, RPC client initialization (via direct EthereumClient instantiation since not in ClientFactory), and adapter routing. Closes openscan-explorer#113. - Add Avalanche C-Chain entry to networks.json with CAIP-2 identifier and metadata - Update DataService to create EthereumClient for unsupported chains - Update AdapterFactory and NetworkAdapter to handle chain 43114 - Route to EVMAdapter (standard EVM implementation)
|
🚀 Preview: https://pr-275--openscan.netlify.app |
Consolidate scattered union types (SupportedChainId | 11155111 | 97 | 31337 | 43114) into a single AppChainId type, making it easier to add new networks.
|
@AugustoL Do we need to update Metadata repo before merge this? |
PR merged and we have 1.1.2-alpha.0 on metadata ready to be used for this PR |
|
Just review the avax docs, and there are non standard methods. I'll create a new Issue to add it to network-connectos. Aside the standard/similar methods (eth_callDetailed, eth_getChainConfig), theere is a bunch of specific ones (warp_, avax_) |
great, lets do it. |
Marking this PR as draft until openscan-explorer/network-connectors#19 (or similar) is merged and a new tag/version of network-connectors is released. This PR depends on changes introduced there. |
|
Hola @MiltonTulli , network connectors v1.4.0 is here (: |
…port Update @openscan/network-connectors to v1.4.0 which includes native AvalancheClient (43114). Remove the EthereumClient workaround for unsupported chains and use ClientFactory directly. Simplify AppChainId type since 43114 is now part of SupportedChainId.
3 participants
Description
Add support for Avalanche C-Chain (chain ID 43114), an EVM-compatible smart contract platform with high throughput. This implementation includes network configuration, RPC client initialization, and adapter routing to support block, transaction, and address queries on Avalanche.
Related Issue
Closes #113
Type of Change
Changes Made
networks.jsonwith network metadata (name, currency, logo, links)DataServiceto createEthereumClientdirectly for chains not registered inClientFactory(Avalanche is standard EVM-compatible)AdapterFactoryto route chain 43114 toEVMAdapterNetworkAdapterandEVMAdapterto include 43114Checklist
npm run format:fixandnpm run lint:fixnpm run typecheckwith no errorsnpm run test:runAdditional Notes
Avalanche C-Chain uses the standard EVM adapter (same as Ethereum, Sepolia, localhost) since it's fully EVM-compatible. Network logo is served from CDN. RPC endpoints will be fetched automatically from the metadata service.