-
Notifications
You must be signed in to change notification settings - Fork 45
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
Fix runtime bytecode check when deploying a contract #408
Comments
@loredanacirstea Do you mean |
Maybe I can see this problem with |
@pirapira I suspect there might be a mistake in Otherwise, determine the external failure reason. In the initial complaint (#397), there was also another bug that recompiled the contracts when deploying, fixed by #407. |
Now I can reproduce the issue.
|
Now the differences are only at the end. These are probably contract metadata hashes. |
The metadata contains the absolute path where things are compiled, so it can be different on each machine
|
Previously, contracts.json contained some absolute paths with user names and so on. This caused verification failures after a user compiles a contract locally. The absolute paths were used in the contract metadata and were included in the metadata hash at the end of the deployed code. This was one cause of raiden-network#408
This issue will go away after #414 is merged and a new version of contracts are deployed. Because the user names like @loredanacirstea do you also want a temporary fix that works with the currently deployed contracts? |
I don't think we need the temporary fix for now. We should not get this issue in practice, after fixing the deploy script to not recompile. |
So #430 will close this issue. Since we change |
And #435 removes all iffy code. |
@loredanacirstea please close this when the relevant PRs are merged. |
From: #397
The runtime bytecode calculation is wrong here and might fail for other systems on which
solc
in stalled:raiden-contracts/raiden_contracts/deploy/__main__.py
Lines 519 to 525 in 343b9a9
Needs to be fixed for all subsequent occurrences.
@pirapira started working on this in #405.
The text was updated successfully, but these errors were encountered: