fix(consensus): require validity threshold stake to reconstruct shards - #12651
Queued
VorobyevIlya wants to merge 1 commit into
Queued
fix(consensus): require validity threshold stake to reconstruct shards#12651VorobyevIlya wants to merge 1 commit into
VorobyevIlya wants to merge 1 commit into
Conversation
polinikita
approved these changes
Aug 12, 2026
VorobyevIlya
enabled auto-merge
August 13, 2026 12:00
filipdulic
approved these changes
Aug 19, 2026
VorobyevIlya
added this pull request to the merge queue
Aug 19, 2026
Any commits made after this event will not be merged.
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
4 participants
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.
Description of change
Shard reconstruction fired once
info_lengthshards were collected — a count threshold, while the fault model bounds Byzantine stake. That letinfo_lengthcolluding low-stake validators relay proof-valid shards for a fabricated commitment, wasting decode CPU and holding the reconstructed payload in memory until GC (it can never reach Core, since the header gate is keyed by the full commitment).Reconstruction now additionally requires the relayers' combined stake to reach the validity threshold (f+1). Byzantine stake is below that threshold, so every reconstruction includes an honest relayer and only genuinely authored commitments are ever decoded.
Links to any relevant issues
fixes iotaledger/iota-private#472
How the change has been tested