-
Here are some remarks regarding the documentation:
> Installing Noir from the Compiled Binary
We should update the binaries
> Note: At the time of pre-alpha, Nargo supports only one backend…
-
# Problem
Many users are requesting the ability to have global arrays. This will allow users to specify lists of compile time values in a separate file that can be referenced throughout a Noir proj…
-
The readme instructions should state that the Prover.toml file needs to be populated
-
### Aim
Computation is done incorrectly when I take a input (public) and return it.
This seems to be a new issue with 0.4.0
### Expected behavior
Perform computation as the code is writte…
-
While running `nargo prove` I got
The application panicked (crashed).
Message: assertion failed: `(left == right)`
left: `1`,
right: `0`
Location: crates/noirc_frontend/src/hir_def/types.r…
-
# Problem
Currently we have the concept of a public input, and we have the concept of a "return" field in the public inputs which functionally serves as public output.
# Solution
We can:
-…
-
As we add Noir contracts, there's going to become confusion around the `nargo contract` command. Does it create a solidity verifier contract or does it do something else related to noir contracts?
…
-
# Description
## Aim
1. Runs `noirup` with an existing `nargo` installation
2. Installation overwrites both `nargo` and the standard library with new versions
## Bug
```
noirup % sudo ba…
-
### Problem
I am trying to understand how merkle proof works in noir.
I have the following doubts:
- What is index? In examples, we are only using index 0 . Why is that the case
- How to dete…
-
https://docs.aztec.network/developers/noir