fix(verify): latest.json may carry the publisher's activation bundle - #48
Merged
Merged
Conversation
The publisher now writes its replay-from-anchor bundle into latest.json as data.activation. The verifier required an exact key set on the latest data block, so every ./reproduce run refused the live pointer with 'unexpected [activation]' once the new publisher went live. The reader contract admits the bundle present, absent, or null. This verifier recomputes values from receipts and calc_params and does not consume the bundle, so it is admitted as an opaque object and nothing inside it is interpreted. A non-object bundle and any other unexpected key still refuse. Verified: ./reproduce h100, h200, b300 and b200 for 2026-09-02 from a clean checkout against the public record: 96 MATCH, 0 MISMATCH each (all four refused before this change). Signed-off-by: hobbyistz <293619914+hobbyistz@users.noreply.github.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.
Summary
The publisher now writes its replay-from-anchor bundle into
latest.jsonasdata.activation. This verifier required an exact key set on the latest data block, so every./reproducerun refused the live pointer withunexpected ['activation']once the new publisher went live on 2026-09-03.The reader contract admits the bundle present, absent, or null. This verifier recomputes values from receipts and
calc_paramsand does not consume the bundle, so it is admitted as an opaque object and nothing inside it is interpreted. A non-object bundle and any other unexpected key still refuse (tested).Verification
./reproduce h100 2026-09-02,h200,b300,b200from a clean checkout with its own venv against the public record: 96 MATCH, 0 MISMATCH, 0 degraded each. All four refused before this change.ruff checkclean; DCO sign-off present.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.