Kava Validator Tools & Infrastructure Documentation
Complete infrastructure toolkit for Kava validators and developers. Access our professional-grade services including RPC nodes, API endpoints, daily snapshots, and real-time metrics. Our kava infrastructure features optimized pruning configurations, automated backups, and comprehensive monitoring solutions. Supporting both mainnet and testnet environments with dedicated endpoints, state-sync services, and detailed technical documentation for seamless network participation and development.
With our state sync services you will be able to catch up latest chain block in matter of minutes
ⓘ  Â
State Sync allows a new node to join the network by fetching a snapshot of the application state
at a recent height instead of fetching and replaying all historical blocks. Since the
application state is generally much smaller than the blocks, and restoring it is much
faster than replaying blocks, this can reduce the time to sync with the network from days to minutes.
#Instructions
#Stop kava and reset database
sudo systemctl stop kava
cp $HOME/.kava/data/priv_validator_state.json $HOME/.kava/priv_validator_state.json.backup
kava tendermint unsafe-reset-all --home $HOME/.kava --keep-addr-book
#Get and configure the state sync information
STATE_SYNC_RPC=https://rpc.cosmos.directory:443/kava
BACKUP_RPC=https://rpc.lavenderfive.com:443/kava
LATEST_HEIGHT=$(curl -s $STATE_SYNC_RPC/block | jq -r .result.block.header.height)
BLOCK_HEIGHT=$(echo LATEST_HEIGHT | awk '{print $1 - ($1 % 6000)}'); \
TRUST_HASH=$(curl -s "$STATE_SYNC_RPC/block?height=$BLOCK_HEIGHT" | jq -r .result.block_id.hash)
SEEDS="[email protected]:13956,ebc272824924ea1a27ea3183dd0b9ba713494f83@kava-mainnet-seed.autostake.com:26656,7ab4b78fbe5ee9e3777b21464a3162bd4cc17f57@seed-kava-01.stakeflow.io:1206,[email protected]:26656,[email protected]:16677"
echo -e "Modifying $HOME/.kava/config/config.toml based on the following values:"
echo -e "RPC Address: $STATE_SYNC_RPC"
echo -e "Latest Block Height: $LATEST_HEIGHT"
echo -e "Sync Block Height: $BLOCK_HEIGHT"
echo -e "Trust Hash: $TRUST_HASH"
sed -i \
-e "s|^enable *=.*|enable = true|" \
-e "s|^rpc_servers *=.*|rpc_servers = \"$STATE_SYNC_RPC,$BACKUP_RPC\"|" \
-e "s|^trust_height *=.*|trust_height = $BLOCK_HEIGHT|" \
-e "s|^trust_hash *=.*|trust_hash = \"$TRUST_HASH\"|" \
-e "s|^seeds *=.*|seeds = \"$SEEDS\"|" \
$HOME/.kava/config/config.toml
mv $HOME/.kava/priv_validator_state.json.backup $HOME/.kava/data/priv_validator_state.json
#Download latest wasm
ⓘ  Â
Currently state sync does not support copy of the `wasm` folder. Therefore, you will have to download it manually.
curl -L https://snapshots.lavenderfive.com/wasm/kava/wasmonly.tar.lz4 | lz4 -dc - | tar -xf - -C $HOME/.kava
#Restart kava and check the log
sudo systemctl restart kava && sudo journalctl -u kava -f --no-hostname -o cat
Chain ID:
The unique identifier for the blockchain network.
kava_2222-10Latest Version:
The latest version of the chain software.
v0.26.0Github:
The Github repository hosting the code for the network in question.
Public endpoints
Public endpoints are rate limited but can be used for basic CLI usage, node syncing or testing environments. Request an API key for enhanced access limits, we offer free trial periods of 14 days and cheap shared access plans from $50 a month.
REST/LCD
REST endpoint for querying blockchain data through the REST framework. Often available for Cosmos chains but also the main framework for Aleo as an example.
rest.lavenderfive.com:443/kava
RPC
Remote Procedure Call endpoint for the consensus client of a blockchain. This is not an EVM endpoint (we call this json RPC) but the main framework for blockchain frameworks like Cosmos, Aptos, Sui and Near.
rpc.lavenderfive.com:443/kava
gRPC
High-performance RPC endpoint for blockchain communication using the Google gRPC framework. This is often standard gRPC and not the "WEB" framework which is sometimes also accesible.
kava.lavenderfive.com:443
WebSocket
WebSocket endpoint for real-time blockchain updates of the consensus client. This is not the EVM websocket integration, we name and expose that separately. WS is commonly available for Cosmos and Move networks that also expose a REST endpoint.
wss://rpc.lavenderfive.com:443/kava/websocket
Json-RPC
JSON-RPC endpoint for EVM interactions and queries. This is the main endpoint for Ethereum like networks but might co-exist alongside a consensus RPCs on Cosmos like networks that have a separate consensus endpoint like Berachain, Story and Evmos.
jsonrpc.lavenderfive.com:443/kava
Json-RPC (websocket)
The websocket interface for the json-RPC EVM endpoint to listen/subscribe to event feeds.
wss://jsonrpc.lavenderfive.com:443/kava/ws
© 2022 Lavender.Five Nodes. All rights reserved.