13

Command to add trusted nodes to config This is how I configure the node to use these "trusted nodes". I added the command to open up to 500 connections which can be left out of course: ./tezos-node config update \ --peer="dubnodes.tzbeta.net:9732" \ --peer="franodes.tzbeta.net:9732" \ --peer="sinnodes.tzbeta.net:9732" \ --peer="nrtnodes.tzbeta.net:9732" \ -...


6

Here is whats in my consig.json: "dubnodes.tzbeta.net ", "franodes.tzbeta.net ", "sinnodes.tzbeta.net" , " nrtnodes.tzbeta.net"


6

You should use as many peers as you can, for a more secure approach you can use a private node that connects to your public nodes instead. List with nodes: Tzscan Network Script to add peers: addPeers


3

Here is the full list given by the maintainer of the foundation nodes: dubnodes.tzbeta.net franodes.tzbeta.net sinnodes.tzbeta.net nrtnodes.tzbeta.net pdxnodes.tzbeta.net I use those mainly.


1

Behind the known DNS addresses are several individual IPs with the nodes. Therefore you should use dig (from package dnsutils on debian) to connect to all of them. When running a node in private mode, you also need to trust the address first. Also it might be a good idea to put these nodes into your default config. See the commented alternative line. ...


Only top voted, non community-wiki answers of a minimum length are eligible