Unstable libp2p Peer IDs #7
Description
When nodes are restarted with up their libp2p peer id changes.
The reason is that the compose stack contains a service to generate the keyper config file.
This is re-run on every up to ensure config changes are consistently applied.
Unfortunately this doesn't take into account that the peer id is generated as part of the config file generation.
The probably easiest solution is to make the configuration script (scripts/configure_keyper.sh) check for an existing config and re-use the peer id / node key from that.