# BTC withdrawal transaction not sent? **URL:** \ **Category:** Support\ **Created:** [January 15, 2018, 5:51pm UTC](https://bisq.community/t/btc-withdrawal-transaction-not-sent/4461 "2018-01-15T17:51:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![haenzl](https://bisq.community/letter_avatar/haenzl/32/5_5575768a8748004e209b776fc1b2916d.png) [@haenzl](https://bisq.community/u/haenzl)\ **Post date:** [January 15, 2018, 5:51pm UTC](https://bisq.community/t/btc-withdrawal-transaction-not-sent/4461/1 "2018-01-15T17:51:23Z")
Hi guys, Yetserday evening I tried to withdraw funds from BISQ. Latest version v0.6.3. I have the feeling that my transaction did not get broadcasted. It was created, I can see it in BISQ, there is info in the log files. However, nobody seems to know the transaction. It was created with a fee of 201 sat/byte, so that should not be a problem. I have my own core node running, so BISQ should connect to that one. It usually does. Is there a way to resend the transaction? ---
**Author:** ![haenzl](https://bisq.community/letter_avatar/haenzl/32/5_5575768a8748004e209b776fc1b2916d.png) [@haenzl](https://bisq.community/u/haenzl)\ **Post date:** [January 15, 2018, 9:32pm UTC](https://bisq.community/t/btc-withdrawal-transaction-not-sent/4461/2 "2018-01-15T21:32:09Z")
Ok, here’s an update. I deleted the spv chain and did a resync. This caused the input to be freed again. Apparently nobody except Bisq new about the transaction. I created a new transaction. Used a different input for it, but the same happened. No transaction broadcast. Removed spv chain again, and again the transaction disappeared. I shut down my bitcoin core node, and created a new transaction. This one indeed was broadcasted to the network. So basically, some strange things happened, but I’m OK for now. ---
**Author:** ![cbeams](https://bisq.community/user_avatar/bisq.community/cbeams/32/3396_2.png) [@cbeams](https://bisq.community/u/cbeams)\ **Post date:** [January 19, 2018, 9:39am UTC](https://bisq.community/t/btc-withdrawal-transaction-not-sent/4461/3 "2018-01-19T09:39:49Z")
Thanks for the update @haenzi. @ManfredKarrer, this reminds me: I too had issues broadcasting a transaction from Bisq with my own full node running locally. I checked the log and saw bitcoinj reporting something to the effect of “We are waiting for 4 connections to broadcast… we currently have 1” and then the tx never broadcast. I haven’t had time to file anything about this, but I’m concerned our recent changes to thresholds, etc in v0.6.3 may have caused a situation where Bisq cannot broadcast txns at all against a local full node. Again, needs more investigation, but just quickly saying it here in case it rings a bell. ---
**Author:** ![cbeams](https://bisq.community/user_avatar/bisq.community/cbeams/32/3396_2.png) [@cbeams](https://bisq.community/u/cbeams)\ **Post date:** [January 19, 2018, 9:42am UTC](https://bisq.community/t/btc-withdrawal-transaction-not-sent/4461/4 "2018-01-19T09:42:26Z")
I just added [https://github.com/bisq-network/exchange/issues/1236](https://github.com/bisq-network/exchange/issues/1236) to track this. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [January 20, 2018, 12:48am UTC](https://bisq.community/t/btc-withdrawal-transaction-not-sent/4461/5 "2018-01-20T00:48:45Z")
Yes that is the core of the issue… > > > I have bitcoin core 0.15.1 running on my pc. The node was not fully synced so bi…sq instead of connecting to it was connecting to 165.227.34.56:8333. Only when my node synced fully bisq connected to it. > > I expected bisq would connect to my node 127.0.0.1:8333 or at least to a node via TOR but not 165.227.34.56. The "Bitcoin Network" tab was grayed out - I could not change any settings. > > > I just encountered a trade (id: \`TBTVBNKI\`) in which both taker and deposit fee …transactions failed to be broadacast to / propagate through the Bitcoin network. These transactions are not unconfirmed, but are rather \_non-existent\_ on any node (so far as we know) and certainly not via any block explorer, e.g. bitaps.com or tradeblock.com. > > !\[image.png\](https://images.zenhubusercontent.com/56f1d5436caf56c9d38e1e86/c7b88b8a-056e-4bd3-9ce5-c4d72e500ffc) > > I know @keo-bisq has had at least one other trade with these kind of tx broadcasts. Keo, let's use this issue to track these issues as they come up. Please add a comment for each one you encounter, and I'll do the same. Please ask everyone to attach their log file in a comment on this issue, too, so that @ManfredKarrer and I can analyze them.