Ensure your node is connected to an RPC Provider

The first step is to make sure you’re connected to RPC — if you’ve done our previous tutorial recently. All you’ll need to do is check the status!

_{gaiad status}

🟢 If things worked right, you should see output like below!

This means that your RPC endpoint is reachable from your gaiad installation. Having properly configured RPC is an essential step to sending our first transaction. You can move onto the next step!
‍

⚠️NOTE: if your RPC endpoint is unreachable, your terminal may hang. If so, press CTRL+C. You’ll need to return to the Lava gateway to get an RPC endpoint that you can use. Once you’ve retrieved a working RPC endpoint for the Cosmos Hub (Testnet), then you can continue onto the next step. Having a working RPC is essential to what we do next.

Once you’ve gotten your URL you can put it in gaiad with the following command, replacing the dummy URL with your own:

‍‍_{gaiad config node https://g.w.lavanet.xyz:443/gateway/cos5t/rpc-http/a43dd98c9ea68afa4f167969f48970bb}
‍

‍Then, type in the following command and see if your terminal hangs again._‍

_{gaiad status}‍

After doing so, you should get input similar to what was displayed above(🟢) and you can now move onto our next step!

Verify your Cosmos Wallet address & Balance from the Command Line

As you may remember in the last tutorial, you will have created a Cosmos wallet using only command-line input.
‍

An important step is to verify that this Cosmos wallet is still accessible from your machine. Type the following command:

_{gaiad keys list}

This will list all the keys available to gaiad at the time of this command. You should get some output that displays your previous address by key_name. It should look like the following:

⚠️ If you did not get a print out of names, types, and addresses, please refer to the last tutorial which will guide you through the creation of a new address!
‍

Next, we need to verify the balance of our address. Copy and paste the string of characters after it says address: and input the following command replacing my address with your own! We’ll use the query bank balances command which will give us information on all the available balances on chain at that address. An example of this should look like:

_{gaiad query bank balances cosmos15dgrn5rl8eah6s3lcjm5gjsn78w6kg5plmn6ml}

This will return input reporting the specified address’s balance. Behind the scenes gaiad is really asking the RPC node for the address - but that’s neither here nor there!

As you can see, we verify that we have a uatom balance of 1000000 . If you recall, this is from when we used the CosmosHub Testnet faucet. Now that we have verified our balance, we can move onto sending our funds.

Generate a Tx JSON

It’s important to note that if you’re sending it — it must be going somewhere!

First, let’s make sure we’ve got the correct chain-id. This is akin to making sure we’re operating in the correct universe. You can check where gaiad is pointed using gaiad config chain-id. We want to identify the Theta testnet:

_{gaiad config chain-id theta-testnet-001}‍

Our next step is to identify a sender and a receiver . We can use our pubkey address as the sender. If you don’t remember your address, you can always get it using the gaiad keys list command again. For a receiver, feel free to use my address cosmos15dgrn5rl8eah6s3lcjm5gjsn78w6kg5plmn6ml 😉. Of course, you’re always free to build a second key-pair using the same steps you made the first one. Once you have both a sender and receiver, build the transaction using the following format:

_{gaiad tx bank send <sender> <receiver> <amount> --fees=200uatom --generate-only > unsignedTx.json}

⭕ <sender> field will accept either your address. I use cosmos15dgrn5rl8eah6s3lcjm5gjsn78w6kg5plmn6ml which is the pubkey of my wallet titled test1.
⭕ <receiver> field is another public key address to send to. You can use cosmos15dgrn5rl8eah6s3lcjm5gjsn78w6kg5plmn6ml which is the public address I created at test1! I’ll use cosmos1qxpu7dc0vz2cha0rucdezevejvcwltw4ytqyd2 which is another address I created at test2.
‍
⭕ amount field is parsed as number, then denomination, for short hand <INTdenom> i.e., 1000uatom.
‍

With our --fees=<amount>tag, we need to specify the amount of fees that will be provided to cover the transaction we are building. It carries this same <INTdenom> format as the amount we send. We’ll choose 200 uatom, which should be sufficient to send at the time of this tutorial.
‍

It is this --generate-only flag which is crucial. --generate-only let’s gaiad know that we only want to create some output for our transaction, not actually send it! We could send straightaway but this gives us a chance to inspect the transaction that we are performing. We use > unSignedTx.json to dump the output into a JSON file in the current directory.

If you drop the --generate-only tag, gaiad will prompt you to sign automatically, so you can move onto step 6.

Otherwise, try to cat unSignedTx.json to ensure that the file has been generated by your command. It should contain tx info!

Broadcast the TX JSON using RPC

Now, the money!! Let’s send our transaction right away. 💸 Type the following:

_{gaiad tx broadcast signedTx.json}

Once we do, somewhere in the backdrop, an RPC node (perhaps one served through the Lava gateway) is processing our request. gaiad will attempt to sync and return the txHash after your transaction broadcasts! Make sure you copy it into your clipboard. You will need it for the next step.