Update Secp256r1 Instruction with Message Length as Immediate #534
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.
Abstract
The current specified implementation of the Secp256r1 opcode assumes a 32 byte message being signed over, however, in the current widespread use of the curve in WebAuthn and passkeys, the signed message is larger than 32 bytes (e.g. 69 bytes).
Solution
Allow the immediate value to specify a more flexible message length beyond or below 32 bytes.
Considerations