# Bisq v1.1.0 released!

**URL:** <https://bisq.community/t/bisq-v1-1-0-released/7571>\
**Category:** Development\
**Created:** [May 3, 2019, 11:08am UTC](https://bisq.community/t/bisq-v1-1-0-released/7571 "2019-05-03T11:08:53Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![christoph](https://bisq.community/user_avatar/bisq.community/christoph/32/1252_2.png) [@christoph](https://bisq.community/u/christoph)\
**Post date:** [May 3, 2019, 11:08am UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/1 "2019-05-03T11:08:53Z")

</div>

This release adds an impotant security meassurement to protect against the bank chargeback scammer. With this in place we can remove the banning of certain SEPA regions and Interac scheduled for the 5th of May.

The new restrictions are as follows:  
If a fiat payment account was created after March 15th 2019 it is considered risky and limited to 0.01 BTC trades if the account holder is the BTC buyer. For the seller there is no restriction. The restriction is applied to all payment methods based on bank transfers which carry some chargeback risk (Sepa, Sepa Instant, Interact, Zelle, Revolut, National bank transfers, Chase Quick Pay, Popmoney, Moneybeam, Uphold).

On May 5th we will block old accounts from trading to enable us to unblock the banned SEPA regions and Interac. So please **update as soon as possible**!

This solution is an intermediary step on the way to a more sophisticated protection solution (see [proposals](https://github.com/bisq-network/proposals/issues/78)) but those will require more time to get implemented.

Beside that there are some other important fixes:

- Fix account age display in peer avatar
- Decrease the security deposit amount for altcoins
- Improve BSQ block propagation
- Add search field to trade history

### DAO

- [Request blocks in case we have not received it](https://github.com/bisq-network/bisq/pull/2730)
- [Add node address and capabilities to prevent timeout](https://github.com/bisq-network/bisq/pull/2732)
- [Fix issues with DAO full mode in preferences](https://github.com/bisq-network/bisq/pull/2736)
- [Count cycles correctly](https://github.com/bisq-network/bisq/pull/2757)

### UI

- [Add UTF8 for getBytes calls](https://github.com/bisq-network/bisq/pull/2737)
- [Use existing styling for developer alert message](https://github.com/bisq-network/bisq/pull/2746)
- [Use same precision for all x-axis labels](https://github.com/bisq-network/bisq/pull/2763)

### Trading

- [Add check for account age to apply restrictions](https://github.com/bisq-network/bisq/pull/2801)
- [Improve ignore list](https://github.com/bisq-network/bisq/pull/2733)
- [Improve handling of editing of offers with invalid security deposit](https://github.com/bisq-network/bisq/pull/2740)
- [Use different security deposit for fiat-crypto and crypto-crypto trades](https://github.com/bisq-network/bisq/pull/2742)
- [Add filter to trade history](https://github.com/bisq-network/bisq/pull/2752)
- [Fix account age display of peer](https://github.com/bisq-network/bisq/pull/2753)
- [Don’t disable confirm buttons](https://github.com/bisq-network/bisq/pull/2764)

### Wallet

- [Set p2shHeader to fix address validation issues](https://github.com/bisq-network/bisq/pull/2728)

### Development

- [Remove BSQ filter for crypto currencies](https://github.com/bisq-network/bisq/pull/2734)
- [Reflect pricenode operator change in ProvidersRepository](https://github.com/bisq-network/bisq/pull/2769)
- [Update mobile notification relay node DEV\_URL IP address](https://github.com/bisq-network/bisq/pull/2770)

### Assets

Added two new asset: List Trust Eth reOrigin (TEO) and ParsiCoin (PARS)

---

<div class="post-metadata">

**Author:** ![huey](https://bisq.community/letter_avatar/huey/32/5_5575768a8748004e209b776fc1b2916d.png) [@huey](https://bisq.community/u/huey)\
**Post date:** [May 3, 2019, 1:09pm UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/2 "2019-05-03T13:09:14Z")

</div>

No prompt inside the software to update.

---

<div class="post-metadata">

**Author:** ![christoph](https://bisq.community/user_avatar/bisq.community/christoph/32/1252_2.png) [@christoph](https://bisq.community/u/christoph)\
**Post date:** [May 3, 2019, 1:35pm UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/3 "2019-05-03T13:35:42Z")

</div>

True - I only tested on Regtest if the message works. The problem is that we have two alert message out there right now. The scam alert and the update alert and the depending on the timing one overwrites the other during startup. I have to wait on Manfred to remove the scam alert he sent out, so that the update message becomes visible.

Thanks for pointing that out!

---

<div class="post-metadata">

**Author:** ![GOran](https://bisq.community/letter_avatar/goran/32/5_5575768a8748004e209b776fc1b2916d.png) [@GOran](https://bisq.community/u/GOran)\
**Post date:** [May 3, 2019, 1:42pm UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/4 "2019-05-03T13:42:27Z")

</div>

> [@huey](#):
>
> No prompt inside the software to update.

I got a notification about 1.1.0 being released

---

<div class="post-metadata">

**Author:** ![christoph](https://bisq.community/user_avatar/bisq.community/christoph/32/1252_2.png) [@christoph](https://bisq.community/u/christoph)\
**Post date:** [May 3, 2019, 1:48pm UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/5 "2019-05-03T13:48:01Z")

</div>

Yes, it’s unfortunately a timing issue right now, as we only used the alert system for app updates and not for broadcast messages. It will be shown soon to all users.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [May 3, 2019, 3:43pm UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/6 "2019-05-03T15:43:00Z")

</div>



---

<div class="post-metadata">

**Author:** ![goraelec](https://bisq.community/letter_avatar/goraelec/32/5_5575768a8748004e209b776fc1b2916d.png) [@goraelec](https://bisq.community/u/goraelec)\
**Post date:** [May 3, 2019, 3:46pm UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/7 "2019-05-03T15:46:09Z")

</div>

Hello.

There’s one issue with the current restrictions based on the account age.

I sell BTC only for EUR (SEPA) and my account is ~30 days old. I want to trade with reputable peers, even the ones I’ve already traded with, whose acc age is more than a year, but I cannot do so.

I know this is only temporary, but I’m perfectly aware of the risks and have my own methods towards mitigating them. By disallowing me to participate in trades with reputable peers, this restriction goes against the very vision of Bisq:

> No power of censoring, confiscating, monitoring or controlling your financial interaction.

Is there an estimate as to when 1.2.0 with the new protocol will be ready?

---

<div class="post-metadata">

**Author:** ![christoph](https://bisq.community/user_avatar/bisq.community/christoph/32/1252_2.png) [@christoph](https://bisq.community/u/christoph)\
**Post date:** [May 3, 2019, 4:02pm UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/8 "2019-05-03T16:02:43Z")

</div>

Please wait (around two days) until we force people to update to 1.1.0 to trade. When we do this we’ll also lift the restrictions again for certain payment methods (SEPA is one of them). So people with payment accounts created before March 15th will be able to trade as before the restrictions.

---

<div class="post-metadata">

**Author:** ![christoph](https://bisq.community/user_avatar/bisq.community/christoph/32/1252_2.png) [@christoph](https://bisq.community/u/christoph)\
**Post date:** [May 3, 2019, 4:04pm UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/9 "2019-05-03T16:04:12Z")

</div>

As a seller you can trade after this also with reputable peers as takers (even if your account age as seller is ~30 days old)

---

<div class="post-metadata">

**Author:** ![huey](https://bisq.community/letter_avatar/huey/32/5_5575768a8748004e209b776fc1b2916d.png) [@huey](https://bisq.community/u/huey)\
**Post date:** [May 3, 2019, 7:15pm UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/10 "2019-05-03T19:15:47Z")

</div>

> [@christoph](#):
>
> The restriction is applied to all payment methods based on bank transfers which carry some chargeback risk (Sepa, Sepa Instant, Interact, Zelle, Revolut, National bank transfers, Chase Quick Pay, Popmoney, Moneybeam, Uphold).

Just to confirm, Transfer with specific bank and Transfer with the same bank are also included right?

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [May 4, 2019, 1:42am UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/11 "2019-05-04T01:42:53Z")

</div>

Yes, the are also included.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [May 5, 2019, 7:04pm UTC](https://bisq.community/t/bisq-v1-1-0-released/7571/12 "2019-05-05T19:04:58Z")

</div>


