Say that catch-up is proven live, and say what still is not - #31
Merged
Merged
Conversation
An induced six-block gap was repaired against the production node: the deposit and the spend were both in blocks the subscriber never received, and the alarm fired from the refetch. Two runs put 68,000+ real mainnet transactions through the parser with nothing malformed. The README claim that the block path had 'run only against fixtures' was therefore false, and it is a public claim, so it goes first. The more useful half of this change is the list of what is still not proven, kept in the same place: reorg handling is detected-and-refused rather than repaired and cannot be induced to order; the sockets have been watched live without a single drop, which says nothing about a period that does drop; and the proof authenticated with the node's cookie, which bypasses rpcwhitelist, so whitelist compatibility rests on inspection rather than a live run. A status section that only accumulates good news stops being read. Refs #24 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Chain catch-up now has a result against the production node (#24), so two documents were saying something false.
What changed in fact
An induced six-block gap, repaired. The deposit and its spend were both in blocks the subscriber never received, and the alarm fired from the refetch — which is the entire claim reconciliation makes. Across two runs, 68,000+ real mainnet transactions went through the parser with none malformed; until that point it had only ever seen its own synthetic fixtures.
The README said the block path had "run only against fixtures". That is a public claim, and it was false the moment the run finished, so it goes first.
The more useful half
The same sections now say what is still not proven, in the same place a reader finds the good news:
rpcwhitelist. Compatibility was checked by inspection instead: every method the code calls appears in the configured line. Sound for a per-method list, but inspection is not a live run and should not be written as one.A status section that only accumulates good news stops being read, and the point of having one is that someone picking this up can tell what is load-bearing from what is aspiration.
Checks
Documentation only. 194 tests, ruff clean.
Refs #24
🤖 Generated with Claude Code