Keysets Master [DRAFT] #11
Draft
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.
NOTE
This is a long running feature branch that receives regular updates from
master. This is the primary feature that allows for keyset functionality ( multiple concurrent sets of root keys, that are unrelated to each other ) within the nodes.Pull Request Overview
This PR implements threshold enforcement for keysets by introducing a keyset-based architecture that replaces the previous single root key approach. The changes enable the system to support multiple keysets with configurable thresholds, curve types, and realm associations.
Key changes:
See linear project : https://linear.app/litprotocol/project/keysets-56c26d54587f/overview
MISC
INCOMPATIBILITIES
Check LibStakingStorage - this does not match develop at the moment.
Must re-enable upgrade test against develop or some ansible target.