CLI Feature/Command Request: calldata encoding

abcoathup · October 25, 2019, 1:07am

@gitpusha created a feature request to add calldata encoding to the OpenZeppelin CLI
See the GitHub Issue for details:

github.com/OpenZeppelin/openzeppelin-sdk

New command for calldata encoding

opened 08:29AM - 24 Oct 19 UTC

kind:idea topic:interacting

TL;DR: - CLI command that abi encodes args you pass - CLI command that abi e…ncodes function Signature you pass with its args It would be sweet to have a `oz` `CLI` `command` `option` that let's you pass `args` and have them `abi` `encoded` into a `bytes` `payload` by passing a `option` flag like `--bytes` or `--encode`. It would also be cool to have a `oz` `CLI` `command` `option` that let's you pass a `function Signature` with its `args` and then pass a `flag` like `--encodeWithSig`, so that the `payload` is automatically converted into `abi.encoded bytes` with a `function selector`. I use a lot of contracts that usually would get abi encoded parameters from a frontend. It would be sweet to be able to play around with these contracts from the `oz` `CLI` tool too, without having to manually encode the `args` I wanna pass to a `send-tx` myself. I have seen such a `CLI` feature before with `seth`. Check it out: http://dapp.tools/seth/ ![image](https://user-images.githubusercontent.com/36712489/67467486-195bc180-f649-11e9-8e2d-65668df9a378.png)

Topic		Replies	Views
Encoding function call data from upgradeable contract itself Contracts upgrades	1	1841	July 10, 2020
Abi.encode VS abi.encodePacked Support	6	47912	April 20, 2022
Decode input arguments for transaction hash Smart Contracts etherscan-verify	2	937	February 20, 2023
Using call(abi.encode()) in solidity, but getting error Contracts	1	1467	May 1, 2021
How is the output of a contract call encoded? Support	2	484	April 30, 2021

CLI Feature/Command Request: calldata encoding

Related topics