-
Notifications
You must be signed in to change notification settings - Fork 12
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
Separate Stake and Stake Pool keys #495
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.
splendid
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 really like this change. In some places the variable names were not updated to match the new type, I marked these with suggestions. I got into it and by the time I realized how spammy this could be on GH I was nearly done already, sorry about that. If you prefer I could make these fixes myself and push on your branch.
toolkit/mainchain-follower/db-sync-follower/src/candidates/mod.rs
Outdated
Show resolved
Hide resolved
toolkit/mainchain-follower/db-sync-follower/src/candidates/mod.rs
Outdated
Show resolved
Hide resolved
toolkit/primitives/session-validator-management/query/src/tests/mock.rs
Outdated
Show resolved
Hide resolved
toolkit/primitives/session-validator-management/query/src/tests/mod.rs
Outdated
Show resolved
Hide resolved
toolkit/primitives/session-validator-management/query/src/tests/runtime_api_mock.rs
Show resolved
Hide resolved
toolkit/primitives/session-validator-management/query/src/types/registrations.rs
Outdated
Show resolved
Hide resolved
I haven't mostly changed variables names. Perhaps some could be changed, but I am not going to break any existing interface that has been released (v1.5.0 or earlier) for sake of matching them. No CLI params changes. No JSON fields name changes. No extrinsic calls changes. |
Not even with an alias, preserving compatibility, like I suggested? |
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.
🎉
58f7c93
to
0b84113
Compare
Description
Separates StakePoolPublicKey and StakePublicKey and their respective signatures into separate types.
Before there was just MainchainPublicKey, but I argue that Stake key and StakePool key are two different things in the domain, used for different activities.
Please let me know what you think
This PR doesn't separate their hashes, it still is MainchainKeyHash.
Checklist
changelog.md
for affected crate