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 BJPZHDY #137

Closed
pfergi42 opened this issue Sep 24, 2018 · 6 comments
Closed

Fee Reimbursement for trade BJPZHDY #137

pfergi42 opened this issue Sep 24, 2018 · 6 comments

Comments

@pfergi42
Copy link

Reported bug here: bisq-network/bisq#1604
Blockchain explorer link: https://www.blockchain.com/btc/tx/d81ef07166c34032ff98179e0ed39abc095e513a22370dfb7149d4e38fcc87fe

screen shot 2018-09-24 at 11 53 55 am

d81ef07166c34032ff98179e0ed39abc095e513a22370dfb7149d4e38fcc87fe
6813c33e76bef5c33723cbf5e968577f12b7b31eb874225e00ae67eed68eaa69

@ManfredKarrer
Copy link
Member

Thanks for filing the issue. Please have patience until there are a number of issues so we can do a batch tx.

@KanoczTomas KanoczTomas moved this from Todo to In progress in Lost fee reimbursements Oct 16, 2018
@KanoczTomas
Copy link
Member

6813c33e76bef5c33723cbf5e968577f12b7b31eb874225e00ae67eed68eaa69 is marked as transmitted (needs to be reimbursed), but d81ef07166c34032ff98179e0ed39abc095e513a22370dfb7149d4e38fcc87fe is on the blockchain as well. @cbeams please review.

@KanoczTomas KanoczTomas moved this from In progress to Waiting for info in Lost fee reimbursements Oct 17, 2018
@cbeams
Copy link
Member

cbeams commented Oct 17, 2018

@KanoczTomas, I'm not sure why d81ef... was not marked as transmitted in the screenshot, but it should be reimbursed as well.

@cbeams cbeams moved this from Waiting for info to Todo in Lost fee reimbursements Oct 17, 2018
@KanoczTomas
Copy link
Member

ok, thanks! Will work on it later ...

@KanoczTomas KanoczTomas moved this from Todo to In progress in Lost fee reimbursements Oct 18, 2018
@KanoczTomas
Copy link
Member

@ManfredKarrer #136 & #137 have the same "issue". Both maker and taker were broadcast to the network, but only one is marked as complete on the screenshot. Could this be a bug?

KanoczTomas added a commit that referenced this issue Oct 18, 2018
@KanoczTomas KanoczTomas moved this from In progress to Staged in Lost fee reimbursements Oct 18, 2018
@cbeams
Copy link
Member

cbeams commented Oct 20, 2018

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

@cbeams cbeams closed this as completed Oct 20, 2018
Lost fee reimbursements automation moved this from Staged to Closed Oct 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

4 participants