# PSA: Ongoing DAO sync issue **URL:** \ **Category:** Support\ **Created:** [October 23, 2025, 10:38pm UTC](https://bisq.community/t/psa-ongoing-dao-sync-issue/13399 "2025-10-23T22:38:19Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![suddenwhipvapor](https://bisq.community/user_avatar/bisq.community/suddenwhipvapor/32/3291_2.png) [@suddenwhipvapor](https://bisq.community/u/suddenwhipvapor)\ **Post date:** [October 23, 2025, 10:38pm UTC](https://bisq.community/t/psa-ongoing-dao-sync-issue/13399/1 "2025-10-23T22:38:19Z")
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: > **[Fork Monitor](https://forkmonitor.info/stale/920138)** 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. ---
**Author:** ![suddenwhipvapor](https://bisq.community/user_avatar/bisq.community/suddenwhipvapor/32/3291_2.png) [@suddenwhipvapor](https://bisq.community/u/suddenwhipvapor)\ **Post date:** [October 24, 2025, 7:54am UTC](https://bisq.community/t/psa-ongoing-dao-sync-issue/13399/2 "2025-10-24T07:54:15Z")
### 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. ---
**Author:** ![darawheelan](https://bisq.community/user_avatar/bisq.community/darawheelan/32/3431_2.png) [@darawheelan](https://bisq.community/u/darawheelan)\ **Post date:** [November 25, 2025, 6:10am UTC](https://bisq.community/t/psa-ongoing-dao-sync-issue/13399/3 "2025-11-25T06:10:25Z")
Users are reporting the DAO being unable to sync again. The timing of the issue corresponds to a recent fork. > **[Fork Monitor](https://forkmonitor.info/stale/925051)** If you have a trade in progress you might have an error message eg: ```auto resync the DAO state ``` ```auto There is an issue with a missing or invalid transaction ``` ```auto Please do NOT send payment. ``` ```auto Open a support ticket to get assistance from a Mediator. ``` ```auto Error message: Fee receiver not a recognized address ``` If you have a trade in progress with an error message it will likely be fine to complete the trade, but you can open mediation to be sure. If you have no trades in progress then the best thing to do it to wait and try connecting in a few hours. Last time the issue took 48-72 hours to resolve. But hopefully this time it will be sooner. ---
**Author:** ![FairMoneyEmerging](https://bisq.community/user_avatar/bisq.community/fairmoneyemerging/32/3534_2.png) [@FairMoneyEmerging](https://bisq.community/u/FairMoneyEmerging)\ **Post date:** [December 1, 2025, 6:09am UTC](https://bisq.community/t/psa-ongoing-dao-sync-issue/13399/4 "2025-12-01T06:09:56Z")
is this happening again right now? I having the issue reported in [this thread](https://bisq.community/t/a-verack-message-must-follow-version/11400/3) ---
**Author:** ![MnM](https://bisq.community/user_avatar/bisq.community/mnm/32/257_2.png) [@MnM](https://bisq.community/u/MnM)\ **Post date:** [December 1, 2025, 6:55am UTC](https://bisq.community/t/psa-ongoing-dao-sync-issue/13399/5 "2025-12-01T06:55:11Z")
It’s ok now.