Shared Random and Half-Hour Consensuses
My test authority was asleep for an hour, and so it didn't have a recent consensus. It started voting at 10:30 for round commit 3/reveal 3, but the rest of the network wasn't voting for commit 3/reveal 3 until 11.
How does an authority recover from this situation if it has thrown away its state at 1030?
Do we fix this by implemeting #19045 (moved) (keep voting for shared random values)? Or does that make this worse?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information