phytohydra

I got the AUR bisq package to build. It needed sha256 sums for two files (protoc-3.19.1-linux-aarch_64.exe and protoc-gen-grpc-java-1.42.1-linux-aarch_64.exe) added to the verification-metadata.xml first. bisq-desktop doesn't launch ([already reported](https://github.com/bisq-network/bisq/issues/7037)); work around...

Building against it wasn't necessary; just using the archlinux-java command to set the default java environment to liberica-jdk-11-full. That fixed the JavaFX error for both Bisq and Haveno, and all...

It displays the 'Open Tor Settings' button after a while, and eventually times out and opens the Tor settings dialog itself. The last messages in the console are, ``` Feb-25...

I meant, is there a way I can add XMR to the bounty for supporting ARM64? It looks like this is all manual at this point, so I'd send it...

I got a bit further today. As per the [gist](https://gist.github.com/tmakerman/ee53a94c3cfc8362192ad9df20709547?permalink_comment_id=4723520), on RPi they're starting tor themselves and then having Bisq connect to the running instance. I don't think it needs...

I think no seed nodes is because mainnet isn't supported yet. I tried running stagenet, ``` $ ./haveno-desktop --baseCurrencyNetwork=XMR_STAGENET --useLocalhostForP2P=false --useDevPrivilegeKeys=false --nodePort=9999 --appName=haveno-XMR_STAGENET_user1 --apiPassword=apitest --apiPort=3201 --torControlPort 9051 --torControlCookieFile=/var/lib/tor/control.authcookie --torControlUseSafeCookieAuth ```...

Updated from [liberica-jdk-11](https://aur.archlinux.org/packages/liberica-jdk-11-full-bin) to [liberica-jdk-21](https://aur.archlinux.org/packages/liberica-jdk-21-full-bin) and confirmed that it works, starting tor separately as above. The liberica-jdk-21 AUR PKGBUILD needed some tweaks. The first three files in the `source` array...

Most linux distributions have a tor daemon binary package already in the repos, including on arm64. Maintaining just the tor daemon is much easier than porting and packaging the entire...

I suggest that if there is a backlog at the current fee level, the wallet should automatically check what the backlog would be at each higher fee level, until it...

Would it cause the blocks to grow faster?