[QA] [Mainnet] WGLMR contract address on wormhole-connect is different from contract address in Metamask

[tsadovska]

Describe the current behavior in detail

Checked on https://wormhole-connect-mainnet.netlify.app/ [Mainnet] and https://preview.portalbridge.com/ [Mainnet] with macOS and Google Chrome.

Steps:

1. Select BSC network as source chain > Connect Metamask wallet > Open Assets list > Check WGLMR contract address
2. Open Metamask extension > Switch network to BSC Mainnet > Check WGLMR token details

Asset in Explorer: https://bscscan.com/token/0x1C063db3c621BF901FC6C1D03328b08b2F9bbfba

What is the expected/desired behavior

Contract address is the same on wormhole-connect and in Metamask.

Notes

• Click here to view similar issues.
• Issue is also reproducible on Fantom network.

[AigaD]

Tested from: https://preview.portalbridge.com/bceadc8c64/# WGLMR contract address also differs from contract address shown in Suiscan Attachment:

[AigaD]

Reproduced from: https://preview.portalbridge.com/3064c36d95/# Contract address gor WGLMR in Portal and in Moonscan is shown as - 0xAcc15dC74880C9944775448304B263D191c6077F , but in Metamask - 0x43E43580A34c8FdD4694e1F9B5F9b1121a7044a5 Attachment:

[agodlevska]

Tested OK on https://preview.portalbridge.com/859350d189/ [Mainnet].

Contract addresses on Portal Bridge and in Metamask are the same for following tokens:

• WGLMR (Moonbeam) on BSC, 0x1C063db3c621BF901FC6C1D03328b08b2F9bbfba
• WGLMR (Moonbeam) on Sui, 0x66f87084e49c38f76502d17f87d17f943f183bb94117561eb573e075fdc5ff75::coin::COIN

Blast network is not displayed in Networks list on Portal Bridge. Ticket can be closed after changes are merged on https://portalbridge.com/ [Mainnet].

[agodlevska]

Changes are merged on https://portalbridge.com/, closing the ticket.