[bisq-network/bisq] when seller as taker using min btc range security deposit is higher (#3869)

[beingindot]

<!--
   SUPPORT REQUESTS: This is for reporting bugs in the Bisq app.
   If you have a support request, please join #support on Bisq's
   Keybase team at https://keybase.io/team/Bisq
-->

### Description
when seller takes an offer and fills min btc amount, security deposit is around 75%

<!-- brief description of the bug -->

#### Version
1.2.5
<!-- commit id or version number -->

### Steps to reproduce
1. alice puts buy offer with 0.05 - 0.25 btc range
2. alice pays security deposit of 0.0375 btc
3. bob takes that offer
4. bob fills 0.05 as btc amount
5. bob pays 0.0375 btc as security deposit which is way more 15%

<!--if you can reliably reproduce the bug, list the steps here  -->

### Expected behaviour
security deposit is 15%
<!--description of the expected behavior -->

### Actual behaviour
security deposit is calculated based on max btc range
<!-- explain what happened instead of the expected behaviour -->

### Screenshots
![Screenshot from 2020-01-07 16-56-48](https://user-images.githubusercontent.com/55691179/71894869-7578b100-3175-11ea-8a22-7f21965eacbd.png)
![Screenshot from 2020-01-07 16-56-55](https://user-images.githubusercontent.com/55691179/71894881-7b6e9200-3175-11ea-8c27-0d0fcfc2c1ff.png)

<!--Screenshots if gui related, drag and drop to add to the issue -->

#### Device or machine

<!-- device/machine used, operating system -->



#### Additional info
Please close this if not a bug @chimp1984 
<!-- Additional information useful for debugging (e.g. logs) -->


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/3869
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200107/3247381a/attachment.html>