I am very happy to see that the community was able to verify the recovery proposal!
Here’s the last proposal, 137151, to enable the vetKeys production key on the fiduciary subnet.
Proposal 137130 Review | Malith H - CO.DELTA △
VOTE: YES 
TLDR:
Reshares the vetKD master key (Bls12_381_G2:key_1) to subnet uzr34 by updating its recovery CUP. Second of three proposals.
Payload state Hash: e45b2b3f06469a1199487a582e7d5bd5076a917f46fcbf68656b6b55ad87f33f
Verification Summary (via CLI)
CUP timestamp: 2025-06-26 07:58:50 UTC
Recovery height: 100597000
Recovery hash matches CUP hash:
CLI verification log
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!
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.
2 Likes
Proposal 137131 Review | Malith H - CO.DELTA △
VOTE: YES
TLDR:
Unhalts subnet uzr34 to complete the resharing of the vetKD master key (Bls12_381_G2:key_1) from subnet pzp6e. Third and final proposal in the sequence. Forum post · Prev proposal
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.
2 Likes
Proposal 137151 Review | Lorimer 
- CO.DELTA △
VOTE: YES
TLDR: Enables the vetkeys production key on the signing subnet (Fiduciary). LGTM 
The last time a production key was enabled was proposal 132383. I’ve diffed the payloads below.
Aside from the omission of deprecated fields in the config, the only difference is the name of the key (bls12_381_g2), as we would expect.
Congratulations to all who have worked on this feature! The communication around scheduling and the various details has also been superb. Thank you @andrea
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.
2 Likes
Proposal 137123 – LaCosta | CodeGov
Vote: ADOPT
Inline with the steps for resharing the vetKD production key on subnet uzr34, a series of three proposals are necessary.
This first proposal halted the subnet at it’s next CUP (Catch up Package) height.
Proposal 137130 – LaCosta | CodeGov
Vote: ADOPT
Reshares the vetKD to subnet uzr34 by updating its recovery CUP.
Using the new tool to verify CUPs more on that can be found here, I verified that the subnet was restarted without any state changes.
Proposal 137131 – LaCosta | CodeGov
Vote: ADOPT
As the last step for resharing the vetKD production key on subnet uzr34, the subnet is unhalted to complete the key resharing.
Proposal 137151 – LaCosta | CodeGov
Vote: ADOPT
Enables the vetKD production key on subnet pzp6e
About CodeGov
CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron’s Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralization of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
Proposals 137123, 137130, 137131 & 137151 | Tim - CodeGov
Vote: Adopt
The first 3 proposals (now executed) follow on from proposal 137075 which generated the vetKD production key on subnet pzp6e.
Proposal 137123 halts subnet uzr34 at the next available CUP height using halt_at_cup_height:true in the proposal payload.
Proposal 137130 then shares the vetKD test key from subnet pzp6e to subnet uzr34 within its recovery catch-up package.
Proposal 137131 then unhalts subnet uzr34 (is_halted:false in the proposal payload). Using the instructions given here I was able to successfully verify the recovery CUP and the matching recovery proposal, as shown in this screenshot:
Proposal 137151 enables subnet pzp6e to use the vetKD production key.
Congratulations to the Dfinity Crypto team on reaching this huge milestone! 
@andrea @ais @JackLloyd @franzstefan @eichhorl @Sawchord @anyoneivemissed
About CodeGov
CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, API Boundary Node Management, Node Admin and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neurons’ Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralisation of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
1 Like
Enabling vetKeys for public canister use
Proposals
Vote:
137151 - ADOPT
Summary
Not sure what is going on with the casing of curve:"bls12_381_g2". Shouldn’t it be Bls12_381_G2?
Congratulations to Dfinity and specially the teams involved in shipping this milestone!
@andrea @ais @JackLloyd @franzstefan @eichhorl @Sawchord @anyoneivemissed
I can’t wait to use it myself.
Proposal 137123 & 137131 Review | aligatorr - CO.DELTA △
VOTE: YES
TLDR: Halt and unhalt proposals for II subnet.
- Nothing else was enforced with both propsals
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.
Proposal 137151 Review | aligatorr - CO.DELTA △
VOTE: YES
TLDR: Following successfull VetKey generation in 137075, this proposal will enable VetKey usage on the subnet Fiduciary.
- Enabled algo and key name match with previousely generated ones:
name "key_1", curve: "bls12_381_g2"
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.
1 Like
Proposal 137151 Review | Malith H - CO.DELTA △
VOTE: YES
TLDR:
As per last review and Proposal of generating Bls12_381_G2 key for subnet pzp6e. This proposal will enable its use in production.
Payload check:
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.
2 Likes