Temporary solution for DAO resync loop

suddenwhipvapor · June 5, 2024, 4:57pm

== ATTENTION ==

Since I cannot edit the above post anymore, I need to make a new one to amend that.
While the method explained above “works”, in my experience it will still lead to an unstable state where Bisq will still ask you to resync the DAO even if you are in consensus with seed nodes.

My current “working” solution, is to build Bisq from source (sorry, Windows users…) using this page as a guide:

github.com

bisq-network/bisq/blob/master/docs/build.md

## Building Bisq

1. **Clone Bisq**

   ```sh
   git clone https://github.com/bisq-network/bisq
   # if you intend to do testing on the latest release, you can clone the respective branch selectively, without downloading the whole repository
   # for the 1.9.3 release, you would do it like this:
   git clone --branch release/v1.9.3 https://github.com/bisq-network/bisq
   cd bisq
   ```

2. **Build Bisq**

   On macOS and Linux, execute:
   ```sh
   ./gradlew build
   ```

   On Windows:

This file has been truncated. show original

and making sure to select branch 1.9.16 in the example of the first bullet, so using:
git clone --branch release/v1.9.16 https://github.com/bisq-network/bisq

It will not be rock solid, but at least for a decent amount of time after a DAO resync, you will be synced and able to do normal operations.
I do use my own bitcoin node though, so also check out