chore: backport #21754 (feat!: make isContractInitialized a tri-state enum) to v4-next - #21792
Merged
nchamo merged 2 commits intoMar 19, 2026
Conversation
AztecBot
force-pushed
the
claudebox/backport-21754-tri-state-enum
branch
from
March 19, 2026 14:40
9f45f3c to
e6497c1
Compare
nchamo
marked this pull request as ready for review
March 19, 2026 14:44
nchamo
approved these changes
Mar 19, 2026
nchamo
enabled auto-merge (squash)
March 19, 2026 14:51
Collaborator
Author
Flakey Tests🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
AztecBot
added a commit
that referenced
this pull request
Mar 21, 2026
BEGIN_COMMIT_OVERRIDE chore: backport #21754 (feat!: make isContractInitialized a tri-state enum) to v4-next (#21792) fix(stdlib): zero-pad bufferFromFields when declared length exceeds payload (#21802) test(protocol-contracts): verify max-size bytecode fits in contract class log (#21818) chore: port P2P mesh topic deflake fix to v4-next (#21825) fix(archiver): throw on duplicate contract class or instance additions (#21799) feat: sync poseidon in the browser (#21833) chore: backport #21824 (fix(aztec-up): add sensible defaults to installer y/n prompts) to v4-next (#21844) fix(sequencer): backport wall-clock time for slot estimation to v4-next (#21769) (#21847) chore: backport PR #21788 (feat(p2p): add tx validation for contract class id verification) to v4-next (#21852) feat: sync poseidon browser (#21851) END_COMMIT_OVERRIDE
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 #21754 to v4-next.
Replaces
ContractMetadata.isContractInitialized(boolean | undefined) withContractMetadata.initializationStatus(ContractInitializationStatusenum:INITIALIZED,UNINITIALIZED,UNKNOWN). When the instance is not registered, the wallet now falls back to checking the public initialization nullifier before returningUNKNOWN.Cherry-pick conflicts
Two doc files conflicted due to version-specific differences between
nextandv4-next:docs/developer_versioned_docs/.../how_to_create_account.md— kept v4-next'snewAccount.addressvariable name, applied theinitializationStatusfield renamedocs/examples/ts/aztecjs_connection/index.ts— kept v4-next's existing structure (which already has the deploy sections), applied the field rename, dropped the duplicate incoming sections that usefeeJuiceAccountCommit structure