Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
trjo1016 opened this issue Aug 15, 2023 · 0 comments
Open

Comments

@trjo1016
Copy link

trjo1016 commented Aug 15, 2023

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.

@trjo1016 trjo1016 changed the title Bridging to an exisiting token redsults in a different contract address Bridging to an exisiting token results in a different contract address Aug 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant