Add recursive verification example and cleanup #12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
critesjosh
commented
Oct 23, 2025
critesjosh
commented
- Adds an example to recursively verify noir proofs in aztec contracts.
- Introduced CLAUDE.md to provide guidance for using Claude AI with the repository.
- Expanded README to include an overview of the repository, examples, prerequisites, and development workflows.
- Updated project structure and added detailed instructions for running examples and testing.
- Removed outdated GitHub Actions workflow for testing examples.
- Introduced .gitignore to exclude build artifacts and dependencies. - Added CLAUDE.md and EXPLAINER.md for project documentation and guidance. - Created data.json for proof data storage. - Implemented scripts for proof generation and contract interaction. - Developed the ValueNotEqual contract to verify Noir proofs. - Included tests for contract deployment, proof verification, and counter management. - Established project structure with necessary configurations and dependencies.
…te README - Introduced a new workflow to automate recursive verification tests on push and pull request events. - Enhanced README with instructions for running tests and details on the CI/CD process. - Updated test assertions to use TxStatus for better clarity and maintainability.
- Introduced CLAUDE.md to provide guidance for using Claude AI with the repository. - Expanded README to include an overview of the repository, examples, prerequisites, and development workflows. - Updated project structure and added detailed instructions for running examples and testing. - Removed outdated GitHub Actions workflow for testing examples.
- Added environment variables to limit concurrency and increase memory allocation during proof data generation. - Included a timeout for the proof data generation step to ensure timely execution.
- Changed quotes from single to double in paths for consistency. - Updated Bun version to 1.1.36 for improved compatibility. - Ensured proper cleanup of Docker containers after tests.
- Updated README title for consistency and improved clarity. - Added links to additional examples in the Aztec monorepo. - Removed outdated starter token examples and related files to streamline the repository. - Enhanced contributing guidelines to encourage new example submissions and documentation improvements.
- Modified `.gitignore` to include `store/` directory. - Updated `package.json` to change the `recursion` script to use `tsx` and added new dependencies for `@aztec/kv-store` and `@aztec/noir-contracts.js`. - Refined `README.md` to correct command for executing the circuit. - Enhanced `generate_data.ts` by removing unused imports and simplifying proof data handling. - Revamped `run_recursion.ts` to integrate a new sandbox setup and wallet deployment process, improving contract interaction. - Introduced `sponsored_fpc.ts` for managing Sponsored FPC instances and deployment logic.
- Renamed the test step in the GitHub Actions workflow to "Run recursive verification script" and updated the command to execute the recursion script. - Increased the timeout for the recursive verification script from 10 to 15 minutes. - Added a new "clean" script in package.json to remove the store directory before running tests. - Modified the existing test script to include the clean step for better environment management. - Made minor adjustments to the run_recursion.ts script for improved readability.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.