adkg: update logs#107
Merged
Merged
Conversation
CluEleSsUK
approved these changes
Sep 17, 2025
Contributor
CluEleSsUK
left a comment
There was a problem hiding this comment.
lgtm! The ultimate test is a ceremony though :p
AnomalRoil
approved these changes
Sep 18, 2025
5db133a to
5c8d6ab
Compare
Co-authored-by: AnomalRoil <AnomalRoil@users.noreply.github.com>
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 should allow us to get a good understanding of what happens if a node gets stuck during the ADKG with an info-level.
This gives us the following logs for n = 4, t = 1. Let me know what you guys think: