Voted to adopt proposal #134334.
So while this proposal makes sense and it is so called “in line” with “adding additional application subnets” and it follows proposal# 132409 , I find the addition of the “Subnet Type” column in the summary very much appreciated, I still think that verifying this proposal is a bit complicated for new ppl.
Simply put:
- using the IC Dashboard one can check for eg subnet 4zbus the TYPE (Application), number of Canisters(103) and State size(1.82 MiB).
- a quick search for “subnet info” takes us to using just ic-admin
~$ ./ic-admin --nns-url=https://ic0.app get-subnet 4zbus-z2bmt-ilreg-xakz4-6tyre-hsqj4-slb4g-zjwqo-snjcc-iqphi-3qe
gives quite a detailed list of info including in our example"subnet_type": "verified_application"
- while actually using
$ dre update-authorized-subnets
does recreatepropose-to-set-authorized-subnetworks
to update the list including the payload so we can reproduce the proposal (ofc using dry-run and such should be known).
Anywho the TLDR of my rambling is including a short info/description on how to check/verify would be useful to have in the summary for future proposals, IMHO.
BTW the addition of 349c2a5 is great, really like that there is a check on how many VerifiedApplication
subnets can pass.
Other thoughts:
- side note about “District”
https://nuance.xyz/oif/11630-434go-diaaa-aaaaf-qakwq-cai/distrikt-update-connections
They will be fine