Repository navigation
docs(benchmarks): limit aarch64 ECDSA's P256Order assumption to parsed keys - #390
Conversation
…d keys Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Your OpenCode Go account is out of credit. Top it up, then re-trigger Pullfrog. OpenCode Go's response
|
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 58 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed head: 6226d94
No actionable findings in this documentation-only change.
The narrower assumption matches the proof at this commit:
proofs/Rind/Aarch64/P256Signature.lean:388-488states generation, key loading, and signing without aP256Orderparameter.p256_ecdsa_key_pair_verify(lines 516-535) suppliesg_mult_order d hd0 hd, whose proof inproofs/Rind/P256Multiples.lean:357-364derives the key pair's point order from the proven generator order.p256_ecdsa_public_key_new(lines 540-563) still takesho : P256Orderand uses it for verification with the parsed point.- The changed proof text in
benchmarks/verified.toml:108matches the rendered aarch64 ECDSA row inBENCHMARKS.md:564; the partial-correctness caveat for the unbounded nonce loop remains.
Direction: no revision requested on the reviewed diff.
Limits: GitHub-only static review. I did not run quest context, just check, the benchmark renderer, or Lean proofs; the PR's reported just check result was not independently reproduced. At the reviewed head, the queue checks are skipped, CodeRabbit is rate-limited, and Pullfrog failed with the reported provider-credit error, so these checks do not establish a fresh test/proof pass.

Follow-up to moq-dev/rind#384, which proved P-256's generator has order n. The aarch64 P-256 ECDSA proof now assumes HOL Light's P256_GROUP_ELEMENT_ORDER only for verification with a parsed public key; key generation, loading, signing, and verifying with a key pair's own point no longer need it.
benchmarks/verified.tomlstill said the whole ✓ assumed it, so this narrows the note and re-rendersBENCHMARKS.md.just checkpasses.🤖 Generated with Claude Code
(Written by Claude Opus 5.5)