Skip to content

feat: merge-train/fairies#21760

Open
AztecBot wants to merge 3 commits intonextfrom
merge-train/fairies
Open

feat: merge-train/fairies#21760
AztecBot wants to merge 3 commits intonextfrom
merge-train/fairies

Conversation

@AztecBot
Copy link
Collaborator

@AztecBot AztecBot commented Mar 18, 2026

BEGIN_COMMIT_OVERRIDE
refactor: revert remove assert_bounded_vec_trimmed (#21758)
END_COMMIT_OVERRIDE

AztecBot and others added 2 commits March 18, 2026 18:53
Getting rid of the tyranny of the `Account` entrypoint, and the terrible
sentinel value of `AztecAddress.ZERO` in the `from` parameter.

Now, when a tx is specified as being sent `from: NO_FROM`, the wallet
completely bypasses the account contract. It doesn't even use the
`MulticallEntrypoint` contract, it'll just execute a single call using
`DefaultEntrypoint`. Since we can do wrapping at the app level, this
means ANYTHING goes. Want to wrap 10 calls on a special sauce multicall?
Go ahead. App-sponsored FPC with custom logic that must be the first on
the chain? Knock yourself out!

Even better news: this is thoroughly tested in our codebase thanks to
account contract self-deployments. They're a great example of "I don't
want to use an account contract as entrypoint" flow.

As an extra side effect, this completely deshrines the
`MulticallEntrypoint` protocol contract from the wallet (we only have
the convenience now of it being already registered in every single
wallet)
@Thunkar Thunkar requested a review from a team as a code owner March 18, 2026 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants