feat: adding an option for call-data-file #474
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
The idea here is to to support large calldata where the input comes from a file rather than needing to be read as a argument. E.g ``` polycli ulxly bridge message \ --private-key $pkey \ --rpc-url http://127.0.0.1:18546 \ --bridge-address 0x1348947e282138d8f377b467F7D9c2EB0F335d1f \ --destination-network 23 \ --value 0 \ --call-data-file <(xxd -p /dev/random | tr -d "\n" | head -c 261569) ```
This reverts commit aebc9ed.
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.
The idea here is to to support large calldata where the input comes from a file rather than needing to be read as a argument. E.g