Skip to content

feat: Add invariant check for rental subnets#8776

Open
dsarlis wants to merge 2 commits intodfinity:masterfrom
dsarlis:dimitris/invariant-rental-subnets
Open

feat: Add invariant check for rental subnets#8776
dsarlis wants to merge 2 commits intodfinity:masterfrom
dsarlis:dimitris/invariant-rental-subnets

Conversation

@dsarlis
Copy link
Contributor

@dsarlis dsarlis commented Feb 10, 2026

This PR adds an invariant for the subnet record in the registry regarding rental subnets, specifically a check is added that only application subnets can be rented, i.e. have a "free" cycles cost schedule.

@dsarlis dsarlis requested a review from a team as a code owner February 10, 2026 15:25
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pull request changes code owned by the Governance team. Therefore, make sure that
you have considered the following (for Governance-owned code):

  1. Update unreleased_changelog.md (if there are behavior changes, even if they are
    non-breaking).

  2. Are there BREAKING changes?

  3. Is a data migration needed?

  4. Security review?

How to Satisfy This Automatic Review

  1. Go to the bottom of the pull request page.

  2. Look for where it says this bot is requesting changes.

  3. Click the three dots to the right.

  4. Select "Dismiss review".

  5. In the text entry box, respond to each of the numbered items in the previous
    section, declare one of the following:

  • Done.

  • $REASON_WHY_NO_NEED. E.g. for unreleased_changelog.md, "No
    canister behavior changes.", or for item 2, "Existing APIs
    behave as before.".

Brief Guide to "Externally Visible" Changes

"Externally visible behavior change" is very often due to some NEW canister API.

Changes to EXISTING APIs are more likely to be "breaking".

If these changes are breaking, make sure that clients know how to migrate, how to
maintain their continuity of operations.

If your changes are behind a feature flag, then, do NOT add entrie(s) to
unreleased_changelog.md in this PR! But rather, add entrie(s) later, in the PR
that enables these changes in production.

Reference(s)

For a more comprehensive checklist, see here.

GOVERNANCE_CHECKLIST_REMINDER_DEDUP

@dsarlis
Copy link
Contributor Author

dsarlis commented Feb 10, 2026

This is a code hardening change and it should hold in the current registry state. Therefore, there are no breaking changes by adding it as the check should succeed.

@basvandijk basvandijk added the security-review-passed IDX or InfraSec have concluded it's safe to run CI on the external PR. label Feb 10, 2026
@github-actions
Copy link
Contributor

@github-actions
Copy link
Contributor

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

Labels

external-contributor feat @governance-team security-review-passed IDX or InfraSec have concluded it's safe to run CI on the external PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants