Repository navigation
fix(pyth): keep vaa verification within wasm local limit - #2084
Conversation
Signed-off-by: Joseph Chalabi <chalabi.joseph@gmail.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review. WalkthroughSignature verification now bounds-checks and processes the declared signature region in fixed-size chunks. A helper performs per-signature validation. Tests check malformed signature bytes and invalid recovery IDs at each of three signer positions. ChangesRouter signature verification
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~12 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to No merge-blocking issue is identified in the router signature-verification change; it is ready for normal checks. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
A rabbit checks each signature with care Comment |
Reduces optimized function locals from 137 to 83. Validated with wasmvm v3.0.8 and 29 passing tests.