Node RequirementsTo use the To use an external RPC, update the 
query and tx commands, your evmd node must either:- Be fully synced with the network you’re interacting with, OR
- Be configured to use an external RPC endpoint in ~/.evmd/config/client.toml
node field to point to a public or private RPC endpoint.Global Flags
These flags are available for all commands:| Flag | Description | Default | 
|---|---|---|
| -b, --broadcast-mode | Transaction broadcasting mode (sync|async) | sync | 
| --chain-id | Specify Chain ID for sending Tx | |
| --fees | Fees to pay along with transaction (e.g., 10atest) | |
| --from | Name or address of private key with which to sign | |
| --gas-adjustment | Adjustment factor to multiply against the estimate returned by tx simulation | 1 | 
| --gas-prices | Gas prices to determine the transaction fee (e.g., 10atest) | |
| --home | Directory for config and data | ~/.evmd | 
| --keyring-backend | Select keyring’s backend | os | 
| --log_format | The logging format (json|plain) | plain | 
| --log_level | The logging level | info | 
| --log_no_color | Disable colored logs | |
| --node | <host>:<port> to CometBFT RPC interface | tcp://localhost:26657 | 
| --trace | Print out full stack trace on errors | 
Commands
- Node Operations
- Key Management
- EVM Queries
- ERC20 Queries
- Feemarket Queries
- Precisebank Queries
- Cosmos SDK Queries
- EVM Transactions
- ERC20 Transactions
- Cosmos SDK Transactions
- Advanced Commands
Examples
Complete Workflows
- Account Setup
- Query Examples
- Transactions
Configuration
- Configuration directory: ~/.evmd/
- Key storage: Managed by the keyring backend (os, file, test)
- Node configuration: ~/.evmd/config/config.toml
- App configuration: ~/.evmd/config/app.toml
If you use the 
--home flag upon initializing the light client, the root/config directory will be generated there