You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the app only supports signing messages for sending tokens. It would be great if multisigs could create and sign any message type (even uploading or pasting in JSON).
I'm a little unclear as to whether this would mean adding support for protobuf message types, or if the Amino signer can handle any message type.
I think this is a great and very valid feature request. However, unfortunatly CosmJS does not yet have the tools to support it well.
In CosmJS, everything starts with a protobuf message. This proto message is the one that is broadcasted to chain at the end of the day. In some cases, the messages are signed in a different representation than that (Amino JSON). But this only affects the signature generation, not how the message is actually encoded in the transaction.
Now those proto messages have a JavaScript representation: EncodeObject. This is good enough for caller-CosmJS app internal communication. But it does not a format that can easily be generated elsewhere. Ideally we support the protobuf JSON representation that is dumped by the Go tooling and convert it to EncodeObjects. This is something that would best be implemented in CosmJS as it is general purpose tooling.
Right now the app only supports signing messages for sending tokens. It would be great if multisigs could create and sign any message type (even uploading or pasting in JSON).
I'm a little unclear as to whether this would mean adding support for protobuf message types, or if the Amino signer can handle any message type.
@webmaster128 Any ideas?
The text was updated successfully, but these errors were encountered: