# Bisq v1.2.1 released! **URL:** \ **Category:** Development\ **Created:** [October 29, 2019, 5:34pm UTC](https://bisq.community/t/bisq-v1-2-1-released/8610 "2019-10-29T17:34:41Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![christoph](https://bisq.community/user_avatar/bisq.community/christoph/32/1252_2.png) [@christoph](https://bisq.community/u/christoph)\ **Post date:** [October 29, 2019, 5:34pm UTC](https://bisq.community/t/bisq-v1-2-1-released/8610/1 "2019-10-29T17:34:41Z")
This is a hotfix release mainly covering following issues: - Fix incorrect display of account signing status: [1](https://github.com/bisq-network/bisq/pull/3514), [2](https://github.com/bisq-network/bisq/pull/3512) - [Remove unnecessary restriction for sell offers](https://github.com/bisq-network/bisq/pull/3518) Here are the release notes from v1.2.0: Bisq v1.2 ships several significant updates. A [new trade protocol](https://docs.bisq.network/trading-rules) moves to 2-of-2 multisig escrows for deposit funds, dispute resolution is overhauled to be more private and scalable, and [account signing](https://docs.bisq.network/payment-methods) removes 0.01 BTC buying limits for risky payment methods in major markets. **If you are updating from a previous version of Bisq, please make sure to do the following before updating to v1.2:** - complete all trades - complete all disputes - disable open offers (at “Portfolio/My Open Offers”) 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. ### DAO - [Apply rule to not allow BSQ outputs after BTC output for regular txs](https://github.com/bisq-network/bisq/pull/3413) - [Fix bug with not updating vote result table at vote result block](https://github.com/bisq-network/bisq/pull/3442) - [Fix vote results view](https://github.com/bisq-network/bisq/pull/3500) ### UI - Translation improvements [1](https://github.com/bisq-network/bisq/pull/3386) - [Translate name of Japan Bank Transfer for non-Japanese users](https://github.com/bisq-network/bisq/pull/3344) ### Trading - New trade protocol: [1](https://github.com/bisq-network/bisq/pull/3333), [2](https://github.com/bisq-network/bisq/pull/3340), [2](https://github.com/bisq-network/bisq/pull/3410), [3](https://github.com/bisq-network/bisq/pull/3414), [4](https://github.com/bisq-network/bisq/pull/3420), [5](https://github.com/bisq-network/bisq/pull/3439), [6](https://github.com/bisq-network/bisq/pull/3453), [7](https://github.com/bisq-network/bisq/pull/3464), [8](https://github.com/bisq-network/bisq/pull/3471), [9](https://github.com/bisq-network/bisq/pull/3474), [10](https://github.com/bisq-network/bisq/pull/3475), - Account signing: [1](https://github.com/bisq-network/bisq/pull/3334), [2](https://github.com/bisq-network/bisq/pull/3342), [3](https://github.com/bisq-network/bisq/pull/3365), [4](https://github.com/bisq-network/bisq/pull/3370), [5](https://github.com/bisq-network/bisq/pull/3374), [6](https://github.com/bisq-network/bisq/pull/3388), [7](https://github.com/bisq-network/bisq/pull/3390), [8](https://github.com/bisq-network/bisq/pull/3392), [9](https://github.com/bisq-network/bisq/pull/3403), [10](https://github.com/bisq-network/bisq/pull/3404), [11](https://github.com/bisq-network/bisq/pull/3406), [12](https://github.com/bisq-network/bisq/pull/3409), [13](https://github.com/bisq-network/bisq/pull/3415), [14](https://github.com/bisq-network/bisq/pull/3421), [15](https://github.com/bisq-network/bisq/pull/3435), [16](https://github.com/bisq-network/bisq/pull/3436), [16](https://github.com/bisq-network/bisq/pull/3445), [17](https://github.com/bisq-network/bisq/pull/3448), [18](https://github.com/bisq-network/bisq/pull/3450), [19](https://github.com/bisq-network/bisq/pull/3465), [20](https://github.com/bisq-network/bisq/pull/3467), [21](https://github.com/bisq-network/bisq/pull/3481), [22](https://github.com/bisq-network/bisq/pull/3490), [23](https://github.com/bisq-network/bisq/pull/3495), [24](https://github.com/bisq-network/bisq/pull/3496), [25](https://github.com/bisq-network/bisq/pull/3497), [26](https://github.com/bisq-network/bisq/pull/3499) - [Add mediator prefix to trade statistics](https://github.com/bisq-network/bisq/pull/3351) - [Add combo block explorer for Blockstream.info + Mempool.space](https://github.com/bisq-network/bisq/pull/3377) - [Increase minimum TX fee to 2 sats/vByte](https://github.com/bisq-network/bisq/pull/3387) - [Not show payment account details for blocked offers](https://github.com/bisq-network/bisq/pull/3425) - [Clean up trade statistics from duplicate entries](https://github.com/bisq-network/bisq/pull/3476) - [Format maker fee for BTC and BSQ correctly](https://github.com/bisq-network/bisq/pull/3498) - [Improve mediation result popup handling](https://github.com/bisq-network/bisq/pull/3503) ### Wallet - [Show connected Bitcoin network peer info](https://github.com/bisq-network/bisq/pull/3423) ### Assets Added 7 new assets: Animecoin (ANI), CTSCoin (CTSC), Donu (DONU), Faircoin (FAIR), ndau (XND), NoteBlockchain (NTBC), uPlexa (UPX) Removed two assets: Byte (GBYTE), Neos (NEOS) ---
**Author:** ![eeeper](https://bisq.community/letter_avatar/eeeper/32/6_22734026db12803ebb3e059622ac3534.png) [@eeeper](https://bisq.community/u/eeeper)\ **Post date:** [October 29, 2019, 6:35pm UTC](https://bisq.community/t/bisq-v1-2-1-released/8610/2 "2019-10-29T18:35:00Z")
I have a bunch of open offers which have very low deposits, which was fine under 2-of-3 but makes me feel very uncomfortable under 2-of-2. Do I just need to say goodbye to my BSQ fees paid here or is there a way to change the deposit % without losing my BSQ trading fees? ---
**Author:** ![DrFredPhD](https://bisq.community/letter_avatar/drfredphd/32/6_22734026db12803ebb3e059622ac3534.png) [@DrFredPhD](https://bisq.community/u/DrFredPhD)\ **Post date:** [October 29, 2019, 6:40pm UTC](https://bisq.community/t/bisq-v1-2-1-released/8610/3 "2019-10-29T18:40:23Z")
Just read through the new trade protocol and am a little concerned. I’ve completed about 70 trades, about 3 of those have had to go to arbitration, all for deposit txs not publishing correctly. It has been impossible to close these trades without an arbitrator as one of the partys tx never published they can’t sign the payout tx. Now I am worried this penalty transaction will result in my money being tied up even longer (or lost altogther). What has been done to reduce these trade bugs? In the event a trade does bug (which it seems to around 5% of the time), how can I make sure my funds are not lost if my deposit published fine but my counterpartys did not? I have a couple of other issues with this protocol too, but less important right now. I second I will most likely be raising my fee and deposit amount under this new protocol. ---
**Author:** ![christoph](https://bisq.community/user_avatar/bisq.community/christoph/32/1252_2.png) [@christoph](https://bisq.community/u/christoph)\ **Post date:** [October 30, 2019, 12:20pm UTC](https://bisq.community/t/bisq-v1-2-1-released/8610/4 "2019-10-30T12:20:52Z")
Unfortunately there is no way to change your deposit percentage in existing offers atm. ---
**Author:** ![christoph](https://bisq.community/user_avatar/bisq.community/christoph/32/1252_2.png) [@christoph](https://bisq.community/u/christoph)\ **Post date:** [October 30, 2019, 12:25pm UTC](https://bisq.community/t/bisq-v1-2-1-released/8610/5 "2019-10-30T12:25:06Z")
The trade protocol changed a bit so it could be that some old bugs are vanished already. Besides that we are working already on 1.2.2 which will be a bug fix release for a couple of nasty bugs, that we were finally able to reproduce locally during release testing of 1.2. So the arbitration use case with the new trade protocol should be a really rare one single digit in total within on month. ---
**Author:** ![tieck](https://bisq.community/letter_avatar/tieck/32/6_22734026db12803ebb3e059622ac3534.png) [@tieck](https://bisq.community/u/tieck)\ **Post date:** [October 30, 2019, 8:21pm UTC](https://bisq.community/t/bisq-v1-2-1-released/8610/6 "2019-10-30T20:21:08Z")
What exactly will happen if I would take with the new version an old offer that is not migrated yet to the new version? Would it fail or run with the old trade protocol version? I saw that some smaller markets do not have the column “Time since signing” in the offer book table, whereas in the EUR offer book there are entries with “N/A”. Therefore I assume that in a market without the “Time since signing” column in the offer book all makers did not yet upgrade to the new version. Is that correct? ---
**Author:** ![WToe](https://bisq.community/letter_avatar/wtoe/32/6_22734026db12803ebb3e059622ac3534.png) [@WToe](https://bisq.community/u/WToe)\ **Post date:** [October 30, 2019, 9:20pm UTC](https://bisq.community/t/bisq-v1-2-1-released/8610/7 "2019-10-30T21:20:44Z")
> [@tieck](#): > > What exactly will happen if I would take with the new version an old offer that is not migrated yet to the new version? Would it fail or run with the old trade protocol version? I just tried that, and bisq made it impossible to do so. Both traders have to be on the new version. ---
**Author:** ![christoph](https://bisq.community/user_avatar/bisq.community/christoph/32/1252_2.png) [@christoph](https://bisq.community/u/christoph)\ **Post date:** [October 31, 2019, 11:09am UTC](https://bisq.community/t/bisq-v1-2-1-released/8610/8 "2019-10-31T11:09:35Z")
You can’t take an old offer with the new version as it is prevent by the UI because of the different trade protocol. Account signing is only required for certain payment methods in certain markets: [https://docs.bisq.network/payment-methods.html#supported-fiat-payment-methods](https://docs.bisq.network/payment-methods.html#supported-fiat-payment-methods) [https://docs.bisq.network/payment-methods.html#account-signing](https://docs.bisq.network/payment-methods.html#account-signing) So if the column is not there or it displays “N/A” in an offer that this payment method doesn’t require account signing