STR-3155: bind snark account updates to specific seqnos#1832
Conversation
|
Commit: a499232 SP1 Execution Results
|
Codecov Report❌ Patch coverage is
@@ Coverage Diff @@
## main #1832 +/- ##
==========================================
+ Coverage 79.63% 79.74% +0.10%
==========================================
Files 666 674 +8
Lines 73278 74745 +1467
==========================================
+ Hits 58356 59605 +1249
- Misses 14922 15140 +218
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 48 files with indirect coverage changes 🚀 New features to boost your workflow:
|
|
@codex review |
|
Codex Review: Didn't find any major issues. Chef's kiss. ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
bewakes
left a comment
There was a problem hiding this comment.
Looks good, but tests are failing.
|
Verrryyyy weird panic in recent versions of |
| # Disable debug_assertions in bitreq to dodge a known concurrency race in its | ||
| # `next_request_id >= readable_request_id` invariant, which fires under | ||
| # concurrent bitcoind RPC traffic in coverage/debug builds. Tracked upstream at | ||
| # https://github.com/rust-bitcoin/corepc/issues/583 (PR #584 unmerged). | ||
| [profile.dev.package.bitreq] | ||
| debug-assertions = false |
There was a problem hiding this comment.
add a TODO(STR-XXXX) comment here.
There was a problem hiding this comment.
Created ticket: https://alpenlabs.atlassian.net/browse/STR-3554
Description
This PR fixes an audit finding by adding a
seq_nofield to the snark account update proof interface, binding the proofs to a specific update seqno.Claude did most of the low-level work with me guiding it to minimize change blast radius.
Type of Change
Notes to Reviewers
Is this PR addressing any specification, design doc or external reference document?
If yes, please add relevant links:
Checklist
Related Issues