-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Key Management and Config File for Validator Onboarding #1990
Key Management and Config File for Validator Onboarding #1990
Conversation
…ialization or test initialization
…eer_validators set other nodes' default pub key and stake value during initialization
…dator Config file for validator
Sishan/scripts gen keypair
…r_onboarding_after_pull
Sishan Long seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
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.
Nice, LGTM!
This reverts commit 0ca0a4f.
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.
Looks good to me !
@@ -54,12 +54,9 @@ impl BLSPrivKey { | |||
} | |||
} | |||
|
|||
#[allow(clippy::incorrect_partial_ord_impl_on_ord_type)] |
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.
I'm good with this as long as it still works as intended ! I wonder why we implemented it this way to begin with
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.
I'm also wondering about that. In the beginning the implementation on this was very long ago, and later implementation just follow that. There are more discussions on whether we want to keep this on zullip.
let config_file_as_string: String = fs::read_to_string(config_file.as_str()) | ||
.unwrap_or_else(|_| panic!("Could not read config file located at {config_file}")); | ||
let config_toml: NetworkConfigFile = | ||
toml::from_str::<NetworkConfigFile>(&config_file_as_string) | ||
let config_toml: NetworkConfigFile<TYPES::SignatureKey> = |
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.
This file is clean! Love it
This PR:
Designs:
config/ValidatorConfigExample
for reference), it would be better to generate it rather than read it from config file, and also ourHotshotConfig
does contain the secret key originally for signning, so it's fine.gen_launcher::<TestTypes, MemoryImpl>(0)
is to identifynode_id
for key pair (pk & sk) generation, sincebuild_system_handle()
incrates/testing/src/task_helpers.rs
needs launcher with different node id.Main review parts:
orchestrator/src/config.rs
,crates/types/src/lib.rs
.