Repository navigation
test(rpc): verify retained state after body pruning - #824
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.
Historical contract queries must continue to use retained state after the corresponding transaction bodies expire. Add
--historical-pruned-bodiesto the existing lifecycle script: natural isolated wPoA production includes six signed transactions, expires the deployment and two storage-write bodies, then checks literal prior code, storage and nonce values before and after a persistent node reopen. Current state remains unchanged by the historical reads.CI reuses its existing node build and SDK installation. The RPC guide documents the single command, libp2p requirement and scaled retention settings.
Validation: the new mode passed with the public v0.27.7 macOS binary and shell-sdk@0.14.0-rc.2. JavaScript and the affected CI shell passed syntax checks. The initial development-mining fixture did not establish finality and therefore did not prune the bodies; the retained failure led to using natural production and finality, without weakening the body-absence assertions. Required hosted checks remain pending.
Scope: one authority, the existing creation-address profile, state retention 64 and body retention 1. Independent import, the default 4096-block window and expired state roots remain unverified by this case.