Repository navigation
Verify protocol history across replay and interrupted recovery - #35
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.
Counterparty can reparse protocol state without changing the Bitcoin block hash. Replay previously compared only that Bitcoin hash, so it could retain orphaned mutable state while reporting caught up.
Verify the stored ledger and message hashes as well as Bitcoin hashes, including the completed predecessor of a partial block. Persist each slice's protocol identities before writes and retain them across cursor commits/restarts. Capture a fixed parsed source anchor before fetching events and recheck it before writes; a new descendant does not invalidate it. Confirmed reparses use exact undo with a protocol-verified ancestor. Missing evidence stops replay without resetting application state.
No new migration is needed. Existing completed block hashes provide history; future slice identities use core_state. Historical incomplete blocks are not retroactively certified.
Validation: full API suite and repository checks; real SQLite regressions for completed/interrupted reparses, messages-only changes, fixed anchors during normal tip growth, missing evidence, and compact/verbose parity.