chore: backport PR #21716 (feat!: no_from) to v4-next#21768
Merged
Thunkar merged 2 commits intobackport-to-v4-next-stagingfrom Mar 19, 2026
Merged
chore: backport PR #21716 (feat!: no_from) to v4-next#21768Thunkar merged 2 commits intobackport-to-v4-next-stagingfrom
Thunkar merged 2 commits intobackport-to-v4-next-stagingfrom
Conversation
AztecBot
added
ci-draft
AztecBot
force-pushed
the
claudebox/backport-21716-no-from-v4-next
branch
from
246aa49 to
717548e
Compare
AztecBot
force-pushed
the
claudebox/backport-21716-no-from-v4-next
branch
from
717548e to
1249867
Compare
Thunkar
approved these changes
Mar 19, 2026
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
Backports #21716 to v4-next via
backport-to-v4-next-staging.Based on latest
backport-to-v4-next-stagingwhich has #21646 (gas estimations on send), so this PR contains only #21716's actual changes (NO_FROM pattern).Cherry-pick conflicts resolved:
bot/src/factory.ts—AztecAddress.ZERO→NO_FROMe2e_fees/account_init.test.ts—AztecAddress.ZERO→NO_FROMdocs/examples/ts/recursive_verification/index.ts— imports + data loading updateddocs/examples/ts/aztecjs_connection/index.ts—AztecAddress.ZERO→NO_FROMin existing fee juice section, discarded duplicate sections from cherry-pickspartan/block_capacity.test.ts— deleted (already removed on v4-next)Key changes
NO_FROMpattern replacingAztecAddress.ZEROsentinel for bypassing account contract entrypointSignerlessAccountContractDefaultEntrypointdirectly whenfrom: NO_FROMMulticallEntrypointfrom wallet internals