Add privacy as CODEOWNER for confidentialrelay paths in core#22762
Merged
Conversation
confidentialrelay holds the relay-DON authorization logic (PRIV-433, PRIV-458), which is privacy-owned security code. It currently inherits /core/capabilities/ (keystone + capabilities-team) with no privacy entry. Add privacy alongside the existing owners so privacy can review and approve changes there, e.g. #22516 and #22703.
Contributor
|
Thank you for adding a CODEOWNERS file - @nadahalli. |
Contributor
|
👋 nadahalli, 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
|
✅ No conflicts with other open PRs targeting |
Both confidentialrelay paths are purely privacy's confidential-relay code: the capability handler (core/capabilities/confidentialrelay) and the gateway handler (core/services/gateway/handlers/confidentialrelay). Assign both to @smartcontractkit/privacy outright, mirroring confidentialhttp in chainlink-common.
MStreet3
approved these changes
Jun 9, 2026
justinkaseman
approved these changes
Jun 9, 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
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.
The confidentialrelay code (relay-DON authorization logic, PRIV-433, PRIV-458) is privacy-owned security code spread across three paths, none of which had a privacy CODEOWNERS entry:
Privacy could not approve changes there as a code owner (e.g. #22516, #22703). This adds @smartcontractkit/privacy for all three.
Note: GitHub only honors these entries if the @smartcontractkit/privacy team has write access to this repo. https://smartcontract-it.atlassian.net/servicedesk/customer/portal/4/SECHD-31726