-
Notifications
You must be signed in to change notification settings - Fork 1.7k
InvalidStateRoot Error on private chain #2794
Comments
You probably need built-in accounts in the spec for a contract to run properly. Try adding these: |
i dont run any contract, i dont need them. |
@iFA88 That's fine, but geth will include them as accounts in their state trie and your state trie will mismatch (notice that the error has "found" root of If you want geth and parity to work together then you'll have to include them. |
i use now this parity genesis.json :
but i got different hash like geth :/ Can anyone help me which parameter should i use to make the same genesis block as on geth? |
Its working perfectly with this parity genesis.json:
Thanks for support! |
@iFA88 Hi, i've met the same problem with 'InvalidStateRoot' Error in geth & parity cross-client syncing, and i tried both your geth and parity genesis block file, but the error seems still there. can you give me some suggestions on solving this problem? |
@achillesss Hi! Sadly I don't remember what was the exact problem. But I know you need the builtin accounts with 1 wei. If you don't has it, then the contracts with these calls would be thrown. |
Trying to setup a own chain with geth and parity.
I have successfully created for every client a genesis block below can you find the 0 block details. The hash are matching!
This 2 client is running on my debian VPS:
The connection is in every type enstablished and worked. (desktop geth -> vps geth, dekstop parity -> vps parity, desktop geth -> vps parity, dekstop parity -> vps geth)
I have mined few block with VPS geth native miner.
When i connect from my desktop PC with Parity TO VPS geth node, then I get this error:
When i connect from my desktop PC with Geth TO VPS geth or parity then works great.
Here is the #1 block:
geth genesis.json:
Parity genesis.json:
If anyone need more info ask them.
The text was updated successfully, but these errors were encountered: