feat(4337): add toUserOperation utility to convert PackedUserOperation to UserOperation
#3806
Conversation
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
|
@jeanregisser is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
🦋 Changeset detectedLatest commit: bcb74b1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Why this is needed
Real user need: When analyzing account abstraction transactions, or working with existing
PackedUserOperationdata, you often need the unpacked format to use with functions that expect the standardUserOperationformat (e.g.getUserOperationHash).The gap: Bundlers and newer EntryPoints use packed format for efficiency, but there's no built-in way to convert back to the unpacked format when needed for analysis or compatibility.
What it does
Converts packed user operations to standard unpacked format by splitting combined fields:
accountGasLimits→ separateverificationGasLimit+callGasLimitgasFees→ separatemaxPriorityFeePerGas+maxFeePerGaspaymasterAndData→ separate paymaster fieldsinitCode→ separatefactory+factoryDataWorks across all EntryPoint versions and safe to call on already unpacked data. This completes the conversion utilities - now you can go both ways between packed and unpacked formats.