Search content
Sort by

Showing 4 of 4 results by bittyuser
Post
Topic
Board Bitcoin Technical Support
Re: Running Bitcoin core node without Tor.
by
bittyuser
on 30/09/2024, 10:32:35 UTC
Btw how to avoid Tor for faster download? Do I need to comment out the network portion of my bitcoin.conf and stop tor.service from running? I really wanna get this download faster.
It isn't the issue but if you really want to test, you can add these to your bitcoin.conf file or use as command line arg:
Code:
onlynet=ipv4
onlynet=ipv6
listenonion=0
"onlynet=ipv4" and "onlynet=ipv6" limits your node's outbound connection to those networks, and..
"listenonion=0" disables inbound connections via Tor.

Of course, don't forget to restart Bitcoin Core after changing the settings for it to apply.

This is how my bitcoin.conf looks like:
Code:
# Network
onlynet=ipv4
# onlynet-ipv6
listen=1
listenonion=0
#proxy=127.0.0.1:9050
#bind=127.0.0.1

# Raspberry Pi optimizations
maxconnections=40
maxuploadtarget=5000

# Initial block download optimizations
dbcache=2000
blocksonly=1

I observer the downloads and verification is slightly better. Also I stopped tor.service. Not sure if that played a part.
Post
Topic
Board Bitcoin Technical Support
Re: Running Bitcoin core node without Tor.
by
bittyuser
on 29/09/2024, 23:00:34 UTC
I am using a 1TB Samsung T7 external SSD and tested the SSD and got about 350 mb/s. The SSD is connected to the blue USB port in the pi 4. Btw I am using Bullseye as per the guide. Apparently tried with Bookworm and there were permission issues that I couldn't resolve.
You can run into an issue, when your SSD demands too much power from the Raspi 4B. A Raspi 4B can only provide a total power budget of 1.2A@5V (or 6W) for all its USB ports combined! Not exactly sure about the Samsung T7, it will mostly work but maybe can overwhelm the Raspi.

With only 4GB of RAM you will later in IBD run into I/O intense periods when chainstate grows way larger than 4GB and you can't give sufficient RAM to dbcache (see below).

The OS shouldn't be much of a factor here.


From an own full IBD experiment started somewhere in June 2023 with an Umbrel node that only ran a Bitcoin Core container via Tor on a Raspi 4B with 8GB RAM and a 1TB SATA SSD connected with an USB3-to-SATA adapter with UASP properly activated and working, I experienced a full IBD within about 95h until full sync with onlynet=onion, onlynet=i2p basically (I also had a dbcache=4883 in my bitcoin.conf file).

Your IBD will be slower as you can't reserve much more than maybe 2 or 2.5GB to dbcache. During IBD you may consider to set blocksonly=1 to avoid having to verify possibly incoming transactions.

If anyone is interested, I can provide snips from the debug.log that I preserved.

Yup I have dbcache=2000 and blocksonly=1. Btw how to avoid Tor for faster download? Do I need to comment out the network portion of my bitcoin.conf and stop tor.service from running? I really wanna get this download faster.
Post
Topic
Board Bitcoin Technical Support
Re: Running Bitcoin core node without Tor.
by
bittyuser
on 29/09/2024, 14:22:31 UTC
Hey, there. I'm running a Raspibolt node.

Tor is very rarely the problem with slow syncing. It's either failing to find peers, or there is lack of memory. But before that, is your external drive an HDD? If that's so, then expect slow syncing. When I finished syncing a couple of years ago, I think it had taken me around 2 weeks, because of that. So, maybe you should shut down everything, move your blocks and chainstate in an SSD, let it sync there, and then move these directories back to your HDD drive. 

Hey man thanks for replying. I am using a 1TB Samsung T7 external SSD and tested the SSD and got about 350 mb/s. The SSD is connected to the blue USB port in the pi 4. Btw I am using Bullseye as per the guide. Apparently tried with Bookworm and there were permission issues that I couldn't resolve.
Post
Topic
Board Bitcoin Technical Support
Merits 6 from 2 users
Topic OP
Running Bitcoin core node without Tor.
by
bittyuser
on 29/09/2024, 12:07:38 UTC
⭐ Merited by BlackHatCoiner (4) ,ABCbits (2)
Hello new to the forum but not to bitcoin.

Setup my bitcoin node using the raspibolt guide (https://raspibolt.org/guide/raspberry-pi/) . Apparently it is taking so long to download. Now the verification progress is at 0.4. I was thinking the slow download is due to running thru TOR.

I am running the node on a Raspberry Pi 4B which is the 4gig ram version. I am running Pi Hole along with the node.

Anyway to speed up the download?

The idea is to run the node and setup my private electrum server so that I could use it with sparrow desktop wallet.

Also please share what's the best practice when running a node?