Skip to content

Bridging to an exisiting token results in a different contract address #6

@trjo1016

Description

@trjo1016

Hello team,

as I gained more security using the bridge, I tried my luck on using the Ethereum bridge. The previous issue still must be looked into about the Eth contract, so please check quickly.

However, I managed to bridge over this DYP token on Binance Smart Chain to Ethereum, but it resulted in a different contract address.

see these two links:
https://etherscan.io/token/0xdfef169a8a537bfcf22963ea0b5c87637ef5d8ed (spacebridge mint)
https://etherscan.io/token/0x961C8c0B1aaD0c0b10a51FeF6a867E3091BCef17 (correct token contract)

Is this supposed to be right? I thought the bridge would recognize an existing contract address, but this seems not to be the case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions