Conversation
mlclay
approved these changes
Mar 6, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When trying to verify our contracts on our sidechain, we're having issues with the binaries from our Dockerized solc not matching what's generated by the version of solc used by the Blockscout explorer. Upon further investigation it looks like the git commits are inconsistent for 0.5.11. 0.5.12 does not have this inconsistency so I am migrating all of our contracts to 0.5.12 and redeploying our latest batch of contracts into meta.json (LOAD 1.2.0, NOTARY 1.0.0).
Related to: argotorg/solidity#7512