Unstable libp2p Peer IDs #7
Comments
ulope
added a commit
that referenced
this issue
Aug 23, 2024
Certain values that are stored in the Keyper config file are generated during first run and are not available in the environment. Previously these were lost on restart with `docker compose up`. This now preserves it. Fixes #7
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When nodes are restarted with
uptheir 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
upto 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.The text was updated successfully, but these errors were encountered: