Skalman set keys proof with rt proof of possession function #17
Conversation
This file contains hidden or 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
…ech#9949) # Description This is an amendment to paritytech#1739 to use the newly developed ProofOfPossessionGenerator/Verifier API instead of using `sign` and `verify` in order to generate and validate key ownership proofs. This is necessary because BLS keys need more complicated proofs which are not possible to be produced using `sign`. From the specification point of view, this PR only adds a context prefix of "POP_" to the ownership statement, otherwise its behaviour is identical to paritytech#1739.
…polkadot-sdk into skalman--set-keys-proof-with-rt-proof-of-possession-function
…paritytech#10002) To solve the CI Build errors in the implementation of `generate_session_key for the following runtimes: - cumulus/parachains/runtimes/testing/yet-another-parachain - cumulus/polkadot-omni-node/lib/src/fake_runtime_api - substrate/frame/revive/dev-node/runtime
…ttps://github.com/paritytech/polkadot-sdk into skalman--set-keys-proof-with-rt-proof-of-possession-function
ownership proof
…untime/src/traits/mod.rs`
…sync ad asset-hub-westend
…aritytech#10033) Also update `/cumulus/pallets/collator-selection/` to actually generate proof when setting keys.
…polkadot-sdk into skalman--set-keys-proof-with-rt-proof-of-possession-function
…lman--set-keys-proof-with-rt-proof-of-possession-function
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
✄ -----------------------------------------------------------------------------
Thank you for your Pull Request! 🙏 Please make sure it follows the contribution guidelines outlined in this
document and fill out the
sections below. Once you're ready to submit your PR for review, please delete this section and leave only the text under
the "Description" heading.
Description
A concise description of what your PR is doing, and what potential issue it is solving. Use Github semantic
linking
to link the PR to an issue that must be closed once this is merged.
Integration
In depth notes about how this PR should be integrated by downstream projects. This part is
mandatory, and should be reviewed by reviewers, if the PR does NOT have the
R0-no-crate-publish-requiredlabel. In case of aR0-no-crate-publish-required, it can beignored.
Review Notes
In depth notes about the implementation details of your PR. This should be the main guide for reviewers to
understand your approach and effectively review it. If too long, use
<details>.Imagine that someone who is depending on the old code wants to integrate your new code and the only information that
they get is this section. It helps to include example usage and default value here, with a
diffcode-block to showpossibly integration.
Include your leftover TODOs, if any, here.
Checklist
Trequired)You can remove the "Checklist" section once all have been checked. Thank you for your contribution!
✄ -----------------------------------------------------------------------------