Skip to content

chore: add support for sev-enabled subnets in the registry#9038

Open
r-birkner wants to merge 8 commits intomasterfrom
rjb/sev-enabled-subnet-registry
Open

chore: add support for sev-enabled subnets in the registry#9038
r-birkner wants to merge 8 commits intomasterfrom
rjb/sev-enabled-subnet-registry

Conversation

@r-birkner
Copy link
Contributor

@r-birkner r-birkner commented Feb 24, 2026

This PR makes the registry ready for fully sev-enabled subnets:

  1. it relaxes the checks on the sev_enabled feature of a subnet. While previously it could only be set at subnet creation, now it can be also set on existing subnets. However, an SEV-enabled subnet can never be "disabled".
  2. it adds invariant checks making sure that an SEV-enabled subnet only consists of SEV-enabled nodes. SEV-enabled nodes are designated by the chip ID in their node record.

@github-actions github-actions bot added the chore label Feb 24, 2026
@r-birkner r-birkner force-pushed the rjb/sev-enabled-subnet-registry branch from db35515 to e10098b Compare February 25, 2026 07:06
@r-birkner r-birkner force-pushed the rjb/sev-enabled-subnet-registry branch from e10098b to 7589699 Compare February 25, 2026 09:30
@r-birkner r-birkner marked this pull request as ready for review February 25, 2026 20:30
@r-birkner r-birkner requested a review from a team as a code owner February 25, 2026 20:30
github-actions[bot]

This comment was marked as resolved.

@r-birkner r-birkner dismissed github-actions[bot]’s stale review February 26, 2026 09:40
  1. Update unreleased_changelog.md

Done!

  1. Are there BREAKING changes?

No

  1. Is a data migration needed?

No

  1. Security review?

No

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants