feat: support emitting messages from utilities (backport #21422)#21551
Merged
mverzilli merged 1 commit intobackport-to-v4-next-stagingfrom Mar 16, 2026
Merged
Conversation
Makes it possible to emit offchain messages by making the corresponding oracle available to utilities, and bubbling the relevant information all the way up to the wallet/aztecjs results. Closes F-427
2997a4b to
3c11df2
Compare
mverzilli
approved these changes
Mar 16, 2026
Collaborator
Author
Flakey Tests🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
169dc49
into
backport-to-v4-next-staging
20 of 22 checks passed
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
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
Backport of #21422 to v4-next via
backport-to-v4-next-staging.Makes it possible to emit offchain messages by making the corresponding oracle available to utilities, and bubbling the relevant information all the way up to the wallet/aztecjs results.
Changes
Cherry-pick of
dc9053c1213eaf3780cfd575cbd66c10dabda40dontobackport-to-v4-next-staging. Only 2 conflicts needed resolution:offchainEffects.map(e => ({ data: e.data }))mapping (strips contractAddress for PrivateCallExecutionResult), keptpreTags(v4-next naming vstaggingIndexRangeson next)getOffchainEffects()from PrivateExecutionOracle (now inherited from parent UtilityExecutionOracle), kept v4-next doc comment naming