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

Bisq allows requesting "arbitration" before timelock expires on payout TX #4064

Closed
wiz opened this issue Mar 15, 2020 · 5 comments
Closed

Bisq allows requesting "arbitration" before timelock expires on payout TX #4064

wiz opened this issue Mar 15, 2020 · 5 comments

Comments

@wiz
Copy link
Contributor

wiz commented Mar 15, 2020

Description

Since the timelocked payout TX will be rejected by the Bitcoin network if broadcast before the timelock expires, Bisq must not attempt to broadcast the TX before then. However, it seems currently Bisq allows this, which causes major support issues for mediators.

Version

v1.2.8

Steps to reproduce

  1. Create an offer on Alice
  2. Take the offer on Bob
  3. Alice requests mediation
  4. Mediator closes mediation case (suggested payout can be anything, doesn't matter)
  5. Alice requests "arbitration"

Expected behaviour

Alice's node should not attempt to broadcast timelocked payout TX until after timelock expires

Actual behaviour

Alice's node broadcasts still-timelocked payout TX which is rejected by Bitcoin network, and funds are not donated to the Bisq donation address

@stale
Copy link

stale bot commented Jun 13, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the was:dropped label Jun 13, 2020
@stale
Copy link

stale bot commented Jun 20, 2020

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

@stale stale bot closed this as completed Jun 20, 2020
@chimp1984
Copy link
Contributor

@wiz Are you sure, if so thats a serious bug. Will add it to my list... Ticket should be reopened.

@wiz
Copy link
Contributor Author

wiz commented Aug 29, 2020

It was 6 months ago but IIRC there was a trader who had this issue and I came up with the steps to reproduce from analyzing their bisq.log

@chimp1984
Copy link
Contributor

I tested it on regtest (there is only 5 blocks locktime) and all worked as expected. Maybe there was some earlier bug? If you see it again please let me know!

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

2 participants