multisig
multisig copied to clipboard
informalsystems
Painless multisig for many keys across many cosmos-sdk chains
This is ultimately an issue for the SDK but maybe there's something we can do in the meantime in multisig: https://github.com/cosmos/cosmos-sdk/issues/12328
Currently when executing the `multisig list` command, the output only displays the folders and files uploaded to S3. A better output would be a table with some details about the...
After broadcast a message there was an error, looks like something related to parsing the result which caused the files not to be deleted from S3
One of the common multisig commands is the `[binary] tx bank send`. Implement a new command for multisig: `multisig tx send`
When trying to sign a tx, if the user uses the wrong keys name (e.g the multisig key name), the tool might show an error that is not very intuitive...
Have a command that you can undelegate from a validator and also with the option `--all` that generate multiple transactions each with around 5 messages (one message per validator).
Currently there is no way to remove / delete all transactions in a particular path all at once. If you use the `delete` command you have to specify the index...
multisig couldn't understand the axelar json response and it didn't delete the files
Currently if a folder is empty e.g. `cosmos/ceph-cosmos` if you issue a command `multisig delete cosmos ceph-cosmos` the command doesn't delete the folder, in order to remove it you need...
When broadcasting a ```{"body":{"messages":[{"@type":"/cosmos.staking.v1beta1.MsgDelegate"...``` on Akash got the error ``` Error: error unmarshalling result: unknown field "mempoolError" in types.ResponseCheckTx ```
Metadata
Owner
Metadata
Painless multisig for many keys across many cosmos-sdk chains