feat(capabilities): add DONByID registry lookup + vault zone-b gates#2256
Merged
Conversation
Add DONByID(ctx, donID) to core.CapabilitiesRegistryMetadata (interface, Unimplemented stub, LOOP gRPC client/server, regenerated proto/pb, mock) so a node can authoritatively resolve any DON's Families by ID. Add cresettings gates for the vault zone-b GetSecrets restriction: - VaultZoneBWorkflowGetSecretsRestrictEnabled (global master gate, default false) - PerOwner.VaultZoneBGetSecretsAllowed (owner-scoped allowlist, default false) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
👋 prashantkumar1982, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
Contributor
|
prashantkumar1982
marked this pull request as draft
July 16, 2026 02:47
prashantkumar1982
marked this pull request as ready for review
July 16, 2026 03:10
cedric-cordenier
approved these changes
Jul 16, 2026
russell-stern
approved these changes
Jul 16, 2026
jmank88
approved these changes
Jul 16, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
Foundational chainlink-common changes for the vault zone-b GetSecrets restriction.
DONByID(ctx, donID)added tocore.CapabilitiesRegistryMetadata(interface,Unimplementedstub, LOOP gRPC client/server, regenerated proto/pb, mockery mock). Lets a node authoritatively resolve any DON'sFamiliesfrom its registry ID — unlikeDONsForCapability, which never returns a caller/workflow DON.VaultZoneBWorkflowGetSecretsRestrictEnabled— global master gate, defaultfalse.PerOwner.VaultZoneBGetSecretsAllowed— owner-scoped allowlist, defaultfalse(deny).Why
The vault capability (in chainlink) needs to authoritatively determine the calling workflow DON's zone from its own registry view, rather than trusting caller-supplied zone data. The chainlink-side consumer is a separate PR.
https://smartcontract-it.atlassian.net/browse/PRIV-593