Fee reimbursement for trade 718499

[metaltrance]

Maker: 3080165d189cc124eeb47e98d7e5902a1921e547381472a9294e08e77ea91651
Taker: 82cf5fb5d2198022b7ac85d83622bab513c1a005f806362ef30e328cddce8854
Deposit: bdb359dfc12679f7bfdab7bc7a38a88ece655c38aa7fa99f35f536556b8a79ef

Bisq version: v1.7.4
BTC address for reimbursement:
bc1q5m0ytwjswle9kgjghfdu67l85wrda820kfzgr5

Other notes:
Error: Deposit transaction is null or has unexpected input count

[ghost]

The deposit tx is valid. You can continue the trade as normal, open mediation (ctrl-o), or seek assistance on keybase. Whatever you're more comfortable with.

FYI that bug is bisq-network/bisq#5494 which has a fix pending for next release, 1.7.5

[metaltrance]

The app wont let me continue the trade and tells me not to send any fiat.

[metaltrance]

[ghost]

Yes, that is a symptom of the bug. Try restarting Bisq, if the issue persists, open mediation (ctrl-o).

[metaltrance]

ok thanks

[metaltrance]

It wont let me open mediation and tells me to do a SPV resync instead. I already did that but will try again.

[metaltrance]

After spv resync and restarting it popped up this error.

[metaltrance]

But the open trade now looks ok and the status is correct. dep tx id is populated and no more error.
Can I safely continue with the fiat payment?

[metaltrance]

This error keeps popping up sometimes at a random time it seems... also after restart
The trade data looks ok though.
#1014 (comment)

[ghost]

"The maker fee transaction for offer with ID 081732 is invalid" is saying that your offer 081732 is bad because the transaction does not exist in the blockchain. Delete that offer and the message will go away.

But the open trade now looks ok and the status is correct. dep tx id is populated and no more error. Can I safely continue with the fiat payment?

For trade 718499 yes, I'd suggest you continue with it.

[metaltrance]

Ok I continued with the trade and removed that offer. Not sure what went wrong there...
Thanks for your help.

[metaltrance]

FYI: This issue just happened to me again on v1.7.5 so it does not seem to be resolved.