CRUST has a bootstrap cache, like skypes host cache. So nodes should never use the hard coded endpoints except on first time after downloading. Even then they can be given endpoints from a friend.
There is a better approach. Nodes are given genesis information (they know the original genesis of netwokr/sections). So they can check the section they connect to (again) can prove cryptographically the network has moved forward from thei last known point. So like a blockchain/linked list signed by the Elders of the section they know if that makes sense. So you know key ABC as the last known section authority, the network nodes can give you the current key in the list signed by the last known elders you knew. AS they sign via consensus then you can be sure you have connected to the correct section and network.
Clients also, but they have the added, can I see my data and friends on this network, view.
Partitions
We have not decided fully on true partitions, e.g. 50% then both sides would stall (at the moment) until they seen at least >2/3 reconnecting. So in a partition we currently forsake liveness at least in terms of network mutations, reads (Gets) are fine though.