Keeping Your Full Node Safe and Private

7 replies 188 views
its_bridgeFull Member
Posts: 3 · Reputation: 793
#1Feb 19, 2018, 09:23 AM
Full nodes do all the heavy lifting by verifying transactions and blocks. But to do this right, they need to run the consensus rules, manage the UTXO set, and gossip across the network. To keep everything trustworthy, you gotta have solid disk performance, enough memory for the mempool, and reliable bandwidth to sync up with everyone. The infrastructure of the node is what really keeps the network strong, working as a minimalistic design.
3 Reply Quote Share
j0hn.ga5Newbie
Posts: 36 · Reputation: 19
#2Feb 19, 2018, 11:50 AM
Most of the time, privacy issues are super simple to fix. Like if you leave your RPC open, forget to close default ports, or even run your node on the same computer where you browse random stuff. Using Tor or I2P for P2P traffic can help hide your home IP and beat cheap surveillance, but basic security is still key. Only bind RPC to localhost, don’t run bitcoind as root, keep your OS patched, and set up a firewall to only allow what you want.
2 Reply Quote Share
gang2015Member
Posts: 269 · Reputation: 62
#3Feb 19, 2018, 10:25 PM
1. Not sure why you think disk performance and memory relate to trusting the Bitcoin network. Other nodes don’t even see what specs you have. 2. What's 'trusted bandwidth' supposed to mean?
3 Reply Quote Share
0xNodeMember
Posts: 307 · Reputation: 80
#4Feb 20, 2018, 10:07 AM
Honestly, eclipse attacks aren’t my biggest worry. By 2021, Bitcoin Core had already put fixes in place for most known weaknesses. Plus, tracking your IP doesn’t guarantee you’re the first node to share a transaction or block.
2 Reply Quote Share
gang2015Member
Posts: 269 · Reputation: 62
#5Feb 20, 2018, 12:45 PM
Yeah, but if you left that public RPC server running, people could snoop on your node easily. They can run commands like getblockchaininfo or getnetworkinfo to check out your system’s resource usage.
3 Reply Quote Share
its_bridgeFull Member
Posts: 3 · Reputation: 793
#6Feb 21, 2018, 01:23 AM
Totally agree. Last I checked, Bitcoin Core doesn’t even turn on RPC server by default. And if it’s enabled, it only listens to localhost. So any breaches are really due to bad setups by the node owners.
4 Reply Quote Share
0xNodeMember
Posts: 307 · Reputation: 80
#7Feb 22, 2018, 12:32 AM
You got it. Trust in the Bitcoin network and disk performance don’t really link up directly. But when you run a full node, which is the user’s choice, it’s all about independence and trustlessness, which does need good disk performance and memory.
2 Reply Quote Share
gang2015Member
Posts: 269 · Reputation: 62
#8Feb 22, 2018, 06:28 AM
You could encrypt node communication using SSL, but it doesn’t work for the P2P port since it’s unencrypted by design. A better option is setting up a node for Tor only, which has its own encryption. Same goes for i2p and other traffic layers.
4 Reply Quote Share

Related topics