chore: re-pin handshake registry with owner-bound nullifiers - #24893
Merged
Conversation
…able-initialization-nullifier-shared-between-two
nchamo
added
ci-draft
nventuro
approved these changes
Jul 21, 2026
nchamo
added
ci-draft
Base automatically changed from
nico/triage-196-privatemutable-initialization-nullifier-shared-between-two
to
merge-train/fairies-v5
July 21, 2026 19:42
…amo/repin-handshake-registry
nchamo
marked this pull request as ready for review
July 21, 2026 19:43
nchamo
enabled auto-merge (squash)
July 21, 2026 19:47
This was referenced Jul 21, 2026
This was referenced Jul 22, 2026
nchamo
added a commit
that referenced
this pull request
Jul 23, 2026
(cherry picked from commit c3a2a85)
6 tasks
rangozd
pushed a commit
to rangozd/aztec-packages
that referenced
this pull request
Aug 5, 2026
…Protocol#24934) Forward-ports the small **cli / bot / docs** commits of the v5-next → next backlog, plus an owner checklist for the spartan-config and standard-contract-repin commits (both need an explicit v6 decision — see below). ## Applied (clean cherry-picks, chronological) - perf(bot): parallelize independent bot factory setup steps (AztecProtocol#24581) - docs: revert threat model for node (AztecProtocol#24465) (AztecProtocol#24610) - feat(cli): support funding accounts in validator-keys new/set-funding-account (AztecProtocol#24476) ##⚠️ Needs owner conflict-resolution (conflict against reshaped `next`; not included here) Cherry-pick onto this branch and resolve: - [x] `git cherry-pick -x 38202d9` — chore(spartan): restore 7 day mainnet slash grace period (AztecProtocol#24804) - [x] `git cherry-pick -x c3a2a85` — chore: re-pin handshake registry with owner-bound nullifiers (AztecProtocol#24893) Part of the manual v5-next → next backlog sweep. Draft until conflicts are resolved and CI is green.
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
HandshakeRegistryso itsPrivateMutablestate uses the owner-bound initialization nullifiers from fix: change init and single claim nullif to incl owner address, add testing utilities #24892, keeping the handshake state of accounts that share keys independent. The registry moves to a new address, and handshakes established with the previous instance must be re-established.sync_state(which still references the old registry address) is never executed now that PXE skips syncing stateless standard contracts (fix: dont panic on note msgs on contracts with no notes #24852).Merges after #24892.