Hello! Here is a quick update from the DFINITY team. As we are progressing in our integration of threshold key derivation (aka the vetKeys feature) into the Internet Computer Protocol, we also made some minor adaptions to the expected vetKD API (see this commit). In particular:
-
the IC method
vetkd_encrypted_keywas renamed tovetkd_derive_encrypted_keyto better express the action that is done (key derivation) and to be more in line with names likesign_with_schnorrandsign_with_ecdsa. -
the argument field
public_key_derivation_pathwas renamed topublic_key, so that both derivation path arguments (one per API) have the same name -
the
key_id’s curve was renamed frombls12_381tobls12_381_g2to be more precise, more future-proof, and to make it obvious that the master public key is in group G2
The various vetKD-related examples all have been updated accordingly (see examples/pull/1087). The chainkey-testing-canister was updated as well, (see chainkey-testing-canister/pull/9) and it was re-deployed.