wiz

Now that Bitcoin nodes support Tor V3 onions the startup time issue is merely a bug in Bisq we can fix by implementing support for Tor V3 nodes

Threads are terrible, this ruins matrix so bad

@burning2019 can you please make your monthly report? also, I checked the current DAO parameter for recipient BTC address `3EtUWqsGThPtjwUczw27YCo6EWvQdaPUyp` and it seems there are no transactions there?? https://blockstream.info/address/3EtUWqsGThPtjwUczw27YCo6EWvQdaPUyp

@gordonel Security for trusted roles in the Bisq DAO is actually pretty well thought out. Of course, the donation address keyholder is a very trusted role, right up there with...

Bisq doesn't hold any user funds. They're always stored in your own wallet, on your own keys, on your own hardware.

Well then what are you talking about? This address is only for trading fee revenue which is less than 50K BSQ worth of BTC each cycle

## Cycle 14 report The mempool node backends are off to a very good start, being monitored every 5 minutes in #ops-alerts channel on Keybase, and users seem very happy...

## Cycle 15 report * Running mempool.space * Now with Bisq Explorer support @ mempool.space/bisq * Fee estimation seems to be working quite well /cc https://github.com/bisq-network/compensation/issues/632

@HarryMacfinned go to DAO -> Proof of Burn and you will see the TX, click "verify" and enter the string as the preimage text to verify @burning2019 in the future...

> To actually verify, a signature is needed. The fact that the TX appears in the box means it has already been verified by your Bisq app. The burning man...