feat(pxe): add resolveCustomRequest hook for caller-defined requests - #24409
Merged
Conversation
nchamo
added
ci-no-fail-fast
nchamo
commented
Jun 30, 2026
|
|
||
| When the hook is absent, the PXE applies a privacy-safe default: unconstrained delivery uses an [address-derived shared secret](../../aztec-nr/framework-description/note_delivery.md#tagging-secret-strategy), which leaves no onchain trace, while constrained delivery fails rather than silently revealing the recipient through a [non-interactive handshake](../../aztec-nr/framework-description/note_delivery.md#tagging-secret-strategy). | ||
|
|
||
| ## `resolveCustomRequest` |
Contributor
Author
There was a problem hiding this comment.
Not in love with the name, open to suggestions
nchamo
marked this pull request as ready for review
June 30, 2026 18:22
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.
Motivation
Contracts sometimes need a value they cannot derive locally or from the protocol's existing oracles. The first case is interactive handshakes, where a sender needs the recipient's signature to establish a shared secret, but there is no generic way for a contract to ask the wallet to fulfill an arbitrary request.
The change
Adds a generic, hook-backed request primitive:
resolve_custom_request(kind, payload)and PXE routes it to a wallet-suppliedresolveCustomRequesthook, returning the opaque response.kindselects the request type so a single hook can serve many; everything request-specific goes in the opaquepayload. The request carries the issuing contract's address and class ID so a resolver can gate per contract.There is no consumer yet; the interactive-handshake flow that uses this primitive lands in a follow-up.