search

TrinityLabDAO / eth-enq-bridge-v1.0

Ethereum Enecuum Bridge V.1.0
0 stars 5 forks source link

Ethereum Bridge not deployed correctly #5

Open trjo1016 opened 1 year ago

trjo1016 commented 1 year ago

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

image

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?

trjo1016 commented 1 year ago

image

Team, you need to be active here, my funds are locked in the spacebridge on enecuum and to bring them back to ETH is very expensive, fix this please

justprepod commented 1 year ago

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?

You can match contracts source code, they are exactly same. Bytecode of deploy transactions differs because of initialization parameters. When bridge is deployed network_id is passed to constructor, and this id is unique for each network.

We're working on contract optimization so it spend less gass.