[bisq-network/bisq] Handle dao state conflicts better (#2674)
notifications at github.com
Mon Apr 8 21:43:04 UTC 2019
I am not sure if we shoud merge that into 1.0.0 or keep it for later. It is not high risk but also not trivial to test. I tested quite a bit though... It should not introduce much risk as well.
Lets discuss if we should add it or not. Would at least reduce confusion if some peers are out of sync as we have seen in dao-regtest last days... Also the missing file deletion of proposals, blind votes and ballots would not have lead to a recovery in current release if the cause for the issue is that one of those db files is out of sync.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bisq-github