When using universal signing, the blockexplorer shows the mapped Ethereum address instead of the loom address.

[andreipope]

Environment

Blockscout Version/branch: http://extdev-blockexplorer.dappchains.com/

Steps to reproduce

Send a transaction and sign it using universal signing.

Expected behaviour

When you send and sign a transaction using universal transaction, the block explorer should:

• show the correct Loom address
• or prefix the Ethereum with the correct chain id (eth)

Actual behaviour

When using universal signing, I find it a bit confusing that the blockexplorer shows the mapped Ethereum address instead of the loom address. And even more, it’s prefixed with loom.

The following:

await this.loomCoinContract.methods
      .approve(gatewayAddress, amountInWei)
      .send({ from: ethAddress })

generated this transaction hash: http://extdev-blockexplorer.dappchains.com/tx/0x3d4c7ce3a32503bc685cafed95069699cfa43bdcbd08ba7823909986682a4550/internal_transactions

The page shows loom6AB5eDEaBC9bf2CD4655369131976fE46ea36BC2 → loom9C8F1dADfFC584afB6F749C25f7c14f65b598493.

But the thing is that 0x6ab5edeabc9bf2cd4655369131976fe46ea36bc2 is an Ethereum address.

The mapping looks like this:

mapping.ethereum: eth:0x6ab5edeabc9bf2cd4655369131976fe46ea36bc2
mapping.loom: extdev-plasma-us1:0xdfe51931ab654accc245dffc60df5151dbbb3b80

Also, if you search for this Ethereum address in the block explorer, a few transactions show up http://extdev-blockexplorer.dappchains.com/address/0x6ab5edeabc9bf2cd4655369131976fe46ea36bc2/transactions. And the address is always prefixed with loom.

This has been reported in TG: https://t.me/LoomSDK/16527