Open ffe9f8 opened 7 months ago
@ffe9f8 who did this task come from? The new json is missing network_id (eg ethereum-2
). Looks like the only difference is in capitalization (eg Ethereum
in old data ethereum
in new), but I want to double check.
Also, I need to know where icons referenced in the data like /images/chains/ethereum-sepolia.svg
is hosted?
@ffe9f8 I'm also seeing a bunch of missing block explorer URLs.
@ffe9f8 Avalanche is missing gateway and gas service addresses. We'll need to make sure this JSON is validated as correct before we rely on it, unless we want to do extra work in the web app to validate it and fail gracefully.
@ffe9f8 who did this task come from? The new json is missing network_id (eg
ethereum-2
). Looks like the only difference is in capitalization (egEthereum
in old dataethereum
in new), but I want to double check.Also, I need to know where icons referenced in the data like
/images/chains/ethereum-sepolia.svg
is hosted?
From @milapsheth. Context
Also potential mismatch with capitalization and keys https://github.com/axelarnetwork/axelar-docs/blob/main/src/data/evm_chains.json#L155C22-L155C30 mismatches in caps with https://axelar-mainnet.s3.us-east-2.amazonaws.com/configs/mainnet-config-1.x.json
Native currency of ethereum isn't weth
Can you clarify this too factory/osmo1mlng7pz4pnyxtpq0akfwall37czyk9lukaucsrn30ameplhhshtqdvfm5c/ulvn
?
Still blocked by https://github.com/axelarnetwork/chains/pull/515
Update the "EVM contract addresses" and "Assets" on the Mainnet and Testnet pages to pull from these two JSON files:
Mainnet: https://axelar-mainnet.s3.us-east-2.amazonaws.com/configs/mainnet-config-1.x.json Testnet: https://axelar-testnet.s3.us-east-2.amazonaws.com/configs/testnet-config-1.x.json