feat: Add Avalanche C-Chain network support

[AugustoL]

Summary

Add support for Avalanche C-Chain (chain ID: 43114) network exploration in OpenScan.

Context

Avalanche C-Chain is EVM-compatible, making integration straightforward using existing L1 adapters. It's one of the largest L1s by TVL with a strong DeFi ecosystem.

Scope

explorer-network-connectors

• Add Avalanche public RPC endpoints
• Verify compatibility with existing EVM fetchers

explorer-metadata

• Add Avalanche network configuration
• Add Avalanche logo and branding assets
• Add popular Avalanche contract tags (AVAX, Trader Joe, Aave, etc.)

explorer (this repo)

• Add Avalanche to networks.json
• Configure default RPC endpoints
• Test block, transaction, and address pages
• Verify contract verification via Sourcify

Network Details

• Chain ID: 43114
• Currency: AVAX
• Block Explorer: snowtrace.io
• RPC Endpoints:
  • https://api.avax.network/ext/bc/C/rpc
  • https://avalanche.public-rpc.com
  • https://rpc.ankr.com/avalanche

Technical Considerations

• Standard EVM-compatible chain (should work with L1 adapters)
• High throughput - may need pagination tuning
• Snowtrace API for additional data if needed

Labels

enhancement, network-support, good-first-issue

[MiltonTulli]

Hey @AugustoL! I've opened a PR to add Avalanche C-Chain support: #275. There's also a companion PR in the metadata repo (openscan-explorer/explorer-metadata#12) for the RPC endpoints. Would love your review if you get a chance!

[AugustoL]

@MiltonTulli thanks! Ive checked the code and it looks good but it is missing a key component, in fact, it is missing the first thing you should work on which is the network connector for avalanche. But you are very close!

The next thing you should do is to add the avalanche c chain connector on https://github.com/openscan-explorer/network-connectors, check out how the other networks are handled and how the tests are ran. Once you added the avalanche c-chain connector we can test the connector integration on the explorer and then finally add it on the metadata.

Also this would be minor releases, so propose the PRs against dev branches on connectors and explorer with a minor version release increased.

This already helps a lot! take your time to work on this, no hurry :)