aztec-packages
aztec-packages copied to clipboard
Otherwise they don't get forwarded to the container if run with the aztec script.
Adds a LOG_JSON env var that disables the foundation logger and replaces it with a winston json logger. ``` {"level":"info","message":"Set block interval to 12","module":"aztec:sandbox","timestamp":"2024-08-21T02:15:29.509Z"} {"level":"info","message":"Deploying contracts from 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266...","module":"aztec:sandbox","timestamp":"2024-08-21T02:15:29.509Z"} {"level":"info","message":"Deployed Registry...
:robot: I have created a release *beep* *boop* --- aztec-package: 0.50.0 ## [0.50.0](https://github.com/AztecProtocol/aztec-packages/compare/aztec-package-v0.49.2...aztec-package-v0.50.0) (2024-08-21) ### Features * Add a prover-node to the proving e2e tests ([#7952](https://github.com/AztecProtocol/aztec-packages/issues/7952)) ([ec5a5fb](https://github.com/AztecProtocol/aztec-packages/commit/ec5a5fb8fd9c344bcb0d33a4e9f07300d3317bf2)) * Add max...
Cloudwatch is smart enough to parse JSON logs, and we can use the different fields extracted for querying in Insights. **Builds on #8095**
Initial definition of the helm chart for an "aztec-network". Currently not part of CI (that is https://github.com/AztecProtocol/aztec-packages/issues/8000). However, a meaningful smoke test is included that can be run with: ```...
Automated pull of development from the [noir](https://github.com/noir-lang/noir) programming language, a dependency of Aztec. BEGIN_COMMIT_OVERRIDE fix: (LSP) only add cached files relevant to workspace (https://github.com/noir-lang/noir/pull/5775) chore: make spans non-optional on `UnresolvedType`...
Please read [contributing guidelines](CONTRIBUTING.md) and remove this line.
This script replaces the gen_inner_proof_inputs_ultra_honk.sh with regenerate_verify_honk_proof_inputs.sh, which does the resetting of test_programs and input copying automatically so that people don't have to know intricate details on what to do...
Please read [contributing guidelines](CONTRIBUTING.md) and remove this line.
This PR is the first of several where we are moving to use native implementations of Merkle Trees for performance reasons. It includes: 1. The core tree implementations for both...