-
Notifications
You must be signed in to change notification settings - Fork 36
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
Decommission signer registration with declarative PoolId #653
Decommission signer registration with declarative PoolId #653
Conversation
b074d03
to
90061ff
Compare
@@ -252,7 +252,7 @@ impl KeyRegWrapper { | |||
if cfg!(not(feature = "allow_skip_signer_certification")) { | |||
Err(ProtocolRegistrationErrorWrapper::OpCertMissing)? | |||
} | |||
println!("WARNING: Uncertified signer regsitration by providing a Pool Id is deprecated and will be removed soon! (Pool Id: {:?})", party_id); | |||
println!("WARNING: Uncertified signer regsitration by providing a Pool Id is decommissionned and must be used for tests only! (Pool Id: {:?})", party_id); |
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.
Should we put this warning directly when the signers are initialised? So, rather than warn users only when they've tried to register, if they already run the node with the "allow_skip_signer_certification", then this warning should appear, saying they won't be able to register. WDYT?
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.
It's difficult to know that at signer initialization if the signer will be certified or not because the feature flag allow_skip_signer_certification
is applied to mithril-common
. But I agree with you that this could be a good option 🤔
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.
ah, good point. We could put the warning with StmInitializerWrapper::setup()
then. WDYT?
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.
Yes, I moved the warning in StmInitializerWrapper::setup()
in b83300e
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.
Changes look good. Just a minor comment on 'when' to notify the signer that their registration will not be successful except for testing.
In 'mithril-common' and 'mithril-end-to-end'.
90061ff
to
b00a5cc
Compare
Moved to 'StmInitializerWrapper::setup()' to warn earlier in the process.
To make all tests pass in signer registerer of aggregator. This is a temporary fix. This issue will be resolved in #663.
b83300e
to
fcd16bb
Compare
Avoid unwanted usage of features when building the artifacts from the workspace. Split in 2 phases: tooling first and then distribution.
fcd16bb
to
16cf8fe
Compare
Also remove the 'allow_skip_signer_certification' feature that was misused. Use directly 'mithril-stm' as dependency in this crate to retrieve protocol types.
Content
This PR decommissions the declarative
PoolId
signer registration mode. Once this PR is merged SPOs will be required to provide theirOperational Certificate
andKES Secret Key
to certify that they are the owner of aPoolId
.Pre-submit checklist
Issue(s)
Closes #621