Repository navigation
fix: restore legacy mempool snapshots with certified hashes - #38
Merged
Merged
Conversation
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
1 participant
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.
v4.1.6 rejected the five-field
Size statsrecords emitted by current mainnet nodes. Acceptcertified_hashesalongsideuncommitted_txs, preserving count/list validation and oldest-uncommitted age.The regression fixture follows an observed mainnet record. Tests also reject malformed counts and verify metric publication and removal across all three supported schemas.
Validation: full shuffled Go suite and race tests, vet, staticcheck, govulncheck, generated docs, workflow and release-note checks, and Linux amd64/arm64 builds pass.