Nolus Validator Tools & Infrastructure Documentation
Complete infrastructure toolkit for Nolus validators and developers. Access our professional-grade services including RPC nodes, API endpoints, daily snapshots, and real-time metrics. Our nolus 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.
Catch the latest block faster or recover from a missed upgrade or corrupted database by using our daily snapshots.
ⓘ  Â
Snapshots allows a new node to join the network by recovering application state from a backup file.
Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
snapshot server is periodically beeing state-synced.
Snapshots are taken automatically every 12 hours
| Pruning | Indexer | Version Tag |
|---|---|---|
107/0/13 | null | v0.6.3 |
| Block | Age | Download |
|---|---|---|
12616523 | 9 hours | snapshot (4.0 GB) |
ⓘ  Â
You can query api.lavenderfive.com/snapshots/nolus to double check the latest state if the above information doesnt display.
#Instructions
#Quick setup
ⓘ  Â
One liner to get moving quickly
sudo systemctl stop nolusd
cp $HOME/.nolusd/data/priv_validator_state.json $HOME/.nolusd/priv_validator_state.json.backup
rm -rf $HOME/.nolusd/data
curl -L https://snapshots.lavenderfive.com/snapshots/nolus/nolus_12616523.tar.zst | tar -Ilz4 -xf - -C $HOME/.nolusd
mv $HOME/.nolusd/priv_validator_state.json.backup $HOME/.nolusd/data/priv_validator_state.json
sudo systemctl start nolusd && sudo journalctl -u nolusd -f --no-hostname -o cat
#Stop nolusd and reset the data
sudo systemctl stop nolusd
cp $HOME/.nolusd/data/priv_validator_state.json $HOME/.nolusd/priv_validator_state.json.backup
rm -rf $HOME/.nolusd/data
#Download latest snapshot
curl -L https://snapshots.lavenderfive.com/snapshots/nolus/nolus_12616523.tar.zst | tar -Ilz4 -xf - -C $HOME/.nolusd
mv $HOME/.nolusd/priv_validator_state.json.backup $HOME/.nolusd/data/priv_validator_state.json
#Restart nolusd and check the log
sudo systemctl start nolusd && sudo journalctl -u nolusd -f --no-hostname -o cat
Chain ID:
The unique identifier for the blockchain network.
pirin-1Latest Version:
The latest version of the chain software.
v0.6.3Github:
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/nolus
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/nolus
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.
nolus.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/nolus/websocket
© 2022 Lavender.Five Nodes. All rights reserved.