# CRITICAL Notice: Finish Trades Before Upgrading to v1.2

**URL:** <https://bisq.community/t/critical-notice-finish-trades-before-upgrading-to-v1-2/8576>\
**Category:** Support\
**Created:** [October 21, 2019, 9:24pm UTC](https://bisq.community/t/critical-notice-finish-trades-before-upgrading-to-v1-2/8576 "2019-10-21T21:24:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![m52go](https://bisq.community/letter_avatar/m52go/32/5_5575768a8748004e209b776fc1b2916d.png) [@m52go](https://bisq.community/u/m52go)\
**Post date:** [October 21, 2019, 9:24pm UTC](https://bisq.community/t/critical-notice-finish-trades-before-upgrading-to-v1-2/8576/1 "2019-10-21T21:24:58Z")

</div>

**Before** upgrading to v1.2 (likely releasing this week), you **must** :

- complete all trades
- complete all disputes
- disable open offers (not delete, just disable)

This is because v1.2 integrates Bisq’s new trade protocol, which moves from 2-of-3 multisigs to 2-of-2 multisigs.

[See Twitter thread here](https://twitter.com/bisq_network/status/1185120881695178757).

Please spread the word to any Bisq users you know.

There will be a clear warning in the upgrade prompt in the software, but still – please beware.

---

<div class="post-metadata">

**Author:** ![Progresso](https://bisq.community/user_avatar/bisq.community/progresso/32/2395_2.png) [@Progresso](https://bisq.community/u/Progresso)\
**Post date:** [October 22, 2019, 2:37pm UTC](https://bisq.community/t/critical-notice-finish-trades-before-upgrading-to-v1-2/8576/2 "2019-10-22T14:37:50Z")

</div>

So, the warning needs to be extremely clear. This potentially means you cannot trade around 12 days.

Just an example. Before the upgrade you have a contract which has a maximum timeslot of four days. Buyer is not responding during these four days. Then you go to the mediator. Another four days and finally you call the arbitrator another four days.

OK for now with the snmall volumes handled by Bisq, but if the volume goes to thousands of contracts per day this is an absolute no go.

Something to think about.

---

<div class="post-metadata">

**Author:** ![m52go](https://bisq.community/letter_avatar/m52go/32/5_5575768a8748004e209b776fc1b2916d.png) [@m52go](https://bisq.community/u/m52go)\
**Post date:** [October 29, 2019, 3:49pm UTC](https://bisq.community/t/critical-notice-finish-trades-before-upgrading-to-v1-2/8576/3 "2019-10-29T15:49:21Z")

</div>

v1.2 release is imminent.

**Please make sure to do the following before updating to v1.2:**

- complete all trades
- complete all disputes
- disable open offers (not delete, just disable)

Updating to v1.2 with unfinished trades and disputes will require an arbitrator to intervene and manually make payouts. Downgrading back to v1.1.7 to rectify the situation will not be possible, so please double-check before updating.

Disabling open offers prevents the chance that one of your offers is taken before you close the Bisq program and update, which could inadvertantly cause one of the scenarios above.

---

<div class="post-metadata">

**Author:** ![BitSpartacus](https://bisq.community/letter_avatar/bitspartacus/32/5_5575768a8748004e209b776fc1b2916d.png) [@BitSpartacus](https://bisq.community/u/BitSpartacus)\
**Post date:** [October 29, 2019, 11:20pm UTC](https://bisq.community/t/critical-notice-finish-trades-before-upgrading-to-v1-2/8576/4 "2019-10-29T23:20:00Z")

</div>

How do I disable an open offer please? I only see a delete button and I know that will cost me if I do it?

---

<div class="post-metadata">

**Author:** ![m52go](https://bisq.community/letter_avatar/m52go/32/5_5575768a8748004e209b776fc1b2916d.png) [@m52go](https://bisq.community/u/m52go)\
**Post date:** [October 29, 2019, 11:50pm UTC](https://bisq.community/t/critical-notice-finish-trades-before-upgrading-to-v1-2/8576/5 "2019-10-29T23:50:36Z")

</div>

Go to Portfolio \> Open Offers and uncheck the box in the Enabled column.

![Screenshot%20from%202019-10-29%2019-49-26](https://bisq.community/uploads/default/original/2X/5/5f056c3bb9c80809717f9ea21e5e7c0f7ea52912.png)
