Cx receipt fixes main - #5101
Merged
Merged
Conversation
…taking quorum uniformVerifier.IsQuorumAchievedByMask compared the full committee size (len(mask.Publics)) against the threshold instead of counting bits actually set in the signer bitmap. An all-zero bitmap paired with an all-zero (identity) aggregate BLS signature therefore satisfied quorum for any pre-staking-epoch committee, since len(mask.Publics) always exceeds the threshold regardless of how many signers were enabled. Count enabled bits via mask.IndexEnabled and reject a nil mask outright. Add regression coverage: a mask-level table test for zero/below-threshold/ at-threshold/padding-bit bitmaps, and an engine-level test asserting that verifySignature rejects an empty pre-staking quorum end-to-end.
…kleProof IsSpent and WriteCXReceiptsProofSpent only derived the spent-marker key from the signed block.Header (ShardID/Number) from IsCXMerkleProofReplayFixEpoch onward. For any proof whose Header.Epoch() precedes that fork epoch, the key fell back to CXMerkleProof.ShardID/BlockNum -- fields that ValidateCXReceiptsProof never binds to the Header for those epochs. Since the Header (and therefore its signature) can't be altered without invalidating VerifyHeaderSignature, but MerkleProof.ShardID/BlockNum are otherwise unauthenticated, a genuine, already-applied CXReceiptsProof could be resubmitted with a mutated MerkleProof identity: each resubmission hashed to a different, "unspent" key, letting ApplyIncomingReceipt credit the destination again with no corresponding source debit. Always derive the spent-marker key from the Header. This doesn't change what ValidateCXReceiptsProof accepts, and is a no-op for honestly generated proofs -- MerkleProof.ShardID/BlockNum are naturally populated from the same source block as the Header, so the on-disk key is unchanged for real historical data; only a proof with a deliberately mismatched MerkleProof identity resolves to a different (correct) key than before. Add TestIsSpentIgnoresMutatedMerkleProofIdentity covering the replay case.
mur-me
approved these changes
Aug 12, 2026
|
Tick the box to add this pull request to the merge queue (same as
|
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
2 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.
Cx receipt fixes main