Skip to content

chore: redo typo PR by donatik27 #9004

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TomAFrench merged 1 commit into from
Jun 24, 2025
Merged

chore: redo typo PR by donatik27 #9004

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ jobs:
run: |
cargo update --workspace

- uses: actions/setup-node@v3
- uses: actions/setup-node@v4
with:
node-version: 20.18.3
cache: 'yarn'
Expand Down
6 changes: 6 additions & 0 deletions acvm-repo/acir/src/circuit/opcodes/black_box_function_call.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,12 @@ pub enum BlackBoxFuncCall<F> {
/// For more context regarding malleability you can reference BIP 0062.
/// - the hash of the message, as a vector of bytes
/// - output: 0 for failure and 1 for success
///
/// Expected backend behavior:
/// - The backend MAY fail to prove this opcode if the public key is not on the secp256k1 curve.
/// - Otherwise the backend MUST constrain the output to be false.
/// - The backend MUST constrain the output to be false if `s` is not normalized.
/// - The backend MUST constrain the output to match the signature's validity.
EcdsaSecp256k1 {
public_key_x: Box<[FunctionInput<F>; 32]>,
public_key_y: Box<[FunctionInput<F>; 32]>,
Expand Down
Loading