feat(aztec): universal deploys in the deployment framework - #25263
Open
Thunkar wants to merge 1 commit into
Open
feat(aztec): universal deploys in the deployment framework#25263Thunkar wants to merge 1 commit into
Thunkar wants to merge 1 commit into
Conversation
Contract steps declare either deployer (bound: salts + sends, the address commits to it) or universal + from (the address is the same whoever sends it; from sends and pays) — mutually exclusive in the type, mirroring DeployMethod.create. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Thunkar
force-pushed
the
gj/deploy-universal-flag
branch
from
August 18, 2026 17:17
519338a to
57b482d
Compare
Thunkar
marked this pull request as ready for review
August 18, 2026 17:27
Collaborator
Flakey Tests🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
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.
Contract steps had no way to publish at a deployer-independent address:
resolveContractalways builds a deployer-boundDeployMethod, which rejects universal shapes. Some contracts need exactly that — an address agreed on and shared before anyone commits to deploying it (e.g. an FPC that receives deposits at a pre-published address).A contract step now declares either
deployer(bound: salts + sends, the address commits to it) oruniversal: true+from(the address is the same whoever sends it;fromsends and pays) — mutually exclusive in the type, mirroringDeployMethod.create. Register mode derives accordingly, keeping the register/publish same-address invariant. Covered indeploy.test.ts.🤖 Generated with Claude Code