Evgeny Danilenko

Looks good to me!

0txs blocks are reproducible as well as stuck in txPool transactions. For that reason the rest is marked as skipped for further txPool fixes.

@manav2401 I believe now we have everything to merge the branch into develop. Could you resolve conflicts, fix TODOes if needed and merge it?

> Do you foresee any major conflicts when we merge upstream changes in future? We can just try ) we didn't merge Geth upstream for a while, so we can...

> Hmm... In both cases we'll increase our tech debt, because we'd need to support at least 1 long living branch. I'd suggest to finish mining analysis, merge it to...

@PaulGrandperrin @ilmoi Just had the same issue with MacOs. I believe https://github.com/google/honggfuzz/issues/371 was closed successfully some time ago. However, mentioned lines in Makefile are still there...

@JuliusBrain Is it alive?

can be related to https://github.com/kowala-tech/kcoin/issues/806

From `09-26|13:30:22.136` to `09-26|13:33:36.443` there're quite a lot duplicate votes for blocks like ``` {"log":"\u0009Block Number:\u0009\u00095145\n","stream":"stderr","time":"2018-09-26T13:30:22.136100079Z"} {"log":"\u0009Block Hash:\u0009\u0009\u00090000000000000000000000000000000000000000000000000000000000000000\n","stream":"stderr","time":"2018-09-26T13:30:22.13610306Z"} ``` So it's not for a block, it's voting against the block....

The second problem: if validator starts away after others, it states will be different from the entire network. It seems that voting is a part of a replicated state machine...