Updating the list of public subnets to open up io67a

Governance NNS proposal discussions
1

A new proposal with id 134498 has been submitted.

Updating the list of authorized subnets to:

Subnet id Subnet Type Public Description
2fq7c-slacv-26cgz-vzbx2-2jrcs-5edph-i5s2j-tck77-c3rlz-iobzx-mqe Application false Subnet has more than 60000 canisters
3hhby-wmtmw-umt4t-7ieyg-bbiig-xiylg-sblrt-voxgt-bqckd-a75bf-rqe Application false Subnet has more than 300 GiB state size
4ecnw-byqwz-dtgss-ua2mh-pfvs7-c3lct-gtf4e-hnu75-j7eek-iifqm-sqe Application true
4zbus-z2bmt-ilreg-xakz4-6tyre-hsqj4-slb4g-zjwqo-snjcc-iqphi-3qe Verified Application true
5kdm2-62fc6-fwnja-hutkz-ycsnm-4z33i-woh43-4cenu-ev7mi-gii6t-4ae Verified Application false Other verified subnets opened up in this run
6pbhf-qzpdk-kuqbr-pklfa-5ehhf-jfjps-zsj6q-57nrl-kzhpd-mu7hc-vae Application false Subnet has more than 300 GiB state size
bkfrj-6k62g-dycql-7h53p-atvkj-zg4to-gaogh-netha-ptybj-ntsgw-rqe Application false Explicitly marked as non-public (European subnet)
brlsh-zidhj-3yy3e-6vqbz-7xnih-xeq2l-as5oc-g32c4-i5pdn-2wwof-oae Application true
csyj4-zmann-ys6ge-3kzi6-onexi-obayx-2fvak-zersm-euci4-6pslt-lae Verified Application false Other verified subnets opened up in this run
cv73p-6v7zi-u67oy-7jc3h-qspsz-g5lrj-4fn7k-xrax3-thek2-sl46v-jae Application true
e66qm-3cydn-nkf4i-ml4rb-4ro6o-srm5s-x5hwq-hnprz-3meqp-s7vks-5qe Application true
ejbmu-grnam-gk6ol-6irwa-htwoj-7ihfl-goimw-hlnvh-abms4-47v2e-zqe Verified Application false Other verified subnets opened up in this run
eq6en-6jqla-fbu5s-daskr-h6hx2-376n5-iqabl-qgrng-gfqmv-n3yjr-mqe Verified Application false Subnet has more than 60000 canisters
fuqsr-in2lc-zbcjj-ydmcw-pzq7h-4xm2z-pto4i-dcyee-5z4rz-x63ji-nae Application true
gmq5v-hbozq-uui6y-o55wc-ihop3-562wb-3qspg-nnijg-npqp5-he3cj-3ae Application true
io67a-2jmkw-zup3h-snbwi-g6a5n-rm5dn-b6png-lvdpl-nqnto-yih6l-gqe Verified Application false ⇒ true
jtdsg-3h6gi-hs7o5-z2soi-43w3z-soyl3-ajnp3-ekni5-sw553-5kw67-nqe Application true
k44fs-gm4pv-afozh-rs7zw-cg32n-u7xov-xqyx3-2pw5q-eucnu-cosd4-uqe Application false Subnet has more than 300 GiB state size
lhg73-sax6z-2zank-6oer2-575lz-zgbxx-ptudx-5korm-fy7we-kh4hl-pqe Application false Subnet has more than 300 GiB state size
lspz2-jx4pu-k3e7p-znm7j-q4yum-ork6e-6w4q6-pijwq-znehu-4jabe-kqe Application true
mpubz-g52jc-grhjo-5oze5-qcj74-sex34-omprz-ivnsm-qvvhr-rfzpv-vae Application true ⇒ false Subnet has more than 300 GiB state size
nl6hn-ja4yw-wvmpy-3z2jx-ymc34-pisx3-3cp5z-3oj4a-qzzny-jbsv3-4qe Application true ⇒ false Subnet has more than 300 GiB state size
o3ow2-2ipam-6fcjo-3j5vt-fzbge-2g7my-5fz2m-p4o2t-dwlc4-gt2q7-5ae Application true ⇒ false Subnet has more than 300 GiB state size
opn46-zyspe-hhmyp-4zu6u-7sbrh-dok77-m7dch-im62f-vyimr-a3n2c-4ae Application true ⇒ false Subnet has more than 300 GiB state size
pae4o-o6dxf-xki7q-ezclx-znyd6-fnk6w-vkv5z-5lfwh-xym2i-otrrw-fqe Verified Application false Other verified subnets opened up in this run
pjljw-kztyl-46ud4-ofrj6-nzkhm-3n4nt-wi3jt-ypmav-ijqkt-gjf66-uae Application true
pzp6e-ekpqk-3c5x7-2h6so-njoeq-mt45d-h3h6c-q3mxf-vpeq5-fk5o7-yae Application false Explicitly marked as non-public (Fiduciary subnet)
qdvhd-os4o2-zzrdw-xrcv4-gljou-eztdp-bj326-e6jgr-tkhuc-ql6v2-yqe Application true
qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae Verified Application false Other verified subnets opened up in this run
shefu-t3kr5-t5q3w-mqmdq-jabyv-vyvtf-cyyey-3kmo4-toyln-emubw-4qe Verified Application false Explicitly marked as non-public (Distrikt subnet cannot be public before migrating away from ICQC)
snjp4-xlbw4-mnbog-ddwy6-6ckfd-2w5a2-eipqo-7l436-pxqkh-l6fuv-vae Verified Application false Other verified subnets opened up in this run
tdb26-jop6k-aogll-7ltgs-eruif-6kk7m-qpktf-gdiqx-mxtrf-vb5e6-eqe System false System subnets should not have public access
uzr34-akd3s-xrdag-3ql62-ocgoh-ld2ao-tamcv-54e7j-krwgb-2gm4z-oqe System false System subnets should not have public access
w4asl-4nmyj-qnr7c-6cqq4-tkwmt-o26di-iupkq-vx4kt-asbrx-jzuxh-4ae Verified Application false Other verified subnets opened up in this run
w4rem-dv5e3-widiz-wbpea-kbttk-mnzfm-tzrc7-svcj3-kbxyb-zamch-hqe System false System subnets should not have public access
x33ed-h457x-bsgyx-oqxqf-6pzwv-wkhzr-rm2j3-npodi-purzm-n66cg-gae Application false Explicitly marked as non-public (SNS subnet)
yinp6-35cfo-wgcd2-oc4ty-2kqpf-t4dul-rfk33-fsq3r-mfmua-m2ngh-jqe Application false Subnet has more than 300 GiB state size
1 Like
2

Context

This proposal follows the plans that were outlined here (gradually opening up private subnets) →

Suggested approach to make more compute capacity available on the IC - Governance - Internet Computer Developer Forum

The previous proposal of this sort was this one → Proposal: 134334 - ICP Dashboard

Proposal 134498

I’ve voted to adopt. The proposal sets the io67a subnet to public (it’s currently private). This means anyone will be able to deploy to this subnet. It’s a small subnet with very few canisters and very little memory usage. Looks like a good candidate for making public.

There are also 4 subnets that are being made private with this proposal, due to passing the threshold of 300 GB in memory usage (this means canisters will not be able to be deployed to those subnets unless the principal is explicitly authorised by NNS proposal, or already has a canister in the subnet). These changes are detailed in the table below, followed by some questions.

Depending on the size of your screen, you may need to use the arrow keys to scroll right and see all columns of the table (after clicking on the table).

Subnet id Subnet Type Public Authorised Principals Last Changed Canisters Memory Usage Proposal Action and Claims
io67a Verified Application false true pr42y + EVERYONE 141 0.532 GB Subnet Type: Verified Application, Public: false ⇒ true
wyzjx + EVERYONE
xiwzc + EVERYONE
mpubz Application true false EVERYONE 2024-12-02 by 134334 54,985 317.019 GB Subnet Type: Application, Public: true ⇒ false, Subnet has more than 300 GiB state size
pr42y
nl6hn Application true false EVERYONE 2024-12-02 by 134334 31,252 316.527 GB Subnet Type: Application, Public: true ⇒ false, Subnet has more than 300 GiB state size
o3ow2 Application true false EVERYONE 2024-12-02 by 134334 56,244 516.721 GB Subnet Type: Application, Public: true ⇒ false, Subnet has more than 300 GiB state size
opn46 Application true false EVERYONE 2024-12-02 by 134334 39,501 366.461 GB Subnet Type: Application, Public: true ⇒ false, Subnet has more than 300 GiB state size
pr42y

@DRE-Team, after this proposal executes pr42y will have privileged deployment access to opn46 and mpubz (as illustrated in the table above). Is this intended, and can I ask who or what team this principal represents? (if this isn’t known, I would suggest the privilege should be removed)

Note that if io67a is made private again in the future, there will be three principals that will still retain priviledged deployment access (also illustrated in the table above).

3 Likes
3

@Lorimer Where can we find information on authorised principals? I couldn’t see it in ic-admin.

3 Likes
4

Hey @timk11, you can query the CMC (get_principals_authorized_to_create_canisters_to_subnets), and/or you can scan though proposal history and programatically reproduce the state from successfully executed proposals.

I do both to check for inconsistencies :slight_smile:

2 Likes
5

Thanks @Lorimer ! The CMC link is very handy. I’ll add that to my resource list.

For what it’s worth, pr42y shows up through a Google search as the sole controller of canister 2b2k4-rqaaa-aaaaa-qaatq-cai and another. This canister ID in turns appears in this piece of boundary node test code. Still a mystery, but it suggests a probable origin within Dfinity.

3 Likes
6

Voted to adopt proposal #134498.

Sets io67a from private to public. It has 544.61 MiB (0.571064975 GB) State and 138 Canisters.
image

image
image967×691 16.2 KB

The four ( mpubz, nl6hn, o3ow2, and opn46) subnets that will be set to private all have over 300 GB.

2 Likes
7

Voted to adopt proposal 134498. This proposal changes the status of 4 subnets from public to private and 1 subnet from private to public. The content of the proposal matches the payload and the reasoning as explained within the table is sound. As has been pointed out in this thread, principal pr42y may still have access to deploy canisters on two of the subnets being made private, but this could potentially be addressed separately.

2 Likes
8

Proposal 134498

Vote: ADOPT

The proposal updates the list of public subnets by making 4 subnets private due to having more than 300GiB state size which can be verified through the Dashboard and 1 subnet public with a state size of 544.67 MiB.

2 Likes