-
Notifications
You must be signed in to change notification settings - Fork 536
Provide multi addresses instead of p2p peer ids to the manifest file #1272
Provide multi addresses instead of p2p peer ids to the manifest file #1272
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will the multiaddr be output by the polybft-secrets
command?
Nope, it just prints out P2P node id. The thing is that AFAIK, we don't keep IP addresses and ports inside secrets, but only P2P node IDs, so we are not able to reconstruct the entire multiaddress. |
Ok, so it's the user that should build the multiaddr format for feeding the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Yes, that is correct. 👍 |
Updated README on my end: fa743f1 |
Description
This PR changes the way we are expecting validators' network parameters to be specified when creating the manifest file. Prior to this, when specifying validators via CLI flags, only P2P peer id was expected, and then when genesis configuration was generated multi-address was assuming the local host IP address.
Now manifest generation expects entire multi-address to be provided if case genesis validators are being specified via CLI flag. Otherwise, if secrets are provided on local file storage, multi addresses are being constructed with localhost IP addresses.
Changes include
Breaking changes
Please complete this section if any breaking changes have been made, otherwise delete it
Checklist
Testing
Manual tests
Please complete this section if you ran manual tests for this functionality, otherwise delete it
Documentation update
Please link the documentation update PR in this section if it's present, otherwise delete it
Additional comments
Please post additional comments in this section if you have them, otherwise delete it