# Why does Bisq still allow unconfirmed transactions to be used to open an offer?

**URL:** <https://bisq.community/t/why-does-bisq-still-allow-unconfirmed-transactions-to-be-used-to-open-an-offer/4422>\
**Category:** Support\
**Created:** [January 13, 2018, 11:20am UTC](https://bisq.community/t/why-does-bisq-still-allow-unconfirmed-transactions-to-be-used-to-open-an-offer/4422 "2018-01-13T11:20:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pleia](https://bisq.community/letter_avatar/pleia/32/5_5575768a8748004e209b776fc1b2916d.png) [@pleia](https://bisq.community/u/pleia)\
**Post date:** [January 13, 2018, 11:20am UTC](https://bisq.community/t/why-does-bisq-still-allow-unconfirmed-transactions-to-be-used-to-open-an-offer/4422/1 "2018-01-13T11:20:22Z")

</div>

I can see how this made sense in 2015, but with full blocks and large spam attacks, we’re now seeing a steep rise in offers that never hit the blockchain because the taker or maker funds were never confirmed, and have too low a fee to confirm during the total length of the trade.

This is a huge problem, as the party whose transactions HAD been confirmed when the offer was accepted takes a **total loss** on the fees, AND has no recourse to the counterparty’s deposit, since it was never confirmed.

1. Am I understanding this wrong?
2. Isn’t this a huge risk that makes Bisq undependable and highly risky for essentially no reason (other than to make things slightly more convenient)?
3. Why doesn’t Bisq just require that funds have 1 confirmation before allowing a given transaction to be included in the Available Balance?

---

<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:** [January 13, 2018, 12:26pm UTC](https://bisq.community/t/why-does-bisq-still-allow-unconfirmed-transactions-to-be-used-to-open-an-offer/4422/2 "2018-01-13T12:26:27Z")

</div>

The deposit tx uses the inputs of both traders. If one would do a double-spend or RBF the deposit tx is invalid so no harm to the other trader beside loss of time.  
Requiring confirmation decreases the usability as you have to wait longer before you can start trading or making an offer.

---

<div class="post-metadata">

**Author:** ![pleia](https://bisq.community/letter_avatar/pleia/32/5_5575768a8748004e209b776fc1b2916d.png) [@pleia](https://bisq.community/u/pleia)\
**Post date:** [January 13, 2018, 1:11pm UTC](https://bisq.community/t/why-does-bisq-still-allow-unconfirmed-transactions-to-be-used-to-open-an-offer/4422/3 "2018-01-13T13:11:36Z")

</div>

I wasn’t referring to double-spends as the risk. The risk is loss of fees and no trade going thru after waiting for the entire duration of the trade.

Isn’t that a much more serious usability issue than having to wait for a confirmation before trading?

---

<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:** [January 22, 2018, 12:46am UTC](https://bisq.community/t/why-does-bisq-still-allow-unconfirmed-transactions-to-be-used-to-open-an-offer/4422/4 "2018-01-22T00:46:45Z")

</div>

Those problems with not confirmed transactions nearly never happened before. There have been some issues over the last 2 months and with the 0.6.4 release those should be hopefully resolved.