Add basic custom calldata option #65
Open
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
|
@ipatka is attempting to deploy a commit to the Eternal Safe Team on Vercel. A member of the Team first needs to authorize it. |
ipatka
commented
Aug 18, 2025
| @@ -1,4 +1,4 @@ | |||
| FROM node:18-alpine | |||
| FROM node:20-alpine | |||
Author
There was a problem hiding this comment.
this change is unrelated but needed to make it for it to build
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.
What it solves
Allow custom transactions beyond ERC20 and ERC721 transfers
Partially Resolves #6
How this PR fixes it
Adds a simple option for arbitrary target and calldata. This does not yet support all the features of Safe transaction-builder like:
How to test it
Screenshots
Custom TX Option
Custom TX Form
Custom TX Form Filled
Custom TX Confirm
Checklist