-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Updating Canary genesis block with TransmissionID checksum - v0.4.0 #2522
Conversation
…2541) Signed-off-by: Fabiano <[email protected]>
Signed-off-by: Fabiano <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, though I'm not sure I like having the JSON objects because all of the information already exists in block.genesis
.
It is another surface that will need to be updated if block.genesis
needs to be resampled, and this feels easy to forget down the line.
In the context of this PR, it's obvious that these files were used to create the genesis block, however it isn't clear from an outside perspective. At the least, I think a name change is warranted; for example, validators.json
-> genesis_validators.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, and agree with @raychu86 point.
Signed-off-by: Fabiano <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM given CI has passed.
Motivation
Updating to Canary genesis block v0.4.0
sha256 == e6419d92fa653a9560310a168ac2f3c65cb3edc9ffb966e1fdb1d208bc0929d2
Related PRs
#2521
ProvableHQ/snarkOS#3367