Signing
This document explains the concepts of Messages and Transactions on Injective (on a higher level), what they represent, and how you can use them to trigger a state change on the Injective chain.
Message
In simpler terms, messages are the instructions given to Injective about the desired state change. Messages are module-specific objects that trigger state transitions within the scope of the module they belong to. Every transaction must have at least one message.
Transaction
Users initialize a transaction (tx) by add one or multiple messages into that transaction.
Once transaction is created, it requires signature(s) from user plus some optional config fields like memo, timeout_height, fee_payer...
Transaction is now ready to be broadcast to Flux Astromesh network and will be executed, modifying designated state related to those messages inside tx.
Signing
Users build and sign their txs through various supported tools