1
When configuring the bitcoin.conf file, what should you put in connect=? There are IP addresses listed here, so I removed the # sign and left them as is. I also entered my WAN address and my local IP address with the forwarded port a separate time. What should I enter and how will I know it is working correctly?
2Trusted nodes only. This is one more security precaution for payment gateways and apps that deal with significant funds but also for everyone who wants to make sure they won't establish a p2p connection with a malicious node. It could become a problem if your trusted nodes aren't available at times, though. – George Kimionis – 2014-04-20T22:37:32.927
Where does one verify which nodes are trusted and which not? Should I remove the # sign and enter my WAN and local IP, or should I leave the defaults? Sorry, I realize that my intermediate command line and tcp/ip knowledge may make this question look ridiculous, but I just wanted to confirm. Thanks, oemb1905. – oemb1905 – 2014-04-20T22:43:42.153
Think should help: https://en.bitcoin.it/wiki/Fallback_Nodes
– George Kimionis – 2014-04-20T22:50:29.937That was helpful. However, how come the defaults then are not listed on the trusted nodes wiki? The default lists 69.164.218.197 and 10.0.0.2:8333 ... whose nodes are those? – oemb1905 – 2014-04-20T22:58:21.797
1
69.164.218.197was the address of an old bitcoin Faucet that doesn't exist anymore but back then it was a highly active node due to its nature and now only serves as a configuration example. – George Kimionis – 2014-04-20T23:04:26.353So then I should replace that entry with one of the nodes listed on the page you referred me to? – oemb1905 – 2014-04-20T23:07:36.607
2No, if you have just started getting familiar with the protocol you shouldn't be adding them manually, leave this for a bit later on when you will be able to define your own
trusted nodeslist. In a totally trust-less network it's all about who YOU trust and not who you "should" trust. – George Kimionis – 2014-04-20T23:16:16.630