-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
EIP 155 Activation #502
EIP 155 Activation #502
Conversation
Merge from upstream
enabled. This flag will not be present in Quorum version 2.0.2 or below, and if not present then it is safe to change the chain ID even after the EIP155 hard fork. On running 'geth init' to update the configuration, the flag is set and thus the regular restrictions about chaning
(we are not yet forked) then allow the chain ID to change.
been started following the changes
been started following the changes
… set-eip155-activation-flag # Conflicts: # eth/backend.go
return newCompatError("EIP155 fork block", c.EIP155Block, newcfg.EIP155Block) | ||
} | ||
if isQuorumEIP155Activated && c.ChainId!=nil && c.IsEIP155(head) && !configNumEqual(c.ChainId, newcfg.ChainId) { | ||
return newCompatError("EIP155 chain ID", c.EIP155Block, newcfg.EIP155Block) |
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.
We should return the ChainId, not the EIP155Block.
Apologies for resurrecting this, but EIP155 only mentions Chain ID and not Network ID
Shouldn't this rather be just if Chain ID is 1 (and not if Network ID is 1), as per EIP155 ? |
Hi @coeniebeyers we also wanted to discourage using or keeping the default network ID, 1. We updated quorum's examples scripts to reflect that too. |
As a part of EIP 155 activation, Quorum will not support chain id 1. The following changes are done as a part of this PR