I just did a test where I was able to synchronize 500 blocks per minute from my #tor hidden service #Monero RPC. So even leaving your wallet closed for 10 days is going to require 15 minutes to catch up.
Discussion
AFAIK the latest block are much more heavier to compute than very old blocks, so bandwidth is not a bottleneck in the most cases. Am I right?
I'll be honest, I'm not totally sure. Newer blocks are going to be heavier, just because they have more transactions in them.
It's a bandwith issue. Just check your CPU usage while the wallet catches up, you'll see that's not the issue.
Nope, it's definitely not because if I synchronize it over the clear net, it's super fast. But synchronizing it over the hidden service is not. So that tells me it's not a CPU issue. It's definitely bandwidth.
Latest blocks are “a lot heavier” because not all nodes online have synchronized that blocks. So you will have a lower number of sources. Isn’t this the point?
The point was that it takes a lot longer to synchronize blocks using a hidden service than it does over the clear net. I knew it would take longer, but I did not realize how much longer it would take.
I was thinking about this some more and it's definitely a bandwidth limitation because if I synchronize over the clear net it goes much much faster so clearly compute is not the bottleneck it's bandwidth.
It’s amazing how quick it can be
I mean, I guess that's not bad for using a hidden service, but doing it over the clear net is way the hell faster than that.
do you know of a guide to make a monero node accessible over tor (for my own purposes only)
You can make the wallet RPC service available. And I think you can get the Monero node itself to synchronize, but you cannot participate in incoming transactions over tor from what I understand. I think Seth for privacy has a guide, but I didn't actually use it. I just kind of did it myself.