Revert #107 (enforce single-node proof verification)#117
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.
Why
PR #107 (
fix(payment): enforce single-node proof verification) is no longerfeasible and is being walked back from the
rc-2026.5.4release candidate,alongside the earlier reverts of #111/#114 (see #116).
Change
bece788) — reverts the single-node payment-verificationchanges in
src/payment/verifier.rs(−636/+88).Verification
cargo checkpasses.cargo clippy --all-targets --all-features -- -D warningspasses.Note
#107 was merged to
mainbefore this rc branch was cut, so this revert removesit from the RC only —
mainstill contains #107. Reverting it onmain(orletting the eventual rc→main release PR carry this revert) is a separate step.
After this merges, the binaries will need a fresh rc.4 roll + tag to pick up
the revert.