[bisq-network/bisq] closing/cancellation of suspended transactions with the consensus of the two parties to the transaction without the participation of the curator/moderator of the transaction (#3516)
C# _
notifications at github.com
Wed Oct 30 06:24:38 UTC 2019
### Description
more manual handling is required
#### Version
Bisq x64 1.1.7 + 1.2.0
### Steps to reproduce
1. I sent a small amount of bitcoins from the _Electrum client to Bisq_.
When sending coins, a **1sat/byte transfer fee** was initially specified.
2. A transaction appears in the blockchain, but without confirmations.
In Bisq, I immediately see them on the balance and can open trades with traders on these coins.
3. Without waiting for confirmation of this transaction I open a trade with the trader on these coins
Now, in relation to this transaction, a **new transaction appears in the blockchain that does not have a confirmed parent** (_the very first transfer with a 1sat/byte commission_).
I do it regularly. Was doing before this incident and after this incident. Always everything went correctly. But there is one feature specifically in this transaction.
- The parent has a low сommission, so the transaction does not find confirmations for a long time (about 40 minutes waited).
- To speed up the procedure I decided to increase the Commission of the initial (still not confirmed) transaction to 10 sat/byte (Electrum has such a function).
That's probably what caused the problem. The deal is displayed in the current open and what to do with it I do not understand.
Opened a dispute in Bisq. Through what the time debate was closed and all without changes. The deal is hanging open.
There is an error message in the transaction itself:
```
An error occurred at task: SignMediatedPayoutTx
Exception message: trade.getDepositTx() must not be null
```
### Expected behaviour
Participants in the transaction must be able to cancel transactions by mutual consent. In General, bitcoins returned somehow to Bisq, but the transaction for this operation expects a transfer from me apparently.
### Actual behaviour
The trade is displayed in the list of active trades.
#### Device or machine
Win7 x64 (actual updates)
#### P.S.
The moderator of the transaction has the right to close or cancel such "slow" transactions? What is the protocol for such situations?
--
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/3516
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191029/1009cca1/attachment.html>
More information about the bisq-github
mailing list