Skip to content

chore: Drop SystemMetadata::full_topology#10411

Draft
alin-at-dfinity wants to merge 1 commit into
stschnei/no-cycles-or-unbounded-xnet-on-enginesfrom
alin/drop-full_topology
Draft

chore: Drop SystemMetadata::full_topology#10411
alin-at-dfinity wants to merge 1 commit into
stschnei/no-cycles-or-unbounded-xnet-on-enginesfrom
alin/drop-full_topology

Conversation

@alin-at-dfinity

Copy link
Copy Markdown
Contributor

Since now all subnets (including engines) always "see" each other, there is no need for a separate full_topology to be certified by the NNS. We can fall back on the regular topology and drop full_topology altogether.

This is to only be merged into master once #10215 has been deployed, to avoid any forward compatibility issues (rolling back from a replica without full_topology to one depending on full_topology would break delegations).

Since now all subnets (including engines) always see each other, there is no need for a separate full_topology to be certified by the NNS. We can fall back on the regular topology and drop full_topology altogether.
@alin-at-dfinity alin-at-dfinity requested a review from a team as a code owner June 8, 2026 12:06
@github-actions github-actions Bot added the chore label Jun 8, 2026
@alin-at-dfinity alin-at-dfinity marked this pull request as draft June 8, 2026 12:06
@schneiderstefan

Copy link
Copy Markdown
Contributor

I don't think you can just drop it like that because of upgrades and downgrades. I initially thought about including this in my PR, but it's a bit trickier. During downgrades, the old version would expect the full topology to still be there. During upgrades, you also want to load the full topology still, otherwise you have no full topology in the first round after the upgrade.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants