Skip to content

feat(eip155): add XDC Network (50) and XDC Apothem testnet (51)#238

Open
AnilChinchawale wants to merge 1 commit into
graphprotocol:mainfrom
AnilChinchawale:feat/add-xdc-network
Open

feat(eip155): add XDC Network (50) and XDC Apothem testnet (51)#238
AnilChinchawale wants to merge 1 commit into
graphprotocol:mainfrom
AnilChinchawale:feat/add-xdc-network

Conversation

@AnilChinchawale

Copy link
Copy Markdown

Summary

Adds XDC Network mainnet (eip155:50) and XDC Apothem testnet (eip155:51) to the registry under registry/eip155/.

XDC is an EVM-compatible L1 (XDPoS consensus). Both chains are present in ethereum-lists/chains and on the Etherscan V2 unified API, and both support EIP-1559. Entries follow the same metadata-only shape as the 54 existing service-less networks (e.g. metis, aurora, vana) — services.subgraphs is left empty pending Graph indexing support, so this is purely additive chain metadata.

Files

  • registry/eip155/xdc.json — XDC Network (mainnet 50)
  • registry/eip155/xdc-testnet.json — XDC Apothem (testnet 51), testnetOfxdc

Validation

bun validate passes (schema + logic) with 0 errors. The only output is the standard "has no web3icon" warning (shared by existing entries like xlayer-sepolia); a web3icon can be wired up once XDC lands in web3icons.

Notes

  • explorer: xdcscan.com / testnet.xdcscan.com (Etherscan V2)
  • apiUrls use the Etherscan V2 form api.etherscan.io/v2/api?chainid=50|51
  • native token: XDC / TXDC

Adds metadata entries for XDC Network mainnet (eip155:50) and XDC Apothem
testnet (eip155:51), consistent with the 54 existing service-less network
entries. XDC is an EVM L1 (XDPoS); both chains are on the Etherscan V2
unified API and support EIP-1559. `bun validate` passes (services left empty
pending Graph indexing support).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant