# Repeated Trade Failures & Fee Loss After Upgrade

**URL:** <https://bisq.community/t/repeated-trade-failures-fee-loss-after-upgrade/13911>\
**Category:** Support\
**Created:** [August 11, 2026, 6:53am UTC](https://bisq.community/t/repeated-trade-failures-fee-loss-after-upgrade/13911 "2026-08-11T06:53:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lmdomah](https://bisq.community/letter_avatar/lmdomah/32/5_5575768a8748004e209b776fc1b2916d.png) [@lmdomah](https://bisq.community/u/lmdomah)\
**Post date:** [August 11, 2026, 6:53am UTC](https://bisq.community/t/repeated-trade-failures-fee-loss-after-upgrade/13911/1 "2026-08-11T06:53:47Z")

</div>

**Environment**

- OS: Windows 11 Pro

- BISQ version: _1.10.4_

- Bitcoin peers: 7 / BISQ network peers: 12

**What’s happening** Since the latest upgrade I’m consistently seeing three errors when attempting to sell:

- ProcessOfferAvailabilityResponse — snapshot height does not match. DAO data may not be synced.

- Timeout reached: Peer has not responded.

- You lost connection to the maker.

The DAO state panel shows _“Your local node is in consensus with the network”_ and peer connectivity looks healthy, so something appears to have shifted during the upgrade.

**Fees lost on failed trades** On the occasions a trade does get through, it fails mid-process and the fees are charged regardless

**Already tried**

- Rebuild DAO state from resource

- Resync SPV wallet

- Deleted Tor files and restarted

- Reinstalled BISQ (repair install) and restarted

All attempted, issue persists.

Really appreciate any help getting this resolved, love the platform and just want to get back to trading smoothly.

---

<div class="post-metadata">

**Author:** ![suddenwhipvapor](https://bisq.community/user_avatar/bisq.community/suddenwhipvapor/32/3291_2.png) [@suddenwhipvapor](https://bisq.community/u/suddenwhipvapor)\
**Post date:** [August 12, 2026, 7:39pm UTC](https://bisq.community/t/repeated-trade-failures-fee-loss-after-upgrade/13911/2 "2026-08-12T19:39:36Z")

</div>

try starting bisq from commandline with argument  
`--skipBsqBlockProvidersSignatureVerification=true`
