vetKeys production key and II subnet downtime

Developers
, ,
16

Proposal 137130 Review | Lorimer :infinity: :dog_face: - CO.DELTA △

VOTE: YES

TLDR: This proposal applied a CUP to the II subnet while it was halted. I’ve used the new tool to verify the specified CUP hash is correct and was produced by halting this subnet. Proposal 137130 also supplied the key material that was generated by Proposal 137075 on the Fiduciary subnet (the signing subnet). The II subnet acts as the backup subnet.

Note that the key isn’t enabled yet. This is scheduled for the Fiduciary subnet tomorrow based on the announcement here.

The last time key material was reshared to the II subnet was August last year, by Proposal 131510. Below is a diff of the payloads. Aside for changes in case for case insensitive fields, the CUP hash and height, we see the Bls12_381_G2:key_1 details are appended to the key config.

image
image1515×846 53 KB

We also see that the CUP hash matches the output from the verification tool, which also confirms the origin of the CUP.

Reading CUP file at "/ic/uzr34_cup.pb"
CUP integrity verified!

Checking CUP signature for subnet uzr34-akd3s-xrdag-3ql62-ocgoh-ld2ao-tamcv-54e7j-krwgb-2gm4z-oqe...
Getting registry value of key catch_up_package_contents_uzr34-akd3s-xrdag-3ql62-ocgoh-ld2ao-tamcv-54e7j-krwgb-2gm4z-oqe at version 51509...
CUP signature verification successful!

Latest subnet state according to CUP:
                TIME: 1750924730644446051, (2025-06-26 07:58:50.644446051 UTC)
              HEIGHT: 100596000
                HASH: e45b2b3f06469a1199487a582e7d5bd5076a917f46fcbf68656b6b55ad87f33f
    REGISTRY VERSION: 51509

Verifying that the subnet was halted on this CUP...
Getting registry value of key subnet_record_uzr34-akd3s-xrdag-3ql62-ocgoh-ld2ao-tamcv-54e7j-krwgb-2gm4z-oqe at version 51509...

Confirmed that subnet uzr34-akd3s-xrdag-3ql62-ocgoh-ld2ao-tamcv-54e7j-krwgb-2gm4z-oqe was halted on this CUP as of 2025-06-26 07:58:50.644446051 UTC.
This means that the CUP represents the latest state of the subnet while the subnet remains halted.
The subnet may ONLY be restarted via a recovery proposal using the same state hash as listed above.

Searching for a recovery proposal...
Getting registry value of key catch_up_package_contents_uzr34-akd3s-xrdag-3ql62-ocgoh-ld2ao-tamcv-54e7j-krwgb-2gm4z-oqe at version 51510...
Found Recovery proposal at version 51510:
                TIME: 1750924816209467626
              HEIGHT: 100597000
                HASH: e45b2b3f06469a1199487a582e7d5bd5076a917f46fcbf68656b6b55ad87f33f
Ensuring recovery time is greater than CUP time...
Success!
Ensuring recovery height is greater than CUP height...
Success!
Ensuring recovery state hash is equal to CUP state hash...
Success!
The subnet was correctly recovered without modifications to the state!

We also see that the specified recovery height is larger than the halting height. My understanding is that the exact amount is arbitrary (in this case 1000).

You may wish to follow the CO.DELTA known neuron if you found this analysis helpful.

CO.DELTA △

We’re a verifiably decentralised collective who review IC deltas (changes applied by NNS proposals). We follow a common code:

  • Look: We observe the details and context of NNS proposals
  • Test: We test and verify the claims made by those proposals
  • Automate: We automate as much as possible by building increasingly sophisticated tools that streamline and strengthen the reviewal process.

Every vote cast by CO.DELTA is the result of consensus among diligent, skilled and experienced team members acting independently. The CO.DELTA neuron follows the vote of D-QUORUM on NNS topics that the CO.DELTA team does not handle directly. You can therefore follow CO.DELTA on all topics and rely on the highest quality of vote.

3 Likes