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

Fee reimbursement for trade WPREIBWQ #121

Closed
cbeams opened this issue Jun 13, 2018 · 7 comments
Closed

Fee reimbursement for trade WPREIBWQ #121

cbeams opened this issue Jun 13, 2018 · 7 comments

Comments

@cbeams
Copy link
Contributor

cbeams commented Jun 13, 2018

UPDATE: see #121 (comment)

Background

From @pfischer1290 in bisq-network/bisq#1193 (comment):

image

@ManfredKarrer, do you recall what the best course of action is in a case like this?

@pfischer1290
Copy link

The Trade got stuck before reaching first point. Im available for additional information and logs or sth elese at any time. thanks for your help guys
bildschirmfoto 2018-06-13 um 13 36 52

@ManfredKarrer
Copy link

@pfischer1290 Can you post both maker and taker fee tx? You can see those at the trade details when clicking on the trade ID.

@ManfredKarrer
Copy link

The output of the maker fee tx (second ouput) leads to another funding tx, so it was not spent for a deposit tx. The take fee tx output for the deposit is still unspent. So you can select any MultiSig address in the dialog and tell the arbitrator that the deposit tx was never created so he can close the failed trade. You should see after the trade has been closed by the arbitrator all balances as expected.
The bug might have been cause by a the wallet db being not in sync with the wallet.
I would recommend to start over with a new data directory. See: https://bisq.community/t/switching-to-a-new-data-directory/1697
You can export the accounts and you should copy over the signature key as described here to not lose the account age witness (trade limits based on account age). See: https://bisq.community/t/carry-over-account-age-witness-to-new-data-directory/5605

@cbeams
Copy link
Contributor Author

cbeams commented Jun 14, 2018

image

Maker: c361683b07c83345bfe421abf1bcb922cee000b94ac747e2dcc1dcd75ca9a2e6
Taker: a4e625884668862a880f09f7886c9a6e0b05f325f4216b44195a0feebadc5657
Deposit: b175e56b3a6278a364746f0719a5ea751f35d0b31ddf3884589fbffc1292d60d

Deposit tx was never published. Both maker and taker transactions to be reimbursed in #101.

KanoczTomas added a commit that referenced this issue Oct 16, 2018
@cbeams
Copy link
Contributor Author

cbeams commented Oct 20, 2018

Closing as reimbursed via the batch transaction documented at #101 (comment).

@yourwpguy
Copy link

Trade ID: 423719
Maker: 4b5e5ddaec3c3674e7dc7f63257d2690ce18929b9cf131ea7e67c80fe9525533
Taker: 144dfec41edcd4ff3cc49c05c01eb307b1ef142f30f8f5a562bfad87dc39415f
Deposit: 1613811bd3449022a522ce0b638c727306fd6eb7b7655fa1d7c718ec93270607

Deposit tx was never published. What to do next?

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