feat: deploy BackwardsCompatible4337Account in Deploy script#27
Merged
Conversation
Adds the opt-in ERC-4337 example account as a fourth deployed singleton alongside DefaultAccount, DefaultHighRateAccount, and UpgradeableAccount, so callers who need bundler/EntryPoint support have a canonical deployed implementation to point at.
chunter-cb
added a commit
to chunter-cb/viem
that referenced
this pull request
Jul 8, 2026
base/eip-8130#27 adds BackwardsCompatible4337Account as a fourth deployed singleton, so accounts.erc4337 (0x8812ee...) is a canonical deployed address rather than an opt-in the caller must deploy. Update the deployment doc comment and guides accordingly.
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
1 participant
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
BackwardsCompatible4337Accountas a fourth deployed singleton inscript/Deploy.s.sol, alongsideDefaultAccount,DefaultHighRateAccount, andUpgradeableAccount, so it has a canonical deployed implementation address for callers who opt into ERC-4337/bundler support.addresses()/run()logging and doc comments, and the README's contracts table, to reflect that it's now deployed by default (though neither of the other deployed accounts depends on it).Test plan
forge buildcompiles cleanlyforge fmt --checkpassesforge script script/Deploy.s.sol --sig "addresses()"previews all 4 account addresses plus authenticatorsforge test— 207 tests passing