Make Container.sol ERC-4337 compliant
#27
Merged
Conversation
This file contains 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
v3.15.0
…trypoint' ReentrancyGuard to v5.0.0
… calldata packing
…e docs and checks
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.
Breaking changes
ContainerERC-4337 compliant by inheriting the Thirdweb non-upgradeableAccountCoreimplementation;DockRegistrycontract to comply with theBaseAccountFactorypattern;DockRegistryto act as a ERC-4337 factory allowing smart accounts to easily be created through thecreateAccountmethod. As before, at the creation time, eachContainergoes under one dock space. This method is also responsible to enable the initial modules on the smart account;Other changes
executeBatchmethod on theContainersmart account allowing for multiple module calls to be made within the same transaction;DeployDeterministicDockRegistryandDeployContainerscripts;