Sergey Khoroshavin

It looks like now Indy Node/Plenum cannot successfully catch up when node is too much behinds (for example new node joining 3-years old pool with 10000s transactions). While workaround is...

It looks like Plenum has timing-related bug in view change protocol. **Potential steps to reproduce** * create a test pool with 4 nodes * pause 2 nodes, none of which...