fix: hyperchain nodes require child_block_production_time set#7
Closed
adas0x wants to merge 1 commit intoaeternity:masterfrom
Closed
fix: hyperchain nodes require child_block_production_time set#7adas0x wants to merge 1 commit intoaeternity:masterfrom
adas0x wants to merge 1 commit intoaeternity:masterfrom
Conversation
when starting with a fresh config, it errors with:
{{missing_mandatory_chain_consensus_config_key,[<<"child_block_production_time">>]},
after filling this value in manually it continues on. 500 is the default
value from the schema, so figure it's safe to use as the default here.
Member
|
There was a updated version branch which is now merged: #8 |
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 starting with a fresh config, it errors with:
{{missing_mandatory_chain_consensus_config_key,[<<"child_block_production_time">>]},
after filling this value in manually it continues on. 500 is the default value from the schema, so figure it's safe to use as the default here.