BSQ transaction not confirming

#1

I opened a trade to sell BSQ for BTC. Someone accepted and I proceeded to sent the BSQ to their address. After 10 hours this transaction is still not confirmed. TX 4eec1d818b827fda9eea40427de8f0339eb67fa65a574ecb52447eceabaa7f48

Does anybody know how to proceed? In the BSQ explorer I still cannot see it…

Thanks!

#2

Do you notice the fees which were used for this tx ?

#3

It is a BSQ transaction and Bisq doesn’t allow to fix fees. The program just says “Unverified BSQ transaction”

#4

BSQ is a colored BTC, and is entirely managed on bitcoin’s blockchain.
In Settings/Preferences, you can fix the fees.
For my part, I systematically put 5 sat/bytes more than the proposed fees. To avoid the spikes which happen from time to time with BTC mining fees.

#5

OK thanks. How do I find the BTC transaction that corresponds to my BSQ transaction? So I can send more fees…

#6

The BSQ tx ID is the same as BTC tx ID, so you can lookup at any blockexplorer as well.
If the tx is not confrimed in about 1 day, make a backup of all and resync the spv chain file. Then the tx is removed from the wallet and you can send it again. Check first in Settings if fee is either set automatically or set to a reasonable value. https://whatthefee.io/ is a good resource.

1 Like
#7

Hi Manfred, thanks. I did so and found the BSQ as you describe it here. I then redid the transaction with 65 sat/byte to avoid any issues but after one hour it still says “Unverified” like the old one. For reference:

https://explorer.bisq.network/tx.html?tx=c2533d3c4dfe889f3cfef5d707ada70925c47370e052ae26353b41ad01fc13ff

In a bitcoin explorer does not show anything. It doesn’t find it. I don’t know how to act now. I feel bad for my counter party who is waiting for these BSQ.

#8

I had lately also a delayed BSQ transaction (instant buy with BTC; Bisq 1.1.1).
The conformation of the BSQ transaction took 7 hours.
Consequences: Extra workload for the Arbitrator and sleep deficit for me.

#9

Can you PM me the log file? There is a know issue with dust output, might be the same here.

#10

I just sent you the file. Tell me if you didn’t get it…

#11

It could be an issue with dust output as I am leaving 0.07 BSQ as change. Is there something I could do? The other party is still waiting. Thanks

#12

Yes its the dust issue. but in ht elog there is not the tx details, was in an older log. could u search in the other log files fo 616f83db7a5fe5c495e025219f0dcf85e5f68e3bad9d446ce6a5b659fcf2c5c8 and post me the t details. it will be the full print of the tx details iwth all inputs and outputs, then we see what is the dust amout and i can tell u how to fix that. its a bug in the app that it does not cehck for dust outputs and will be fixed soon

#13

Signed Tx:
616f83db7a5fe5c495e025219f0dcf85e5f68e3bad9d446ce6a5b659fcf2c5c8
in PUSHDATA(71)[304402200c6d0bd60eeb0c3dd10e20ed50c224c1ae75ba9e2e9d39fd4a65508b841937a2022069a0910114f798c3bedcc975b2c0c8f57b72e931f641adb64403f3d8fb554a6e01] PUSHDATA(33)[029a1be94a479b6f8dbbc3a046d140c3213ea3cec85fd4097f9e27680718d2a590] 0.00005007 BTC (5007)
outpoint:93a5d59ea44266c7827378362f00b7e4cfba595cd742b7e9444e2a959134303e:0 hash160:466f5675a1e14049564042a8f3bda2c380e91bbb
in PUSHDATA(71)[304402207c911e1d27ff73709d1315188eb02780572c6b2c0056ebc21f21727258abf51602207d6236ee91f50efea3019f5fd9ccc3f2920613703b4e41b85fd797153748960901] PUSHDATA(33)[0335e4ce9322b5f2c01c8aeee5ae3a81eb5776bd68fb62db8e406ed5f0171281db] 0.01994509 BTC (1994509)
outpoint:93a5d59ea44266c7827378362f00b7e4cfba595cd742b7e9444e2a959134303e:2 hash160:71311f0f068ad4142d1f1ae6097745bf386175e3
out DUP HASH160 PUSHDATA(20)[74840d18c0fd5974c09c96dd65d52fded9ffe8fa] EQUALVERIFY CHECKSIG 0.00005 BTC (5000) ScriptPubKey: 76a91474840d18c0fd5974c09c96dd65d52fded9ffe8fa88ac Address:1Bd5aL1PrvKuSgadFwP8mdNkUNCaHQ9YJJ
out DUP HASH160 PUSHDATA(20)[482e96f6f61a6f01fa82aca87825455234f6121a] EQUALVERIFY CHECKSIG 0.00000007 BTC (7) ScriptPubKey: 76a914482e96f6f61a6f01fa82aca87825455234f6121a88ac Address:17afTvSG1wDTVCoBNQusQZ2cFHkd2AL7UR
out DUP HASH160 PUSHDATA(20)[f7eb9b851b0fc72c5a3013e8b9a9b2b9fc00abb4] EQUALVERIFY CHECKSIG 0.01972099 BTC (1972099) ScriptPubKey: 76a914f7eb9b851b0fc72c5a3013e8b9a9b2b9fc00abb488ac Address:1Pbt9gLRpskX92dCCVunEaQqhdf1vxBzks
fee 0.0002241 BTC for 406 bytes (55 Satoshi/Byte)
prps USER_PAYMENT

may.-07 09:59:47.493 [JavaFX Application Thread] INFO o.b.w.Wallet: commitTx of 616f83db7a5fe5c495e025219f0dcf85e5f68e3bad9d446ce6a5b659fcf2c5c8
may.-07 09:59:47.493 [JavaFX Application Thread] INFO o.b.w.Wallet: marked 93a5d59ea44266c7827378362f00b7e4cfba595cd742b7e9444e2a959134303e:0 as spent by 616f83db7a5fe5c495e025219f0dcf85e5f68e3bad9d446ce6a5b659fcf2c5c8
may.-07 09:59:47.493 [JavaFX Application Thread] INFO o.b.w.Wallet: marked 93a5d59ea44266c7827378362f00b7e4cfba595cd742b7e9444e2a959134303e:2 as spent by 616f83db7a5fe5c495e025219f0dcf85e5f68e3bad9d446ce6a5b659fcf2c5c8
may.-07 09:59:47.493 [JavaFX Application Thread] INFO o.b.w.Wallet: 93a5d59ea44266c7827378362f00b7e4cfba595cd742b7e9444e2a959134303e prevtx <-unspent ->spent
may.-07 09:59:47.493 [JavaFX Application Thread] INFO o.b.w.Wallet: ->pending: 616f83db7a5fe5c495e025219f0dcf85e5f68e3bad9d446ce6a5b659fcf2c5c8
may.-07 09:59:47.494 [JavaFX Application Thread] INFO o.b.w.Wallet: Estimated balance is now: 0.02222599 BTC
may.-07 09:59:47.494 [JavaFX Application Thread] INFO o.b.w.WalletFiles: Saving wallet; last seen block is height 574959, date 2019-05-07T07:58:47Z, hash 0000000000000000000c8bc926297a06d4ed7073c22d959e843a64950b3b0fab
may.-07 09:59:47.508 [JavaFX Application Thread] INFO o.b.w.WalletFiles: Save completed in 13.94 ms
may.-07 09:59:47.508 [JavaFX Application Thread] INFO o.b.w.Wallet: commitTx of 616f83db7a5fe5c495e025219f0dcf85e5f68e3bad9d446ce6a5b659fcf2c5c8
may.-07 09:59:47.508 [JavaFX Application Thread] INFO o.b.w.Wallet: marked 93a5d59ea44266c7827378362f00b7e4cfba595cd742b7e9444e2a959134303e:0 as spent by 616f83db7a5fe5c495e025219f0dcf85e5f68e3bad9d446ce6a5b659fcf2c5c8
may.-07 09:59:47.509 [JavaFX Application Thread] INFO o.b.w.Wallet: 93a5d59ea44266c7827378362f00b7e4cfba595cd742b7e9444e2a959134303e prevtx <-unspent ->spent
may.-07 09:59:47.509 [JavaFX Application Thread] INFO o.b.w.Wallet: marked 93a5d59ea44266c7827378362f00b7e4cfba595cd742b7e9444e2a959134303e:2 as spent by 616f83db7a5fe5c495e025219f0dcf85e5f68e3bad9d446ce6a5b659fcf2c5c8
may.-07 09:59:47.509 [JavaFX Application Thread] INFO o.b.w.Wallet: ->pending: 616f83db7a5fe5c495e025219f0dcf85e5f68e3bad9d446ce6a5b659fcf2c5c8
may.-07 09:59:47.509 [JavaFX Application Thread] INFO o.b.w.Wallet: Estimated balance is now: 0.00000007 BTC
may.-07 09:59:47.509 [JavaFX Application Thread] INFO o.b.w.WalletFiles: Saving wallet; last seen block is height 574959, date 2019-05-07T07:58:47Z, hash 0000000000000000000c8bc926297a06d4ed7073c22d959e843a64950b3b0fab
may.-07 09:59:47.518 [JavaFX Application Thread] INFO o.b.w.WalletFiles: Save completed in 8.904 ms

#14

I send the full log to you via PM

#15

Ok, the second output is 7 satoshi so its dust and therefore not forwarded by nodes.
Please send 50.07 BSQ instead of 50 then there is no change output creating dust.
It is a known issue in the app and need to be fixed to not create dust.

#16

I thought that the minimum fees in the appli was 10 satoshis.
So I guess that using less is only possible with the user doing it voluntarily (?).

Withdrawn with Low Fee (3 sat/b)
#17

Thanks, it worked. I informed the arbitrator. Hopefully he is still with us and can unlock the funds!
If you need more information, log files, etc. to provide the patch feel free to ask! Great product in any case

What is a bit strange is my BSQ wallet now. Should I do anything?
Captura

#18

Such state is usual when all tx are not completely confirmed/finished.
Waiting a bit is generally enough.

#19

Actually the transactions were confirmed. What produced this was to produce the transactions which were not executed due to the dust problem, deleting the spv wallet sync, resyncing again. This 0.28 that you see is 0.07 dust x 4 transactions that were not executed. It is probably an error in a local database and not a real “unconfirmed change output”