feat: Add ERC20 approve transaction helper#343
Open
forceunwrap wants to merge 1 commit into
Open
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6d9fa3d547
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
9a82f39 to
34d0967
Compare
Add a generic ERC20 approve constructor in the contract transaction layer and expose a matching SafeSmartAccount transaction_erc20_approve API. This lets native clients submit a standard token approve(spender, amount) call through the existing 4337 transaction pipeline. World Card onboarding needs this to grant Permit2 spending approval before submitting the separate Permit2 allowance for the funding contract.
34d0967 to
497c9f2
Compare
aurel-fr
requested changes
May 28, 2026
Collaborator
aurel-fr
left a comment
There was a problem hiding this comment.
This is not an API we want to expose. We can add a custom function to grant allowance to the PERMIT2 contract if needed.
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
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
World Card onboarding needs to grant Permit2 spending approval before submitting the separate Permit2 allowance call to the funding contract. The existing helpers cover transfers (
transaction_transfer) and Permit2-side approvals (transaction_permit2_approve), but there was no path for a plain ERC-20approve— which is the prerequisite for any Permit2-based flow.What
Erc20Approvetype inbedrock/src/transactions/contracts/erc20.rsthat encodesIERC20.approve(spender, value)as a 4337UserOperationvia the existingIs4337Encodabletrait.TransactionTypeId::Erc20Approve = 141nonce type so approvals are distinguishable from transfers in on-chain analytics.SafeSmartAccount::transaction_erc20_approve(token_address, spender_address, amount)as a high-level API for native clients.Test
erc20.rscovering the approve call data encoding (test_erc20_approve_call_data) and nonce layout (test_erc20_approve_preflight_nonce_type_id).bedrock/tests/test_smart_account_erc20_approve.rsthat spins up Anvil, deploys a Safe with the 4337 module, funds the EntryPoint, executestransaction_erc20_approveend-to-end, and asserts the on-chainallowance(safe, spender)matches the requested amount.