Skip to content
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

Merged
merged 23 commits into from
Aug 23, 2018
Merged

EIP 155 Activation #502

merged 23 commits into from
Aug 23, 2018

Conversation

vsmk98
Copy link
Contributor

@vsmk98 vsmk98 commented Aug 23, 2018

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

  1. If the chain id is 1 or network id is 1, geth start will fail with appropriate error messages
  2. For migration scenarios where a network was running with a pre EIP155 version - the suggested approach is to bring down the network, update the chain id to a value > 1 in genesis.json file and run geth init with the new genesis file before bringing up the network
  3. Network id will be defaulted to 1337

vsmk98 and others added 23 commits August 15, 2018 05:59
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.
… 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)
Copy link
Contributor

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.

@jpmsam jpmsam merged commit 8a25cad into Consensys:master Aug 23, 2018
@vsmk98 vsmk98 deleted the EIP155-Activation branch August 24, 2018 02:24
@coeniebeyers
Copy link
Contributor

Apologies for resurrecting this, but EIP155 only mentions Chain ID and not Network ID

  1. If the chain id is 1 or network id is 1, geth start will fail with appropriate error messages

Shouldn't this rather be just if Chain ID is 1 (and not if Network ID is 1), as per EIP155 ?

@jpmsam
Copy link
Contributor

jpmsam commented Sep 4, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants