search

permaledger / go-perma

clean-slate Ethereum clone
https://github.com/permaledger/perma
GNU Lesser General Public License v3.0
1 stars 0 forks source link

Uncles causing merkle errors #6

Open Riverhead opened 8 years ago

Riverhead commented 8 years ago

From mining machine:

I0707 13:05:21.365985 miner/worker.go:555] commit new work on block 559 with 0 txs & 0 uncles. Took 306.604µs
I0707 13:05:21.466859 miner/worker.go:555] commit new work on block 559 with 0 txs & 0 uncles. Took 352.187µs
I0707 13:05:22.725638 miner/worker.go:337] �  Mined block (#559 / ac289b6a). Wait 5 blocks for confirmation
I0707 13:05:22.726050 miner/worker.go:555] commit new work on block 560 with 0 txs & 0 uncles. Took 349.44µs
I0707 13:05:22.954312 miner/worker.go:337] �  Mined stale block (#559 / cde3b6eb).

From node trying to sync:

I0707 13:13:40.843896 eth/downloader/downloader.go:299] Synchronisation failed: invalid merkle root: header=650d5eea78d839166876bf5a57382269d7e23208ae77cda1c1a4ddad4c2cac9d computed=54206d0c433fc31c44fd1e669ab5f05a540ee683b830422c53030e50eba34a8b

Notes: I can bypass the issue by copying the blockchain database from the mining machine however the next uncle that gets produced will cause sync to fail again.

MrComputerCodes commented 8 years ago

Hi @Riverhead,

Could you try out this branch on a fresh network?

https://github.com/permaledger/go-perma/tree/max-0-uncles