@bit-stacker@goraelec
There’s an issue that has bee causing an error when broadcasting transactions. In this case, it seems that the make offer transaction wasn’t successfully broadcast but the Bisq Network still accepted it as a valid offer.
My log entries include:
fee 0.0000815 BTC for 813 bytes (10 Satoshi/Byte)
which looks reasonable (about $0.81 USD)
I see the onion stuff and peer messaging going on. There is an entry:
Sep-22 14:02:25.383 [JavaFX Application Thread] INFO o.b.c.TransactionBroadcast: broadcastTransaction: We have 9 peers, adding 2642b5e520bd407d2385bf6a60f8d7492a0ad76d5333959a73ba215bde390b8a to the memory pool
but the transaction is still not there.
I am on latest 1.1.6 - could this be a problem? Would it help if I upload the log file?
@bit-stacker, yes I’d suggest sharing the bisq.log file on the Github issue you’ve created.
Meanwhile, if you’re connecting to your local host or a custom node it may be worth trying the default and connection to the default BTC nodes. Also, try to turn off your VPN if you have one on, it may be causing issues.
I updated the issue 3305 with the log section. Hopefully it can shed some light. I was using the default and not running my own node. No VPN involved. Thanks again.
Hi @huey - would you recommend I delete all Bisq files, reinstall and recreate my wallet from seed words and date? Would that make Bisq forget about the unbroadcast transaction?
I think I have the same problem but a resync didn’t help. Two transactions from a multisig security deposit do not show up in the blockchain. the btc seems to be in my bisq wallet but when i try to withdraw transaction does not show on blockchain either.