Keysets [DRAFT] #11
Draft
Keysets [DRAFT] #11
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
|
PASS [ 43.831s] (3/3) lit_node::test toxiproxy::perf_tests::load_with_no_latency |
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.
WHAT
Allows for keyset functionality ( multiple concurrent sets of root keys ) 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.