Closed MonsieurNicolas closed 9 years ago
added initial legacy_consensus.txt (before any other changes) to make it simpler to follow the flow of changes
gFORCE_CLOSE is not sticky: it gets cleared in the consensus stage (was clearing too early before, which explains why it didn't work in the first place from what I remember).
merging manually into master (robot didn't pick up the r+ for some reason)
changes to move to one validator
The consensus changes were necessary as peers even when not participating in consensus may decide to close their open ledger which causes them to be out of sync with the validator. This change forces all peers (a subset, really) to tag along as part of consensus.
This also slows down the network enough for large/remote nodes to sync. We will adjust timings as we gather more data from production.