DynamicPeerValidationConfig controls what sui-node & sui-bridge binaries that are functioning as a validator that we’ll speak with.
Peer in this case is peers within the consensus committee, for each epoch. This membership is determined dynamically
for each epoch via json-rpc calls to a full node.
StaticPeerValidationConfig, unlike the DynamicPeerValidationConfig, is not determined dynamically from rpc
calls. It instead searches a local directory for pub keys that we will add to an allow list.
StaticPubKey holds a human friendly name, ip and the key file for the pub key
if you don’t have a valid public routable ip, use an ip from 169.254.0.0/16.