chore(pin): move to core-candidate-2026.08.05.3 - #2
Merged
Merged
Conversation
The previous pin contains a defect that REMORA's end-to-end vertical test found after .2 was cut: the "spec changed between assess and dispatch" refusal ran AFTER the authorizing transaction, so a call that was never allowed to happen still left a dispatch intent behind. Harmless only because an unclaimed intent provably never ran, which is a thin thing for this product to rely on. Verified before pinning: verify_core_pin.py against the published release (6 artifacts, all hashes match), then the compatibility suite against the wheel installed from those verified assets — 43 passed.
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.
The previous pin (
.2) contains a defect REMORA's end-to-end vertical test found after that release was cut: the "spec changed between assess and dispatch" refusal ran after the authorizing transaction, so a call that was never allowed to happen still left a dispatch intent behind. Harmless only because an unclaimed intent provably never ran — a thin thing for this product to rely on.Verified before pinning, not after:
The compatibility suite ran against the wheel installed from the verified assets. Only the wheel digest, tag and commit change; the contract artifacts are byte-identical to
.2.