Skip to content

Conversation

@kpop-dfinity
Copy link
Contributor

@kpop-dfinity kpop-dfinity commented Jan 30, 2026

During subnet splitting, when replicas detect that

Implement the logic of subnet splitting CUP share creation, validation, and aggregation.

CUP shares creation

When a replica detects that a "subnet splitting" block (denoted by a new field, subnet-splitting-status in the DkgSummary struct) has been finalized and the state at the block's height has been committed, it will create a CUP in the following way:

  1. Create a new summary block, on the fly, at the next CUP height, with dkg transcript taken from the registry;
  2. Create a dummy random beacon at the next CUP height,
  3. Check if node belongs to the high threshold committee, based on the transcript from the newly created summary block, if not, return None,
  4. Create a CUP, with the block and random beacon created in steps 1. and 2., respectively, and sign it using the key material from the block.

CUP shares validation

CUP shares aggregation

@kpop-dfinity kpop-dfinity added the CI_ALL_BAZEL_TARGETS Runs all bazel targets and uploads them to S3 label Jan 30, 2026
@github-actions github-actions bot added the feat label Jan 30, 2026
@kpop-dfinity kpop-dfinity changed the title feat(subnet-splitting): splitting cup share making/validating/aggregating feat(consenus):[CON-1565] splitting cup share making/validating/aggregating Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI_ALL_BAZEL_TARGETS Runs all bazel targets and uploads them to S3 feat

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant