Migrate examples to Aztec v3.0.0-devnet.20251212#21
Merged
critesjosh merged 4 commits intomainfrom Jan 14, 2026
Merged
Conversation
Update four example projects to use the latest Aztec devnet version: - custom-note: Update contract to use Owned<PrivateSet> pattern, add randomness to CustomNote, use .deliver() for message delivery - account-contract: Update imports from dep::aztec to aztec, use poseidon2_hash, fix TypeScript API for v3 DeployMethod signature - test-wallet-webapp: Update package dependencies - note-send-proof: Major migration from v2 to v3, rewrite contract to use BalanceSet pattern, add postinstall workaround for bb.js native module path issue, update tests to use Jest with yarn All contracts compile and tests pass. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- note-send-proof: Update from v2.0.3 to v3.0.0-devnet.20251212, use local-network instead of sandbox, use `aztec compile` instead of `aztec-nargo compile` - test-wallet-webapp: Update from v3.0.0-devnet.5 to v3.0.0-devnet.20251212, use local-network instead of sandbox Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Use TestWallet instead of createPXEClient (removed in v3) - Use getInitialTestAccountsData and wallet.createSchnorrAccount - Update imports to use v3 subpaths - Fix storage slot reference to use user_balances Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
sklppy88
reviewed
Jan 14, 2026
Collaborator
sklppy88
left a comment
sklppy88
left a comment
There was a problem hiding this comment.
I think note send proof has lost its intended purpose with these changes
Collaborator
There was a problem hiding this comment.
I feel like these tests have completely changed semantically
|
|
||
| #[private] | ||
| #[external("private")] | ||
| fn create_note_for_user(value: u128) { |
Collaborator
There was a problem hiding this comment.
This function shouldn't be changed this much. It changes the way we test it and the purpose / meaning of the contract itself
Collaborator
There was a problem hiding this comment.
The filename change makes this diff 😢
Contributor
Author
There was a problem hiding this comment.
renamed it back to the old name :) we can rename it once its merged
…cation This commit restores the original intent of the note-send-proof example by implementing a custom UintNote with controlled randomness. The key changes: - Create custom uint-note library with create_note_with_randomness function - Use fixed randomness (6969) to enable reproducible hash computation - Update contract to use simple storage slot instead of Map - Update tests to verify computed hash matches on-chain hash - Update generate_data.ts with v3 hash formula ([owner, storage_slot, randomness]) - Update README with v3 hash computation documentation - Fix tsconfig.json moduleResolution for v3 package exports The example now demonstrates: 1. Creating private notes with known parameters 2. Computing the note hash chain (inner -> siloed -> unique) 3. Verifying the computed hash matches what's stored on-chain Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
sklppy88
reviewed
Jan 14, 2026
| nonceGenerator, | ||
| INDEX_OF_NOTE_HASH_IN_TRANSACTION | ||
| ); | ||
| test('should create note with different value and verify hash', async () => { |
Collaborator
There was a problem hiding this comment.
Can probably refactor this to use it.each given most if not all of this is the same, but no need to do in this pr
sklppy88
approved these changes
Jan 14, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Changes by Project
custom-note
CustomNoteContractto avoid naming conflict withCustomNotestructOwned<PrivateSet<CustomNote, Context>, Context>pattern.deliver(MessageDelivery.UNCONSTRAINED_ONCHAIN)for note deliveryaccount-contract
dep::aztectoaztecposeidon2_hashfromaztec::protocol_types::hashDeployMethodcallback signature:(instance, wallet) => ...instead of(address) => ...test-wallet-webapp
note-send-proof
BalanceSetpattern from aztec-nrTest plan
aztec compilesucceeds for all Noir contractsaztec testpasses for custom-note (0 tests)aztec testpasses for account-contract (0 tests)yarn buildsucceeds for test-wallet-webappyarn testpasses for note-send-proof (3 tests)npx tsx ts/deploy-account-contract.tsdeploys successfully🤖 Generated with Claude Code