pull down to refresh
234 sats \ 1 reply \ @emmanuelrosa 1 Jan \ on: How long to get peers over Tor? bitcoin
Try seeding with this list: https://github.com/emmanuelrosa/bitcoin-onion-nodes
This was the super helpful, thank you! What I wound up doing:
- get the list of Tor nodes in a text file
- write a perl script to pick a random one every few seconds and attempt to connect it via bitcoin-cli
- when I get to my desired number of connections, sleep for a minute
This has loaded me up w/ Tor peers, as many as I want, and to keep the connection level where I want it. A lot of those nodes described in that repo are dead, so there's a lot of chaff in there, but enough are still good to make bootstrapping possible. So mission accomplished on that front.
A weird result is that, when I stop the node nicely (w/
bitcoin-cli stop) and then restart it, the peers don't re-load! Not sure wtf is going on there, peers.dat is supposed to save these, I thought. But maybe not for Tor? Or maybe it's using some behind-the-scenes algorithm and only saves them when they've been around long enough, and my testing scenario doesn't trigger it. I could figure this out I'm sure, but don't care enough atm.Whatever, at least I can solve the Tor problem. Thanks for this suggestion :) Now on to other (VPN) problems :/
reply