-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Use DKG package in vault reporting plugin #19160
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
Merged
Merged
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
This was referenced Sep 1, 2025
… into PRIV-149-p256-key
… into PRIV-149-p256-key
|
prashantkumar1982
approved these changes
Sep 8, 2025
cedric-cordenier
approved these changes
Sep 8, 2025
This was referenced Sep 8, 2025
cedric-cordenier
pushed a commit
that referenced
this pull request
Oct 16, 2025
* Add dkgresult database * add p256 key to keystore * tests * Use Use DKG package in vault reporting plugin * Add dkgresult database * make gomodtidy * fix merge conflicts * make generate * fix lint / possible overflow error * fix lint * update test package * Update to use new keyring * make gomodtidy * make gomodtidy * make generate * remove local replace, remove redundant orm * Only ensure DKG recipient key if it is configured * remove ensurekey * add more tests * fix lint * changeset * gomodtidy * bump smdkg, libocr * Use smdkg updates in plugin & test * bump chainlink-common, make generate * Add more config updates * fix test expected error log. * changeset * fix lint * fix config docs * fix tests * fix chainlink-common import * Enable dkg recipient key for CRE E2E tests * fix panic * fix lint, add more tests * ensure key for test env * temp: always ensure key * fix keystore test panic * fix config default behavior * make gomodtidy * bump cdf * add override to other configs * update go mod
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.




This PR:
EnableDKGRecipientconfiguration to the chainlink node to optionally enable the use of the DKG recipient key.EnableDKGRecipientconfiguration & theDKGRecipientKeyensured by the node, such that the E2E CRE suite is able to start the vault capability job that now requires theDKGRecipientKey.Related:
#19162
#19161
smartcontractkit/chainlink-common#1508