-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Fixed binary publishing for arm64
#960
Conversation
arm64
@@ -1,10 +1,5 @@ | |||
{ | |||
"chain_name": "Testnet", | |||
"block_production": { |
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.
Why is deployment chainspec getting changed in a publishing fix?
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.
This section has been replaced by a "consensus" portion. We no longer use the chainspec for poa trigger configuration since verifiers can't check things like whether or not the poa produced the block instantly. Chainspec should only contain fields necessary for verification of blocks, not general node-specific parameters that can't be checked by anyone else.
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.
nice work on testing and fixing this!
No description provided.