Send transaction from Bitcoin Core wallet when config file has walletbroadcast=0

[curious droid]

Hi ! I use Bitcoin full node running trough Tor + Electrum with EPS
While setting up Bitcoin core config file i have set  walletbroadcast= to 0  as it says in this tutorial https://github.com/chris-belcher/electrum-personal-server/blob/master/README.md

"run tor on the same machine as Electrum Personal Server. Then by default transactions will be broadcast through tor. If running tor, also set walletbroadcast=0 in your bitcoin.conf. This prevents the node from rebroadcasting transactions without tor."

All works well, i receive transactions, but when i want to send a transaction from my Bitcoin core wallet ( not electrum) my transaction doesn't go trough, i get a message " unconfirmed, not in memory pool".
I googled and found out that if i set walletbroadcast= to 1 my transactions will go trough. I did so, transaction went thought, and even bitcoin core was still connected to only onion nodes.
My Questions are:
1. If even with walletbroadcast=1 i manage to connect to onion nodes, then what was the point of setting it to walletbroadcast=0 in the first place?
2. Do i compromise privacy when walletbroadcast is set to 0?
3. Is there a way sending transaction from Bitcoin core wallet with walletbroadcast=0 or i need to change it back and forth every time i want to send a transaction from bitcoin wallet.
Can someone please help me to understand how all this works?

[1715451416]

1715451416

[1715451416]

1715451416

[1715451416]

1715451416

[1715451416]

1715451416

[1715451416]

1715451416

[1715451416]

1715451416

[nc50lc]

I saw your post to the other thread and this thread has additional info explaining the situation better,
it seem like you have an active wallet in Bitcoin Core used by your Electrum Personal Server.

You need to disable that option as suggested by the tutorial since you're using Tor.
(if you'll still set it to '0') As a workaround when using sending transactions through Bitcoin Core, just copy the raw transaction of the non-broadcast transaction,
then send it using the command:

Code:

sendrawtransaction "RAW_TXN"

RAW_TXN = the copied raw transaction (a long string of characters in HEX)

If you're using the GUI: Go to "Transactions" tab, right-click the transaction, select "Copy raw transaction".
Go to Console (menu, "Window->Console") and type the command there.

[ranochigo]

You need to disable that option as suggested by the tutorial since you're using Tor.

I think the rationale behind that is to improve on the privacy of the node. The initial consideration appears to be preventing the wallet from automatically rebroadcast transactions. Since the privacy and the rebroadcast logic has been worked on and improved in the recent versions, would this still be necessary?

[nc50lc]

You need to disable that option as suggested by the tutorial since you're using Tor.

I think the rationale behind that is to improve on the privacy of the node. The initial consideration appears to be preventing the wallet from automatically rebroadcast transactions. Since the privacy and the rebroadcast logic has been worked on and improved in the recent versions, would this still be necessary?

When I think about it, I think it's unnecessary in his case since he's running Bitcoin Core through Tor (another info not included in his other post).
Even if he's using the wallet, if I understand the new PRs correctly, rebroadcast is now handled in his node's mempool in a manner that his wallet transactions aren't the only txns that'll be rebroadcast.

[ranochigo]

When I think about it, I think it's unnecessary in his case since he's running Bitcoin Core through Tor (another info not included in his other post).
Even if he's using the wallet, if I understand the new PRs correctly, rebroadcast is now handled in his node's mempool in a manner that his wallet transactions aren't the only txns that'll be rebroadcast.

Yeah. 0.21.0

EPS was modified to broadcast the transaction directly to the peers within Tor and I remember that this was implemented quite a long time ago. I'm not sure what are the justifications, if any that would still hold water. If the user is running Core on Tor, then using the EPS would achieve the same privacy with running Core on Tor alone. Since its dependent on Core anyways.

[curious droid]

The reason of using Core (+ Tor) and Electrum with EPS is to be able to use Trezor.
Trezor just alone doesnt worj with Core, but it can be used with Electrum, hence i have this setup
Core+Tor+Electrum+EPS+Trezor

[curious droid]

Thank you all for helping, it all works for me now.

[HCP]

Trezor just alone doesnt worj with Core, but it can be used with Electrum, hence i have this setup

Thank you all for helping, it all works for me now.

I know you now have a setup that is working for you, but just for the record... you can actually use Hardware Wallets directly with Bitcoin Core... you need to use the HWI python module: https://github.com/bitcoin-core/HWI

Supported devices here: https://hwi.readthedocs.io/en/latest/devices/index.html#support-matrix

And a step by step showing Bitcoin Core + Trezor usage here: https://hwi.readthedocs.io/en/latest/examples/walkthrough/walkthrough.html

[curious droid]

Wow, you just opened up a whole new world for me
Nowhere online i have seen alternative option to use Treazor with Core.
Even on Trezor’s wiki page it talks only about running trezor local instance or Electrup+EPS in case if one whants to be independent from satoshi labs, bypassing their servers.
It took me a lot of time to figure out my current setup with Electrum and EPS, but option to directly use Trezor with core sounds exciting, and i think less complicated, less components in the way thus it will be kind of more
Robust on privacy.
I will now try too figure out this setup.

Tha k you a lot for revealing this to me.