Interact Node

Interacting with the Node
There are multiple ways to interact with a node: using the CLI, using gRPC or using the REST endpoints.
Using the CLI
Now that your chain is running, it is time to try sending tokens from the first account you created to a second account. In a new terminal window, start by running the following query command:
1
rizond query bank balances $MY_ADDRESS --chain-id my-test-chain
Copied!
You should see the current balance of the account you created, equal to the original balance of uatolo you granted it minus the amount you delegated via the gentx. Now, create a second account:
1
rizond keys add recipient --keyring-backend test
2
​
3
# Put the generated address in a variable for later use.
4
RECIPIENT=$(rizond keys show recipient -a --keyring-backend test)
Copied!
The command above creates a local key-pair that is not yet registered on the chain. An account is created the first time it receives tokens from another account. Now, run the following command to send tokens to the recipient account:
1
rizond tx bank send $MY_ADDRESS $RECIPIENT 2000000uatolo --chain-id my-test-chain --keyring-backend test
2
​
3
# Check that the recipient account did receive the tokens.
4
rizond query bank balances $RECIPIENT --chain-id my-test-chain
Copied!
Finally, delegate some of the stake tokens sent to the recipient account to the validator:
1
rizond tx staking delegate $(rizond keys show $MY_ADDRESS --bech val -a --keyring-backend test) 1000000uatolo --from recipient --chain-id my-test-chain --keyring-backend test
2
​
3
# Query the total delegations to `validator`.
4
rizond query staking delegations-to $(rizond keys show $MY_ADDRESS --bech val -a --keyring-backend test) --chain-id my-test-chain
Copied!
You should see two delegations, the first one made from the gentx, and the second one you just performed from the recipient account.
Using gRPC
The Protobuf ecosystem developed tools for different use cases, including code-generation from *.proto files into various languages. These tools allow the building of clients easily. Often, the client connection (i.e. the transport) can be plugged and replaced very easily. Let's explore one of the most popular transport: gRPC.
Since the code generation library largely depends on your own tech stack, we will only present three alternatives:
grpcurl for generic debugging and testing,
programmatically via Go
grpcurl
​grpcurl is like curl but for gRPC. It is also available as a Go library, but we will use it only as a CLI command for debugging and testing purposes. Follow the instructions in the previous link to install it.
Assuming you have a local node running (either a localnet, or connected a live network), you should be able to run the following command to list the Protobuf services available (you can replace localhost:9000 by the gRPC server endpoint of another node, which is configured under the grpc.address field inside app.toml):
1
grpcurl -plaintext localhost:9090 list
Copied!
You should see a list of gRPC services, like cosmos.bank.v1beta1.Query. This is called reflection, which is a Protobuf endpoint returning a description of all available endpoints. Each of these represents a different Protobuf service, and each service exposes multiple RPC methods you can query against.
In order to get a description of the service you can run the following command:
1
grpcurl \
2
    localhost:9090 \
3
    describe cosmos.bank.v1beta1.Query  # Service we want to inspect
Copied!
It's also possible to execute an RPC call to query the node for information:
1
grpcurl \
2
    -plaintext
3
    -d '{"address":"$MY_ADDRESS"}' \
4
    localhost:9090 \
5
    cosmos.bank.v1beta1.Query/AllBalances
Copied!
​
Query for historical state using grpcurl
You may also query for historical data by passing some gRPC metadata to the query: the x-cosmos-block-height metadata should contain the block to query. Using grpcurl as above, the command looks like:
1
grpcurl \
2
    -plaintext \
3
    -H "x-cosmos-block-height: 10000" \
4
    -d '{"address":"$MY_ADDRESS"}' \
5
    localhost:9090 \
6
    cosmos.bank.v1beta1.Query/AllBalances
Copied!
Assuming the state at that block has not yet been pruned by the node, this query should return a non-empty response.
Programmatically via Go
The following snippet shows how to query the state using gRPC inside a Go program. The idea is to create a gRPC connection, and use the Protobuf-generated client code to query the gRPC server.
1
import (
2
    "context"
3
    "fmt"
4
​
5
    "google.golang.org/grpc"
6
​
7
    sdk "github.com/cosmos/cosmos-sdk/types"
8
    "github.com/cosmos/cosmos-sdk/types/tx"
9
)
10
​
11
func queryState() error {
12
    myAddress, err := sdk.AccAddressFromBech32("rizon1...")
13
    if err != nil {
14
        return err
15
    }
16
    denom := "uatolo"
17
​
18
    // Create a connection to the gRPC server.
19
    grpcConn := grpc.Dial(
20
        "127.0.0.1:9090", // your gRPC server address.
21
        grpc.WithInsecure(), // The SDK doesn't support any transport security mechanism.
22
    )
23
    defer grpcConn.Close()
24
​
25
    // This creates a gRPC client to query the x/bank service.
26
    bankClient := banktypes.NewQueryClient(grpcConn)
27
    bankRes, err := bankClient.Balance(
28
        context.Background(),
29
        &banktypes.QueryBalanceRequest{Address: myAddress, Denom: denom},
30
    )
31
    if err != nil {
32
        return err
33
    }
34
​
35
    fmt.Println(bankRes.GetBalance()) // Prints the account balance
36
​
37
    return nil
38
}
Copied!
You can replace the query client (here we are using x/bank's) with one generated from any other Protobuf service.
Query for historical state using Go
Querying for historical blocks is done by adding the block height metadata in the gRPC request.
1
import (
2
    "context"
3
    "fmt"
4
​
5
    "google.golang.org/grpc"
6
    "google.golang.org/grpc/metadata"
7
​
8
    grpctypes "github.com/cosmos/cosmos-sdk/types/grpc"
9
    "github.com/cosmos/cosmos-sdk/types/tx"
10
)
11
​
12
func queryState() error {
13
    // --snip--
14
​
15
    var header metadata.MD
16
    bankRes, err = bankClient.Balance(
17
        metadata.AppendToOutgoingContext(context.Background(), grpctypes.GRPCBlockHeightHeader, "12"), // Add metadata to request
18
        &banktypes.QueryBalanceRequest{Address: myAddress, Denom: denom},
19
        grpc.Header(&header), // Retrieve header from response
20
    )
21
    if err != nil {
22
        return err
23
    }
24
    blockHeight = header.Get(grpctypes.GRPCBlockHeightHeader)
25
​
26
    fmt.Println(blockHeight) // Prints the block height (12)
27
​
28
    return nil
29
}
Copied!
​
Using the REST Endpoints
As described in the gRPC guide, all gRPC services on the Cosmos SDK are made available for more convenient REST-based queries through gRPC-gateway. The format of the URL path is based on the Protobuf service method's full-qualified name, but may contain small customizations so that final URLs look more idiomatic. For example, the REST endpoint for the cosmos.bank.v1beta1.Query/AllBalances method is GET /cosmos/bank/v1beta1/balances/{address}. Request arguments are passed as query parameters.
As a concrete example, the curl command to make balances request is:
1
curl \
2
    -X GET \
3
    -H "Content-Type: application/json" \
4
    http://localhost:1317/cosmos/bank/v1beta1/balances/$MY_ADDRESS
Copied!
Make sure to replace localhost:1317 with the REST endpoint of your node, configured under the api.address field.
The list of all available REST endpoints is available as a Swagger specification file, it can be viewed at localhost:1317/swagger. Make sure that the api.swagger field is set to true in your app.toml file.
Query for historical state using REST
Querying for historical state is done using the HTTP header x-cosmos-block-height. For example, a curl command would look like:
1
curl \
2
    -X GET \
3
    -H "Content-Type: application/json" \
4
    -H "x-cosmos-block-height: 10000"
5
    http://localhost:1317/cosmos/bank/v1beta1/balances/$MY_ADDRESS
Copied!
Assuming the state at that block has not yet been pruned by the node, this query should return a non-empty response.
Cross-Origin Resource Sharing (CORS)
​CORS policies are not enabled by default to help with security. If you would like to use the rest-server in a public environment we recommend you provide a reverse proxy, this can be done with nginx. For testing and development purposes there is an enabled-unsafe-cors field inside app.toml.
Join the Groot testnet
Next - Guide
Migrations
Last modified 8mo ago
Copy link
Contents
Interacting with the Node
Using the CLI
Using gRPC
Using the REST Endpoints
Interacting with the Node

Using the CLI

Using gRPC

grpcurl

Programmatically via Go

​

Using the REST Endpoints

Query for historical state using REST

Cross-Origin Resource Sharing (CORS)
