# Sending BSQ failed - transaction not seen by peers / not confirming \[SOLVED\] **URL:** \ **Category:** Support\ **Created:** [August 4, 2019, 12:35pm UTC](https://bisq.community/t/sending-bsq-failed-transaction-not-seen-by-peers-not-confirming-solved/8185 "2019-08-04T12:35:45Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![CBA](https://bisq.community/letter_avatar/cba/32/5_5575768a8748004e209b776fc1b2916d.png) [@CBA](https://bisq.community/u/CBA)\ **Post date:** [August 4, 2019, 12:35pm UTC](https://bisq.community/t/sending-bsq-failed-transaction-not-seen-by-peers-not-confirming-solved/8185/1 "2019-08-04T12:35:45Z")
After being able to obtain access to my old BSQ wallet after facing a problem with an imported BSQ payment account ([Can not access newly bought BSQ on imported payment account](https://bisq.community/t/can-not-access-newly-bought-bsq-on-imported-payment-account/8125/8)) I tried to send the contained BSQ to my new BSQ wallet. However even after extensive waiting the corresponding transaction is not confirming (seen by 0 peers / 0 confirmations). What may be the reason and what can I do? Is it possible to either a) resend the transaction b) export the privated key from the old BSQ wallet and import it into the new one ? ---
**Author:** ![huey](https://bisq.community/letter_avatar/huey/32/5_5575768a8748004e209b776fc1b2916d.png) [@huey](https://bisq.community/u/huey)\ **Post date:** [August 5, 2019, 12:27pm UTC](https://bisq.community/t/sending-bsq-failed-transaction-not-seen-by-peers-not-confirming-solved/8185/2 "2019-08-05T12:27:03Z")
See if [these steps](https://bisq.community/t/issue-transaction-not-being-broadcast/8135) can help you. ---
**Author:** ![sqrrm](https://bisq.community/letter_avatar/sqrrm/32/5_5575768a8748004e209b776fc1b2916d.png) [@sqrrm](https://bisq.community/u/sqrrm)\ **Post date:** [August 5, 2019, 2:07pm UTC](https://bisq.community/t/sending-bsq-failed-transaction-not-seen-by-peers-not-confirming-solved/8185/3 "2019-08-05T14:07:38Z")
Resyncing SPV wallet might be the best way to republish the tx if that is the issue. ---
**Author:** ![CBA](https://bisq.community/letter_avatar/cba/32/5_5575768a8748004e209b776fc1b2916d.png) [@CBA](https://bisq.community/u/CBA)\ **Post date:** [August 10, 2019, 5:59pm UTC](https://bisq.community/t/sending-bsq-failed-transaction-not-seen-by-peers-not-confirming-solved/8185/4 "2019-08-10T17:59:16Z")
Reyncing the SPV wallet does indeed help by cleaning the non-published transaction. However when I try again to send the BSQ I encounter the same problem - transaction not seen by any peers (I’ve resynced the SPV chain twice and everything was in sync). What else can I do? Is it possible to send or import the BSQ manually using the extracted private keys? ---
**Author:** ![CBA](https://bisq.community/letter_avatar/cba/32/5_5575768a8748004e209b776fc1b2916d.png) [@CBA](https://bisq.community/u/CBA)\ **Post date:** [August 10, 2019, 8:07pm UTC](https://bisq.community/t/sending-bsq-failed-transaction-not-seen-by-peers-not-confirming-solved/8185/5 "2019-08-10T20:07:02Z")
Finally succeeded in sending the BSQ after reducing(!) the default withdrawal fee. 🙃 Could it be that a transaction is not recognized by peers if the remaining BTC after paying for a transaction is below the dust limit (600 sat)? ---
**Author:** ![sqrrm](https://bisq.community/letter_avatar/sqrrm/32/5_5575768a8748004e209b776fc1b2916d.png) [@sqrrm](https://bisq.community/u/sqrrm)\ **Post date:** [August 11, 2019, 2:40pm UTC](https://bisq.community/t/sending-bsq-failed-transaction-not-seen-by-peers-not-confirming-solved/8185/6 "2019-08-11T14:40:12Z")
Indeed, transactions with outputs below the dust limit (546 sat) won’t be propagated by the network. We have taken some precaution to avoid creating such outputs but perhaps there are more cases. Are you sure there was an output below dust limit? What did you do to create it, just trying to send a normal BSQ tx?