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

Open disputes because of unconfirmed transactions #1031

Closed
amuuza opened this issue Nov 29, 2017 · 6 comments
Closed

Open disputes because of unconfirmed transactions #1031

amuuza opened this issue Nov 29, 2017 · 6 comments

Comments

@amuuza
Copy link

amuuza commented Nov 29, 2017

My trade was completed even though the payout did not have 1 confirmation after many hours.
Sometimes Bisq may choose a too low fee to ever have a confirmation.
It would be nice to have a way to open a dispute in those cases.

@ManfredKarrer
Copy link
Member

Fee estimation is a difficult issue. If it is too high users complain if it is too low such cases can happen. Hard to find the right balance. It also depends on earlier unconfirmed txs in the chain (funding tx from external wallet is outside of our control). So far I have not got any other complaints that tx did not get confirmed in a reasonable time. But if so I will increase the fees again. You can open a dispute by cmd+o but you should not just because the deposit was delayed as long the trade period has not expired. Even if the period expires users con continue the trade. The option ot open a dispute is optional not mandatory.

@mrosseel
Copy link
Member

@ManfredKarrer I think the question is: SUPPOSE the multisig payout never confirms, what can the trader do? I tried in my Bisq and I couldn't open a dispute on a completed trade. Is this correct?

@ManfredKarrer
Copy link
Member

You can open a dispute also with a non confirmed dispute, though if the arbitrator close it will still be unconfirmed. A completed trade cannot be disputed as deposit is payout out. Beside in the April tx spam time where our tx fee were too low we never had issues with never confirming txs. If it happens the tx is just invalid so money has not left wallet but BitcoinJ does not handle that well. Was a bit of a mess back then but at the end all worked. SPV chain resync or restore from seeds was usually working to get a clean wallet again.

@amuuza
Copy link
Author

amuuza commented Nov 29, 2017

Well, if we are always able to open a dispute (through Ctrl+o or Alt+o in my case) then it's ok. I undestand there is no easy solution.
I guess this issue can be closed.

@ManfredKarrer
Copy link
Member

If there are more complaints regarding too long conf. time we will increase the fee estimation but then people complain about higher fees ;-(

@ripcurlx
Copy link
Member

Closing as complete. The counter starts now after the first block confirmation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants