-
# Description
Currently we allow return values to be supplied by the prover. This can only be done if the prover runs through the program and generates those values, which is unlikely.
## Aim
…
-
### Aim
We (@fuzzinglabs & @lambdaclass) found an out-of-memory issue in acvm 0.8.1 while reading a circuit.
### Expected behavior
It should not crash.
### Bug
## Root cause
```
memory alloca…
-
# Description
## Expected behavior
For loops shouldn't require a semicolon on their closing brace in order to be valid Noir. This is consistent with Rust's syntax and stated test cases.
## Bu…
-
# Description
## Aim
Auto returning the value of an array without the need to specify it in `Prover.toml` before proving.
The feature was introduced in https://github.com/noir-lang/noir/pull/…
-
# Description
## Aim
Computes an unknown Pedersen hash value.
## Expected behavior
Running `nargo execute` / `nargo prove` on the following should auto-compute the return value and…
-
# Problem
Although the documentation does not forbid to pass arrays of booleans as input to the main function of the circuit, the noirc_abi does not handle this situation.
The problem is easy to rep…
-
# Description
trying to prove the hello world from here https://noir-lang.github.io/book/getting_started/hello_world.html
## Aim
run `nargo prove p`
## Expected behavior
`p.proof` file
…
-
# Description
Currently, calling `noirc_driver::Driver::compile_file` with a `root_file` that doesn't have `.nr` as the extension panics due to unwrapping an option from the call to `FileManager::a…
-
Using the provided values:
```
y = "4"
setpub = []
```
it returns:
```
root@1ff1697833b8:~/circuits# nargo verify my_proof
thread 'main' panicked at 'Expected 1 number of values in Verifier.to…
-
When calling `nargo new `
The generated files are excessively indented.
nargo 0.1
os - Darwin 21.5.0 arm64