Introduction

Introduction
junod is a command line client for the Juno network. Juno users can use junod to send transactions to the Juno network and query the blockchain data.
See here for instructions on installing junod.
Working Directory
The default working directory for the junod is $HOME/.juno, which is mainly used to store configuration files and blockchain data. The Juno key data is saved in the working directory of junod. You can also specify the junod working directory by using the --home flag when executing junod. 
Connecting to a Full-Node
By default, junod uses tcp://localhost:26657 as the RPC address to connect to the Juno network. This default configuration assumes that the machine executing junod is running as a full-node.
The RPC address can be specified to connect to any full-node with an exposed RPC port by adding the --node flag when executing junod
Global Flags
GET Commands
All GET commands have the following global flags:
Name, shorthand
type
Required
Default Value
Description
--chain-id
string
​
​
The network Chain ID
--home
string
​
$HOME/.juno
Directory for config and data
--trace
string
​
​
Print out full stack trace on errors
--log_format
string
​
plain
Logging format (json | plain)
POST Commands
All POST commands have the following global flags:
Name, shorthand
type
Required
Default
Description
--account-number
int
​
0
AccountNumber to sign the tx
--broadcast-mode
string
​
sync
Transaction broadcasting mode (sync | async | block)
--dry-run
bool
​
false
Ignore the --gas flag and perform a simulation of a transaction, but don't broadcast it
--fees
string
​
​
Fees to pay along with transaction
--from
string
​
​
Name of private key with which to sign
--gas
string
​
200000
Gas limit to set per-transaction; set to "simulate" to calculate required gas automatically
--gas-adjustment
float
​
1
Adjustment factor to be multiplied against the estimate returned by the tx simulation; if the gas limit is set
--gas-prices
string
​
​
Gas prices in decimal format to determine the transaction fee
--generate-only
bool
​
false
Build an unsigned transaction and write it to STDOUT
--help, -h
string
​
​
Print help message
--keyring-backend
string
​
os
Select keyring's backend
--ledger
bool
​
false
Use a connected Ledger device
--memo
string
​
​
Memo to send along with transaction
--node
string
​
tcp://localhost:26657
<host>:<port> to tendermint rpc interface for this chain
--offline
string
​
​
Offline mode (does not allow any online functionality)
--sequence
int
​
0
Sequence number to sign the tx
--sign-mode
string
​
​
Choose sign mode (direct | amino-json), this is an advanced feature
--trust-node
bool
​
true
Don't verify proofs for responses
--yes
bool
​
true
Skip tx broadcasting prompt confirmation
--chain-id
string
​
​
The network Chain ID
--home
string
​
$HOME/.juno
Directory for config and data
--trace
string
​
​
Print out full stack trace on errors
Module Commands
Subcommand
Description
​bank​
Bank subcommands for querying accounts and sending coins etc.
​debug​
Debug subcommands
​distribution​
Distribution subcommands for rewards management
​gov​
Governance and voting subcommands
​keys​
Keys allows you to manage your local keystore for tendermint
​params​
Query parameters of modules
​slashing​
Slashing subcommands
​staking​
Staking subcommands for validators and delegators
​status​
Query remote node for status
​tendermint​
Tendermint state querying subcommands
​tx​
Tx subcommands
​upgrade​
Software Upgrade subcommands
​wasm​
Interact with smart contracts

Nodes & Validators - Previous

Deploying a Node on Akash

Next - Command-Line Interface (CLI)

Useful CLI Commands

Last modified 1mo ago

Copy link

Contents

Introduction

Working Directory

Connecting to a Full-Node

Global Flags

Module Commands