Repository navigation
Detect protocol reparses with durable ledger checkpoints - #31
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
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 while retaining the same Bitcoin block hash. The indexer previously treated that checkpoint as unchanged, including after an interrupted block, leaving orphaned application rows in place.
Retain ledger and message hashes in completed and pending checkpoints, verify fixed block and parent identities before writes, and use protocol-verified ancestors for exact rollback. Ordinary new descendants remain valid. Missing protocol evidence stops replay without erasing state. Migration 0054 adds nullable checkpoint columns; the first successful pass establishes a baseline and does not claim evidence for older NULL rows.
Validation: real SQLite replay regressions for completed and interrupted reparses, messages-only changes, new descendant arrival, missing hashes and missing historical evidence. Full API tests, Worker/D1 migration tests, generated types, promise lint and TypeScript checks pass. Migration must precede deployment; the existing deployment workflow enforces that order.