# Bisq DAO constantly in conflict **URL:** \ **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:** 17\ **Page:** 1
**Author:** ![daocat](https://bisq.community/letter_avatar/daocat/32/5_5575768a8748004e209b776fc1b2916d.png) [@daocat](https://bisq.community/u/daocat)\ **Post date:** [January 9, 2022, 2:27am UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/1 "2022-01-09T02:27:42Z")
Hi, my Bisq nearly always shows “Your local data is not in consensus with at least one seed node. Please resync the DAO state.” It often pops up saying I need to resync the DAO state and if I hit the button it closes/restarts Bisq, then the problem comes back pretty soon. I never hit “ignore” checkbox. Today, I reset my entire data directory and started fresh and the DAO is out of consensus already. When clicking on the details of the DAO state, it looks like every DAO state “signed by self” has a red X next to it. Is there something wrong with my computer? I’m running Bisq from the .deb file on Ubuntu 21.10. Thanks ---
**Author:** ![w000000t](https://bisq.community/user_avatar/bisq.community/w000000t/32/3124_2.png) [@w000000t](https://bisq.community/u/w000000t)\ **Post date:** [January 9, 2022, 4:47pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/2 "2022-01-09T16:47:01Z")
If it is any consolation, this issue is happening quite often lately; I also remember another occasion when the same occurred for a while, before disappearing. I experienced it once a few days ago and that has been all, and I also experienced it a few times in the previous “wave”. It might solve by itself in a while. ---
**Author:** ![BowTiedBustard](https://bisq.community/letter_avatar/bowtiedbustard/32/5_5575768a8748004e209b776fc1b2916d.png) [@BowTiedBustard](https://bisq.community/u/BowTiedBustard)\ **Post date:** [January 12, 2022, 3:10pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/3 "2022-01-12T15:10:48Z")
Have had same issue several times over past week or two. Restarted many times but couldn’t resolve it so have had to disable DAO for the moment. ---
**Author:** ![w000000t](https://bisq.community/user_avatar/bisq.community/w000000t/32/3124_2.png) [@w000000t](https://bisq.community/u/w000000t)\ **Post date:** [January 12, 2022, 3:20pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/4 "2022-01-12T15:20:34Z")
I’ve encountered this problem as well the past few days, in my case though it did work for a while after the restart, and in the end it didn’t repeat anymore. Seems like something happening in waves on the peer network. ---
**Author:** ![Pazza](https://bisq.community/user_avatar/bisq.community/pazza/32/2703_2.png) [@Pazza](https://bisq.community/u/Pazza)\ **Post date:** [January 16, 2022, 11:36pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/5 "2022-01-16T23:36:09Z")
Same here, I have done multiple DAO refreshes this weekend. I think it only matters really if you are making / taking a trade using BSQ or accessing / submitting information to the DAO. ---
**Author:** ![w000000t](https://bisq.community/user_avatar/bisq.community/w000000t/32/3124_2.png) [@w000000t](https://bisq.community/u/w000000t)\ **Post date:** [January 17, 2022, 11:33am UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/6 "2022-01-17T11:33:28Z")
Word is an isolate seednode was in conflict with the other seednodes, and the former has been excluded from the network, so the issue _should_ be solved for now ---
**Author:** ![w000000t](https://bisq.community/user_avatar/bisq.community/w000000t/32/3124_2.png) [@w000000t](https://bisq.community/u/w000000t)\ **Post date:** [January 22, 2022, 6:57pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/7 "2022-01-22T18:57:36Z")
I was wrong… still, whenever an out of sync error happens, check first if it’s with other peers (you can ignore this) or with a seed node; in the latter case, restarting bisq is necessary, and will solve the problem at least for a while, after one of a few restarts. Currently being worked on, though. ---
**Author:** ![bisqcogiendo](https://bisq.community/letter_avatar/bisqcogiendo/32/5_5575768a8748004e209b776fc1b2916d.png) [@bisqcogiendo](https://bisq.community/u/bisqcogiendo)\ **Post date:** [January 23, 2022, 11:36pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/8 "2022-01-23T23:36:11Z")
so do i i hope it is resolved soon ---
**Author:** ![w000000t](https://bisq.community/user_avatar/bisq.community/w000000t/32/3124_2.png) [@w000000t](https://bisq.community/u/w000000t)\ **Post date:** [January 24, 2022, 11:46am UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/9 "2022-01-24T11:46:57Z")
Last 1.8.2 version solves this problem for now ---
**Author:** ![steuerboykott](https://bisq.community/user_avatar/bisq.community/steuerboykott/32/3505_2.png) [@steuerboykott](https://bisq.community/u/steuerboykott)\ **Post date:** [September 23, 2025, 8:53pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/10 "2025-09-23T20:53:41Z")
I had this same problem for many weeks and months in 2024 and eraly 2025 with bisq-1 running Ubuntu Linux 24.04.2 LTS. Someone in the bisq Telegram-chat asked me to check if I had the same errors (DAO in conflict, not in consensus, often in conflict with self-signed states) with Windows. So I set up a virtual machine with Windows 11, installed bisq-1 and migrated the data directory and never had any issues. Now I use bisq only in that virtual machine. In the meantime, the bisq Telegram channel blocked me for asking too many good questions - I guess, as I never got any explanation. I want to run bisq-1 with Ubuntu or Debian. So is there more lately experience? Always have a backup of your data directory is the best advice I guess, but the most common advice from people with skills is, switch to Linux. Now what? I should run bisq-1 in a VBox with Windows? Give me a break 😉 And your cancel culture on Telegram is b.s. ---
**Author:** ![MnM](https://bisq.community/user_avatar/bisq.community/mnm/32/257_2.png) [@MnM](https://bisq.community/u/MnM)\ **Post date:** [September 25, 2025, 8:59am UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/11 "2025-09-25T08:59:24Z")
The mods are basically the same in Telegram and this forum, let me know your handle (via direct message if you prefer) and I will unban you. I don’t recall any conversation where someone recommended to use Windows. It’s usually the opposite, Bisq works better in Linux. A 4gb machine it’s on the lower end of what Bisq can handle. ---
**Author:** ![suddenwhipvapor](https://bisq.community/user_avatar/bisq.community/suddenwhipvapor/32/3291_2.png) [@suddenwhipvapor](https://bisq.community/u/suddenwhipvapor)\ **Post date:** [September 29, 2025, 7:54pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/12 "2025-09-29T19:54:22Z")
> [@steuerboykott](#): > > In the meantime, the bisq Telegram channel blocked me for asking too many good questions - I guess, as I never got any explanation. > [@steuerboykott](#): > > And your cancel culture on Telegram is b.s. I think the above sounds offensive for the support staff, if you were banned there was for sure a good reason for that, which you do not agree with I reckon, yet that’s not an excuse to insinuate that you were asking the “good questions” and the evil group administration decided to “cancel” you. If this didn’t happen closely enough in the past there are no remaining logs to check, but yes, I would appreciate if you shared your telegram account name so we can try and see what really happened Regarding your question, debian or ubuntu doesn’t make much difference, but I would recomment even 8GB of ram if you plan to do anything else except bisq on the same machine ---
**Author:** ![steuerboykott](https://bisq.community/user_avatar/bisq.community/steuerboykott/32/3505_2.png) [@steuerboykott](https://bisq.community/u/steuerboykott)\ **Post date:** [September 29, 2025, 9:16pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/13 "2025-09-29T21:16:33Z")
“if you were banned there was for sure a good reason for that, which you do not agree with I reckon…” Thanks for your reply. However, if you assume there was a good reason (while I was telling before that there was no reason at all), you should be able to give the reason here to everyone in full detail with quotes. As long as you cannot do so, I am happy to refuse your assumption. Let’s not continue here, as this topic is about the DAO being in conflict. ---
**Author:** ![steuerboykott](https://bisq.community/user_avatar/bisq.community/steuerboykott/32/3505_2.png) [@steuerboykott](https://bisq.community/u/steuerboykott)\ **Post date:** [September 29, 2025, 9:20pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/14 "2025-09-29T21:20:05Z")
Hi and thank for the offer. I will PM you now. However, I am okay with the ban and think this forum is a better structured place. It was exactly like I said: I was recommended Windows and in fact I did not have any more problems with DAO in conflict. My machine has 32 GB of RAM and I have assigned 16 GB to the virtual machine that runs Windows 11. ---
**Author:** ![lezoblas](https://bisq.community/letter_avatar/lezoblas/32/5_5575768a8748004e209b776fc1b2916d.png) [@lezoblas](https://bisq.community/u/lezoblas)\ **Post date:** [October 23, 2025, 12:53pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/15 "2025-10-23T12:53:20Z")
Same problem here, even after re-starting Bisq 1.9.21 several times on a Linux Mint machine. “Your local data is not in consensus with at least one seed node. Please resync the DAO state.” Help, please. ![image](https://bisq.community/uploads/default/original/2X/d/df216e31e92c8b831af8601bffa2e8f60337bf80.png) ---
**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:24pm UTC](https://bisq.community/t/bisq-dao-constantly-in-conflict/11318/16 "2025-10-23T22:24:13Z")
network-wide issue, only solution is waiting that the p2p network reaches a consensus, seed nodes are synced as of now ---
**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")
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…