PSA: Ongoing DAO sync issue

Since almost 2 days, the DAO data cannot be successfully synced across the p2p network.

The origin of the issue has been a fork in the blockchain:

which happened at about the same time when most of the federated bitcoin nodes were testing an update to bitcoin 28, which was found out that returned RPC responses in an unexpected format, rendering the seednodes unable to sync, and this furthered their inconsistent status.

The btc nodes have been reverted to bitcoin 27, but the issue lasted long enough to cause network-wide inconsistencies in the distributed DAO data.

Since then, all seednodes but one are back online, and they all reached a consistent state, but clients on the network seem to be still sharing incorrect data, preventing users from having a valid DAO state.

Without a functioning DAO subsystem, it is not possible to start new trades, but ongoing trades will work as intended, even if disputes are opened.

2 Likes

Corollary

“…so what should I do?!?”

Avoid overloading the seednodes more than they currently are, do not hammer “resync dao” every 5 minutes as it is not going to help, but rather make the situation worse, imagine that everyone is doing the same, and that there are but a handful of seednodes.

The best course of action is clicking the “resync dao” button, close bisq, and then open it again after a few hours, rather than repeating the process incessantly.

2 Likes