-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ethcore: don't validate difficulty when ignoring seal check #9470
Conversation
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 overall. @andresilva I think we should add a short docs in both Engine::verify_block_basic
and Engine::verify_block_unordered
, stating that those two functions won't be called if check_seal
is false. Just in case those caught us in surprise when writing new engine impls.
@sorpaas Good idea, added a comment about it. |
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. Should we wait for confirmation in #9461 before merging?
This change misses 1 place, where it still checks "SealArity" when --no-seal-check is passed and nullEngine is specfied. see logs here
|
If this is fixed, I think parity will be able to use nullEngine and --no-seal-check to connect to GETH clique chains. |
Should fix #9461. We weren't validating the PoW itself but were immediately rejecting the block based on its difficulty.