We currently don't provide any static list of beacons for any of the networks. This is a security risk, because all of the beacons are injected through the command line parameters. If an attacker manages to get someone to change the related command line parameters, he can put nodes on an alternative network that he controls.
By having a small set of nodes that are static and always used for bootstrapping, we can avoid this problem. Even with an invalid command line parameter, some of the nodes will be correct, and the node will at least be able to tell something strange is going on.
We currently don't provide any static list of beacons for any of the networks. This is a security risk, because all of the beacons are injected through the command line parameters. If an attacker manages to get someone to change the related command line parameters, he can put nodes on an alternative network that he controls.
By having a small set of nodes that are static and always used for bootstrapping, we can avoid this problem. Even with an invalid command line parameter, some of the nodes will be correct, and the node will at least be able to tell something strange is going on.