Ctrlk
WebDiscordGithubTwitter

Multi Message Transaction

Understand how to perform multiple actions at the same time in a single block.

Transactions Vs Messages

A message is a unit of data that represents a single action or intent to perform an action, such as sending tokens from one account to another, creating a new validator, or executing a smart contract function. Messages are the basic building blocks of transactions and are used to describe the specific action that is being requested. (You can think of these as "sub transactions or commits" bundled up into 1 master transaction push).

A transaction, on the other hand, is a collection of one or more messages that are grouped together and signed by a single account. When a transaction is broadcast to the network, it is validated by the nodes on the blockchain, and if it is deemed valid, the requested actions specified in the messages are executed. Transactions provide a way to ensure that multiple actions can be performed atomically, meaning that either all of the actions are executed successfully or none of them are.

One transaction per block, with a transaction being multiple messages.

Transaction Limitation / Account Sequence

By default, you can only submit 1 transaction per block. In doing this, it will increase your wallets account sequence by one. If you try to submit multiple transactions in the same block, it will error with a account sequence mismatch error. This means there is a pending transaction for your account already in the on chain pending pool (mempool of transactions). Once this transaction goes through and all messages are successfully executed, you can submit another transaction in the following block.

Multi Message Transaction (bank)

To generate a multiple message transaction, you will need to slight scripting knowledge to assist for your needs. This works for any module in Juno, and you can add as many different messages to the same transaction within the gas limit. (Gas is a deterministic number describing the amount of computer a given action takes on a node).

First, you need to generate a default single message transaction from the command line. Ensure that the from address is an address you have the key access too.

NOTE: ujunox is used on the uni-6 chain-id, while ujuno is used on the mainnet juno1 chain-id. You can find uni-6 testnet nodes on https://testnet.cosmos.directory/junotestnet/nodes

junod tx bank send juno16g2r... juno1t8e... 1000000ujunox \
    --generate-only --fees=5000ujunox \
    --chain-id=uni-6 --node=https://rpc.uni.junonetwork.io:443 [flags] > bankmsgs.json
{
  "body": {
    "messages": [
      {
        "@type": "/cosmos.bank.v1beta1.MsgSend",
        "from_address": "juno16g2rahf5846rxzp3fwlswy08fz8ccuwk03k57y",
        "to_address": "juno1t8ehvswxjfn3ejzkjtntcyrqwvmvuknzy3ajxy",
        "amount": [
          {
            "denom": "ujuno",
            "amount": "1000000"
          }
        ]
      }
    ],
    "memo": "",
    "timeout_height": "0",
    "extension_options": [],
    "non_critical_extension_options": []
  },
  "auth_info": {
    "signer_infos": [],
    "fee": {
      "amount": [
          {
              "denom": "ujunox",
              "amount": "5000"
          }
      ],
      "gas_limit": "200000",
      "payer": "",
      "granter": ""
    }
  },
  "signatures": []
}

Here we are interested in the body -> messages section. In this array, we can put any amount of actions (within the gas limitation) for this transaction to execute with a single execute. So if I wanted to send another amount to a different address at the same time as well, we can manually alter the array of messages to add this new message like so

In this case, we send 5JUNO to juno1ka... as well as the original account, at the same time. (Reminder: ujuno is a 6th exponent representation of human readable form). So in the above messages, we in total send 6JUNO.

NOTE: If our account only has less than 6JUNO, the entire above transaction would fail (non 0 return code) for not enough balance. Even through the first message is only 1JUNO, all messages in a transaction do not execute unless they are all successful. This is a safety mechanism!

Then we can sign and broadcast it

Multi Message NFT Mint (CosmWasm)

After reading the above guide, the same steps can be applied to mint cosmwasm based NFTs (CW721s). This requires you to submit an NFT contract to chain first, and setup with your collections values before moving on to this step. We will link to that guide HERE in the future.

Once again we are interested in the body -> messages section. In this array, we can put any amount of actions (within the gas limitation) for this transaction to execute with a single execute. So if I wanted to mint another within the same tx we can do the following manually.

Automate Minting Example

Here is a python example for how to automate minting NFTs for a contract based off some parameters. This is only the base logic to get you started in the right direction

This saves a file named mint_nfts.json to the directory this script is saved in. From here you can do the following to execute it on chain

PreviousConversionsNextGet & Decode Transactions

Last updated

Was this helpful?