Tom French

I'm not sure why this was closed originally. I'm taking a look at the linked repo but if I run the tests then I get `false` printed on [this line](https://github.com/signorecello/noir-breaking-verify-signature/blob/35df0c9a3847f696d0c6104143702cb716a90f59/test/index.test.js#L77)....

I've replaced the secp256r1 library being used as I don't really trust it with https://github.com/paulmillr/noble-curves. I've then updated the test suite as below ``` const { BarretenbergBackend } = require...

Note that if you do not call `normalizeS` on the secp256r1 signature then the noir program execution will fail. We reject high S signatures inside the ACVM for malleability reasons....

I'll replace this with a new issue based on the actual error which was uncovered.

See usage here: https://github.com/noir-lang/noir/blob/16d5f18c68cc3da1d11c98e101e3942d2437c3a8/tooling/noir_codegen/package.json#L38

This will no longer panic once https://github.com/noir-lang/noir/pull/4408 is merged but is still active.

This is hard requirement before launching on mainnet as currently it's trivial for a malicious party to drain a stream in their favour by submitting a new stream creation transaction...

Seems like AZTEC have silently added the proof export option http://docs.aztecprotocol.com/#/SDK/zkAsset/Main%20APIs/.send All that remains is generating the required signature

Any update on this?

Ah yeah, looks like the V1 repo is pulling directly from gh rather than from fleek. We'll need to lock it to a particular tag or branch in that case...