Private Network ID Must Match "chainId"

Ethereum Tutorials - Herong's Tutorial Examples

∟MetaMask - Browser Based Ethereum Wallet

∟Private Network ID Must Match "chainId"

This section describes the requirement on private network - the network ID must match the 'chainId' given in the genesis block configuration.

I saw on comment on the Internet that the latest version of MetaMask added the EIP155 security feature, which requires:

"eip155Block" sets to 0 in the configuration provided by the genesis block.
Node "network" ID matches the "chainId" in the configuration provided the genesis block.

If the above settings are not correct, MetaMask will return "Error: invalid sender" when sending an outgoing transaction.

Here are my configuration settings and the network ID:

> admin.nodeInfo.protocols
{
  eth: {
    config: {
      chainId: 314,
      eip150Hash: 
"0x0000000000000000000000000000000000000000000000000000000000000000",
      eip155Block: 0,
      eip158Block: 0,
      homesteadBlock: 0
    },
    difficulty: 435790806,
    genesis: 
"0x1019b138ace55f9b9ee6e1aff60dcb8bde0fe0d7175339e6965206fcc0220d59",
    head: 
"0x5da0738a7e8ac0151b59a4426d89fbadafce629a912f46c46361e942052c2307",
    network: 1
  }
}

So "eip155Block" is set to 0. But "chainId" is 314 and "network" ID is 1, which does not match to each other.

To fix the issue is easy, since the network ID can be specified at the "geth" command line. Let's restart the "geth" node with "--networkid 314":

> exit
C:\> 

C:\> \herong\bin\geth --networkid 314 --datadir \herong\Ethereum\personal 
   --rpc console 2>> geth-personal.log

> admin.nodeInfo.protocols.eth.config.chainId
314

> admin.nodeInfo.protocols.eth.network
314