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.

Sign up for GitHub

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

Jump to bottom

Fee reimbursement for trade viq9n #57

Closed
cbeams opened this issue Jan 23, 2018 · 5 comments
Closed

Fee reimbursement for trade viq9n #57

cbeams opened this issue Jan 23, 2018 · 5 comments
Assignees
@cbeams

Comments

@cbeams
Copy link
Contributor

cbeams commented Jan 23, 2018

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem tracked at bisq-network/bisq#1193, investigated at bisq-network/bisq#1195, and now fixed in Bisq v0.6.4 with the resolution of bisq-network/bisq#1244.

IMPORTANT: If you have not yet upgraded to Bisq v0.6.4, please do so immediately at https://bisq.network/downloads.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.
@cbeams cbeams mentioned this issue Jan 23, 2018
Closed
@cbeams
Copy link
Contributor Author

cbeams commented Jan 23, 2018

Note: I discovered this trade via the forum at https://bisq.community/t/arbitration-for-transaction-id-10687703dbe0cb1b995374264b05c2a6792e60aff88f5c2a3359561ee929f108/4503/

We know the deposit transaction failed to broadcast, and we know that the trader that reached out paid their fees via transaction https://bitaps.com/8595dfe957b46c4536eb6930599e99ddbc0aab5007c1a712588e1680ab3c48b1. It is not yet clear whether this was the maker or taker transaction, but I've asked the trader to clarify that.

Maker: TBD
Taker: TBD
Deposit: 10687703dbe0cb1b995374264b05c2a6792e60aff88f5c2a3359561ee929f108

cbeams added a commit that referenced this issue Jan 29, 2018
@cbeams
Add placeholder entries for add'l reimbursements (#35)
e3fbddf 
For #24, #26, #29, #56, #57, #60, #61, #62, #63
@cbeams
Copy link
Contributor Author

cbeams commented Jan 29, 2018

@keo-bisq, I need a screenshot and plain text of Maker / Taker / Deposit transaction IDs for this trade. Please provide this info and I'll get them staged for reimbursement as appropriate. Thanks.

@cbeams
Copy link
Contributor Author

cbeams commented Jan 29, 2018 •
edited
Loading

I have just figured out via a forum PM sent to me that either the maker or taker transaction in this trade was 8595dfe957b46c4536eb6930599e99ddbc0aab5007c1a712588e1680ab3c48b1 . I am staging it for reimbursement now.

UPDATE: corrected transaction ID. I originally accidentally posted the deposit transaction ID as seen in comments above.

cbeams added a commit that referenced this issue Jan 29, 2018
@cbeams
Add txns for fee reimbursement #57
b563606
@cbeams
Copy link
Contributor Author

cbeams commented Jan 29, 2018

Staged for reimbursement in b563606

@cbeams cbeams assigned cbeams and unassigned keo-bisq Jan 29, 2018
@cbeams
Copy link
Contributor Author

cbeams commented Jan 31, 2018

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

@cbeams cbeams closed this as completed Jan 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cbeams cbeams

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cbeams @keo-bisq