# Bisq DAO constantly in conflict

**URL:** <https://bisq.community/t/bisq-dao-constantly-in-conflict/11318>\
**Category:** Bisq DAO\
**Created:** [January 9, 2022, 2:27am UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318 "2022-01-09T02:27:42Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![MnM](https://bisq.community/user_avatar/bisq.community/mnm/32/257_2.png) [@MnM](https://bisq.community/u/MnM)\
**Post date:** [October 24, 2025, 7:30am UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/17 "2025-10-24T07:30:42Z")

</div>

Do a DAO resync every few hours.

> [@PSA: Ongoing DAO sync issue](https://bisq.community/t/psa-ongoing-dao-sync-issue/13399):
>
> 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 lon…

---

_[View the full topic](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318)._
