[bisq-network/bisq] Add hint to upgrade to Tor v3 address (#5558)

Christoph Atteneder notifications at github.com
Tue Jun 8 11:32:24 CEST 2021

### Description

Deprecation timeline copied from https://blog.torproject.org/v2-deprecation-timeline:

- July 15th, 2021
  0.4.6.x: Tor will no longer support v2 and support will be removed from the code base.
- October 15th, 2021
  We will release new Tor client stable versions for all supported series that will disable v2.

>From July 15th we won't be able to update the tor binary if we haven't migrated everyone from v2 to v3.

The current spread of v2 to v3 addresses is quite stable around 25% on v2 and 75% on v3.
![Bildschirmfoto 2021-06-08 um 11 17 49](https://user-images.githubusercontent.com/170962/121159134-37d8f580-c84b-11eb-81cc-7eeb3db9b3da.png)

To push this number down I'd suggest as a next step to include a popup whenever there is a safe moment to upgrade from v2 to v3 described in https://bisq.wiki/Changing_your_onion_address.

I'd check for it after:
- a successful trade
- a completed mediation/arbitration
- on startup

After Tor v2 support in the codebase is dropped in July and we have the Tor v3 support also in bitcoinj available, we should push in the release after everyone to upgrade to Tor v3 by only allowing user to continue to use the app that have an open trade or dispute. We also have to prevent users from re-opening trades or disputes if the current onion address doesn't match the onion address used in the trade or dispute.

After October 15th we have to present users that are still on Tor v2 an error message that they need to upgrade their Tor addresses as they won't be able to connect to the Tor network anyways. 

Related issues: https://github.com/bisq-network/bisq/issues/5179, https://github.com/bisq-network/bisq/issues/2873 and https://github.com/bitcoinj/bitcoinj/issues/2067

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210608/a96adb9c/attachment.htm>

More information about the bisq-github mailing list