parity-ethereum
parity-ethereum copied to clipboard
Private Chain Spec Sanity Check Please
- Parity Ethereum version: 2.6.8
- Operating system: Linux
- Installation: binary
- Fully synchronized: no (that's the problem)
- Network: private blockchain
- Restarted: yes
On a private PoW blockchain running Parity 2.3.9, we are having syncing problems bringing newer nodes running Parity 2.6.8 online. Can some Big Brains please look at these parameters and tell me if something is obviously incompatible?
Actual problem:
-
Create a new node.
-
Download Parity, run with this private chain spec
-
Node quickly syncs to latest block, then fails to sync after that. It does not import new blocks, but shows the same block again and again. (showing
26/25 peers
) -
All other nodes (running 2.3.9) do continue to Import blocks.
"engine": {
"Ethash": {
"params": {
"minimumDifficulty": "0x020000",
"difficultyBoundDivisor": "0x400",
"metropolisDifficultyIncrementDivisor": "0xA",
"blockReward": "0x4563918244F40000",
"homesteadTransition": "0",
"difficultyHardforkTransition": "0xC55F7BC23038E38",
"difficultyHardforkBoundDivisor": "0x800",
"bombDefuseTransition": "0",
"eip100bTransition": 0
}
}
},
"params": {
"gasLimitBoundDivisor": "0x0400",
"registrar" : "<witheld>",
"accountStartNonce": "<witheld>",
"maximumExtraDataSize": "0x20",
"minGasLimit": "0x1388",
"networkID": "<witheld>",
"subprotocolName": "<witheld>",
"eip140Transition": 0,
"eip150Transition": 0,
"eip155Transition": 0,
"eip160Transition": 0,
"maxCodeSizeTransition": 0,
"eip161abcTransition": 0,
"eip161dTransition": 0,
"eip211Transition": 0,
"eip214Transition": 0,
"eip658Transition": "1104000",
"eip1283Transition": "1104000",
"eip145Transition": "1115000",
"eip1052Transition": "1115000",
"eip1014Transition": "1115000"
},
Can you test with the latest master?
@vorot93
Can you test with the latest master?
Do you mean the first version of openethereum? Is that a drop-in replacement for parity? I'm using Ubuntu 18.04. Will the U16.04 run there? Is there a generic version? Appimage or tar.gz?
Also: do you have a reason to think it would work? Some actual change in the code that you think is connected to the chain spec above? Or just a hope?
If you mean Parity 2.7.2, that still has the problem.