We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
cast wallet sign
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cast
I am building a small wrapper around cast wallet for users to interface with the Safe multisig api. It uses the following two cast operations:
cast wallet address
... unfortunately, as a result, the user must input the same password consecutively - once for each operation.
Can we please have a new cast wallet sign option that allows optional returning both pieces of information in a single command?
No response
The text was updated successfully, but these errors were encountered:
@wavey0x wouldn't this work for you by setting it as an env var and passing it to commands?
Sorry, something went wrong.
Works, but don't want to force user to set cleartext env vars with highly sensitive passwords.
I think you should capture the password once in your program and then pass it along how you see fit using the --password flag.
--password
cast wallet sign "hello" --keystore <keystore> --password <password>
I would like to avoid adding highly specific behavior that combines command invocations.
For now marking this as not planned
not planned
No branches or pull requests
Component
Cast
Describe the feature you would like
I am building a small wrapper around cast wallet for users to interface with the Safe multisig api. It uses the following two cast operations:
cast wallet sign
to sign a payloadcast wallet address
to get the address of the account that signed... unfortunately, as a result, the user must input the same password consecutively - once for each operation.
Can we please have a new
cast wallet sign
option that allows optional returning both pieces of information in a single command?Additional context
No response
The text was updated successfully, but these errors were encountered: