RSS Logo

by Mountaineerbr

#33 - Podcast #6 - More Tor Configs for Bitcoin Node and SSH

Comentando sobre mais algumas configurações que fiz depois de gravar o último podcast sobre bitcoind. Pretendemos dominar as configurações necessárias para poder retransmitir dados para as redes clearnet e onion do bitcoin.

Também falo sobre uma experiência curta colhendo soja em uma empresa privada, montando um servidorzinho em casa, usar acesso SSH em casa e mais.

Main Topic - More Tor, Router and Bitcoind Configuration

There are some more important tweaks to improve connectivity of bitcoind that I did not talk about in the last audiocast episode. That is because I learned more stuff after that recording which I reckon is worth telling my audiocast listeners and subscribers on YouTube.

I will go through some more configs and comment on them. Basically, we want to build a node which can help synchronisation between clearnet and onion networks.

Also, some more configs are needed to make your IPv4 and IPv6 addresses available to other nodes, so they can connect to your node. When properly configured, the node can listen to requests and listen to inbound connections to rebroadcast mempool transactions, transaction index, blocks, IP and Onion addresses, and so on..

Personally, I use my bitcoin node for retrieving some transaction info and mempool info. I don't use that software as a wallet and my node does not do mining (obviously).

Ultimately, we will make our node available only at the onioin network and keep it synchronised. If there is a need to broadcast own transactions or to help the networks, it is easy to change configs and start listening to other nodes instead of just receiving data.

It is up to the user to choose what configs to set in order to run the node the way he wishes. My public dotfiles have got all options set to run on IPv4, IPv6 and Onion networks.

Secondary Topics



During the podcast, I messed up inbound and outbound connection names.. Outbound connections are connections your node initiates whereas inbound connections are initiated by other nodes when connecting to yours.

PS: Following Tone's advice of using fees no lower than 5 sat/vB, I set my sweep transaction fees to 6.1 and 6.2 sat/vB and within 24 hours they were included in the blockchain during the weekend! Finally, those sweeps are done.. Remember, I have been trying to sweep these wallets with very low fees for almost 4 weeks now..