Fee Reimbursement for trade BJPZHDY

[pfergi42]

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

d81ef07166c34032ff98179e0ed39abc095e513a22370dfb7149d4e38fcc87fe
6813c33e76bef5c33723cbf5e968577f12b7b31eb874225e00ae67eed68eaa69

[ManfredKarrer]

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

[KanoczTomas]

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

[cbeams]

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

[KanoczTomas]

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

[KanoczTomas]

@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?

[cbeams]

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