-
Notifications
You must be signed in to change notification settings - Fork 447
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
Parity config update #123
Parity config update #123
Conversation
@@ -4,7 +4,9 @@ | |||
"Ethash": { | |||
"params": { | |||
"minimumDifficulty": "0x020000", | |||
"blockReward": "0x4563918244F40000", | |||
"blockReward": { | |||
"0": "0x4563918244F40000", |
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.
terminal comma breaks jq for me
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.
Right, thanks
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.
Fixed, pushed directly into master
chainconfig=`echo $chainconfig | jq "setpath([\"engine\", \"Ethash\", \"params\", \"eip649Transition\"]; \"0x$HIVE_FORK_BYZANTIUM\")"` | ||
# Set blockreward to 3M for byzantium | ||
chainconfig=`echo $chainconfig | jq "setpath([\"engine\", \"Ethash\", \"params\", \"blockReward\",\"0x$HIVE_FORK_BYZANTIUM\"]; \"0x29A2241AF62C0000\")"` | ||
# difficulty calculation -- aka bomb delay |
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.
For the bomb delay we also need to define additional variables :
chainconfig=`echo $chainconfig | jq "setpath([\"engine\", \"Ethash\", \"params\", \"difficultyBombDelays\",\"0x$HIVE_FORK_BYZANTIUM\"]; \"3000000\")"`
chainconfig=`echo $chainconfig | jq "setpath([\"engine\", \"Ethash\", \"params\", \"difficultyBombDelays\",\"0x$HIVE_FORK_CONSTANTINOPLE\"]; \"5000000\")"`
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.
I'm not sure that'll make a difference -- on hive there are only a couple of blocks, so whether the bomb is delayed to 3M or 5M shouldn't matter. Hive can't really be used to test the bomb delay, I think
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.
Also added an empty difficultyBombDelays struct to chain.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.
Hello, I made a small (big) mistake, our 'difficultyBombDelays' is additive so the right code should be
chainconfig=`echo $chainconfig | jq "setpath([\"engine\", \"Ethash\", \"params\", \"difficultyBombDelays\",\"0x$HIVE_FORK_BYZANTIUM\"]; \"3000000\")"`
chainconfig=`echo $chainconfig | jq "setpath([\"engine\", \"Ethash\", \"params\", "difficultyBombDelays\",\"0x$HIVE_FORK_CONSTANTINOPLE\"]; \"2000000\")"`
to have 5M total delay at constantinople.
Handle openethereum/parity-ethereum#9480: