Skip to content

broacast on an empty [chain]/[key] outputs the wrong error message #81

@andynog

Description

@andynog

Tried to broadcast a tx but the path is empty on S3, instead of error saying files are not there, got a message saying needed signatures. It would make more sense show the right reason why it failed to broadcast (no files).

Got this error:

$ multisig broadcast cosmos ceph-cosmos
Error: Insufficient signatures for broadcast. Requires 2, got 0

But reason is fails is this:

$ multisig raw cat cosmos ceph-cosmos
No files in cosmos/ceph-cosmos

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions