vetKeys production key and II subnet downtime

Developers
, ,
12

The second proposal (out of three) for the backup of the vetKeys production key on subnet uzr34 is 137131. This proposal replaces the recovery CUP in the registry, and reshares all the production threshold keys to subnet uzr34, including the vetKD key Bls12_381_G2:key_1.

As described in this forum post, the following instructions may be used to verify the subnet’s latest CUP and the recovery proposal:

  1. Checkout the current replica version of uzr34

git clone https://github.com/dfinity/ic.git

cd ic

git checkout 035f978fb5cffaef57f73242e1bb2a56423e84c3
  1. Download or copy the latest CUP of subnet uzr34 (download link) into the ic directory, i.e. using the following command:

curl -L -o uzr34_cup.pb "https://drive.google.com/uc?export=download&id=1_nZ6NS1LnZ6bFJXjqSZQ2HkGN_VMy5Hq"
  1. Enter the development container:

ci/container/container-run.sh
  1. Build and run the CUP verification tool:

bazel run //rs/cup_explorer:cup_explorer_bin -- verify-cup-of-halted-subnet --cup-path /ic/uzr34_cup.pb
  1. The output should include the following message:

"Confirmed that subnet uzr34 was halted on this CUP."

"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."
3 Likes