Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
badhitman opened this issue Oct 30, 2019 · 2 comments

Comments

@badhitman
Copy link

badhitman commented Oct 30, 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).
  • 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?

@wiz
Copy link
Member

wiz commented Oct 31, 2019

There is a bug which can prevent in-trade chat and support chat from working on bugged trades, so please join Bisq's #support channel on Keybase to communicate with arbitrators and developers directly.

@badhitman
Copy link
Author

badhitman commented Nov 3, 2019

Thanks for the answer. the deal never goes away. This deal will now forever hang so open. I created a new wallet and moved on.

However, we would very much like to be able to cancel such deals on the condition of consensus. If the payment is not started and both parties to the transaction agree to cancel the transaction, they must be canceled.

@ripcurlx ripcurlx removed the a:bug label Jan 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants