feat: add cli option for root private key in bridge #1030
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
njgheorghita
force-pushed
the
bridge-private-key
branch
from
12e34b8 to
de54b43
Compare
njgheorghita
force-pushed
the
bridge-private-key
branch
from
de54b43 to
4830aa1
Compare
KolbyML
approved these changes
Nov 23, 2023
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was wrong?
In our bridge architecture, we spin up multiple bridge nodes, but their private keys are currently randomly generated. We want the option to provide custom private keys so that we can ensure the bridge nodes are equally distributed around the keyspace.
How was it fixed?
To-Do