trinitylabdao / eth-enq-bridge-v1.0 Goto Github PK

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.

Hello TrinityLab team,

please check and verify the ethereum contract that was created here. The cost of claiming the funds is very high and throws sometimes many errors (I think because the ethereum network is highly used now)

https://etherscan.io/address/0xdEF8D9e6FB07b7295657F494f9A01E68dC09922D

the other chains are working fine as of now

EDIT: I checked the bytecode on optimism spacebridge and bsc spacebridge (I assume it's the same for the other chains) and they all have the similar bytecode starting point: 60a060405

however, the ethereum bridge starts at 608060405 (see picture above). did you make sure you deployed the correct contract?