Updated: 2023-10-03
Relayer clients failing on Archway resulted in some unusable tokens that are forever floating in the Archway network.
This creates confusion, that this GIST aims to clear up.
At least...
USDC.axl, JKL.axl, xAXL, and AXL have two conflicting addresses...
For example, reported to us...
Asset archway>xaxl:{"cw20":"archway135pmrdfsu8le852q5xztwdlxpmzqrp2t589lrqtw2athnr70wgcqg26ecc"} already registered with different info: {"cw20":"archway12a6yk6ydd2kmyr69svgurxvsfwasqvmumqhqswmz5cqpu6a72w2qp2frgt"}
and
Asset axelar>axl:{"native":"ibc/E21808AEBCB7E02F594897100186C126E3BC9A36B0974196AF116750A4573F06"} already registered with different info: {"native":"ibc/C0E66D1C81D8AAF0E6896E05190FDFBC222367148F86AC3EA679C28327A763CD"}
Therefore, the following list should clear up the conflab.
Archway network token contract addresses
[{
"denom": "aarch",
"symbol": "ARCH"
},
{
"address": "archway1cutfh7m87cyq5qgqqw49f289qha7vhsg6wtr6rl5fvm28ulnl9ssg0vk0n",
"symbol": "xARCH"
},
{
"denom": "ibc/27394FB092D2ECCD56123C74F36E4C1F926001CEADA9CA97EA622B25F41E5EB2",
"symbol": "ATOM"
},
{
"address": "archway1m273xq2fjmn993jm4kft5c49w2c70yfv5zypt3d92cqp4n5faefqqkuf0l",
"symbol": "xATOM"
},
{
"denom": "ibc/0471F1C4E7AFD3F07702BEF6DC365268D64570F7C1FDC98EA6098DD6DE59817B",
"symbol": "OSMO"
},
{
"denom": "ibc/E21808AEBCB7E02F594897100186C126E3BC9A36B0974196AF116750A4573F06",
"symbol": "AXL"
},
{
"address": "archway135pmrdfsu8le852q5xztwdlxpmzqrp2t589lrqtw2athnr70wgcqg26ecc",
"symbol": "xAXL"
},
{
"denom": "ibc/B9E4FD154C92D3A23BEA029906C4C5FF2FE74CB7E3A058290B77197A263CF88B",
"symbol": "USDC.axl"
},
{
"denom": "ibc/13C5990F84FA5D472E1F8BB1BAAEA8774DA5F24128EC02B119107AD21FB52A61",
"symbol": "ETH.axl"
},
{
"denom": "ibc/926432AE1C5FA4F857B36D970BE7774C7472079506820B857B75C5DE041DD7A3",
"symbol": "JKL"
},
{
"address": "archway1yjdgfut7jkq5xwzyp6p5hs7hdkmszn34zkhun6mglu3falq3yh8sdkaj7j",
"symbol": "xJKL"
},
{
"denom": "ibc/43897B9739BD63E3A08A88191999C632E052724AB96BD4C74AE31375C991F48D",
"symbol": "USDC.nobl"
}]