feat(crypto): CRP-2646 use dedicated AlgorithmID for vetKD #3997
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
If this pull request affects the behavior of any canister owned by
the Governance team, remember to update the corresponding
unreleased_changes.md file(s).
To acknowldge this reminder (and unblock the PR), dismiss this
code review by going to the bottom of the pull request page, and
supply one of the following reasons:
-
Done.
-
No canister behavior changes.
There was a problem hiding this comment.
If this pull request affects the behavior of any canister owned by
the Governance team, remember to update the corresponding
unreleased_changes.md file(s).
To acknowldge this reminder (and unblock the PR), dismiss this
code review by going to the bottom of the pull request page, and
supply one of the following reasons:
-
Done.
-
No canister behavior changes.
github-actions
bot
added
@consensus
@crypto-team
@execution
@nns-team
@ic-interface-owners
labels
fspreiss
dismissed
github-actions[bot]’s stale review
No canister behavior changes.
…etKD (#4064) Since #3997 we use a dedicated AlgorithmID for vetKD. However, the PR missed to use this algorithm ID also in batch delivery, which led to the long running system test `//rs/tests/consensus/vetkd:vetkd_key_life_cycle_test` getting broken (see #4060). This PR fixes this by using `AlgorithmID::VetKD` also in batch delivery.
Uses a dedicated AlgorithmID for vetKD.