-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
CapabilityRegistry updates #13183
CapabilityRegistry updates #13183
Conversation
…ount-DON-struct KS-204: Add config count to DON struct
… KS-199/update-node-signer-type
KS-128: Implement remove DONs in capability registry
… KS-199/update-node-signer-type
…gner-type KS-199: Update node signer type
…fy-DON-capability-registry KS-129: Implement modify DON
70ea5d9
to
be9ccf5
Compare
…ity-config-interface KS-179: Update ICapabilityConfiguration interface
… KS-197/add-getters-for-entities
Quality Gate passedIssues Measures |
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.
The title of the PR doesn't really match the contents - there's way more stuff here than just "encode packed" :)
struct DONCapabilityConfig { | ||
/// @notice The set of p2pIds of nodes that belong to this DON. A node (the same | ||
// p2pId) can belong to multiple DONs. | ||
EnumerableSet.Bytes32Set nodes; |
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.
The order here is not fixed. I wonder if this could cause any problems with OCR, where order of the nodes is important. I think OCR's config will just handle that but still a little concerned.
Fair fair, updated 🙂 |
No description provided.