test: Strengthen pure Pluto DKG runner validation#467
Merged
Conversation
varex83
approved these changes
Jun 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR improves the existing pure Pluto DKG runner coverage.
The runner now explicitly verifies the expected validator count in the generated artifacts, making the semantic validation stricter and less implicit. It also allows pure-Pluto runs to execute without requiring Charon to be installed when no Charon nodes are configured.
Additionally, the DKG runner documentation and CI job naming were clarified so the pure Pluto 4-node threshold-3 flow is easier to identify and run locally.
Checklist