GLCstakedSUI Network - complete guide to run a Node & Validator
SUI is a layer 1 blockchain designed by Mysten Labs from the ground up in smart contract specific language called MOVE This guide will go over installing a Full Node and Validator from scratch in order to run a Sui network node, assumes a fresh install of Ubuntu 20.04LTS. Hardware Requirements: Node Requirements: Full node requirements are lower, but storage can be expected to increase over time CPUs: 2 RAM: 8GB Storage: 50GB Validator Requirements: Validators perform work and deal with chain...
GLCstakedEasy Guide to Gnosischain Validator - with Lighthouse
This guide is help you set up a Gnosischain Validator, this will cover the full set up on a local device installed with Ubuntu 20.04 LTS. We will be using Lighthouse for consensus layer client and Nethermind for our Execution layer client. Gnosischain merge is on the horizon, this guide is intended to be merge ready the set up will cover steps and configuration needed to run post merge, and today. Gnosischain is using Ethereum Proof of Stake consensus with the Beacon chain to select validator...
GLCstakedAztec Sequencer- Public Testnet
This is a full guide to setup an Aztec Sequencer on Public Testnet, using Docker Compose and your own Sepolia Ethereum node (same device)Aztec Network- A privacy first Layer 2 on EthereumAztec is a zk-rollup allowing developers to build decentralised applications that preserve user privacy without compromising security or decentralisation. Aztec team co-developed Plonk, a highly efficient and universal zk-SNARK proving system that has since become foundational across the ZK ecosystem. Plonk’s...
$ETH Solo Staker #stakefromhome
GLCstakedSUI Network - complete guide to run a Node & Validator
SUI is a layer 1 blockchain designed by Mysten Labs from the ground up in smart contract specific language called MOVE This guide will go over installing a Full Node and Validator from scratch in order to run a Sui network node, assumes a fresh install of Ubuntu 20.04LTS. Hardware Requirements: Node Requirements: Full node requirements are lower, but storage can be expected to increase over time CPUs: 2 RAM: 8GB Storage: 50GB Validator Requirements: Validators perform work and deal with chain...
GLCstakedEasy Guide to Gnosischain Validator - with Lighthouse
This guide is help you set up a Gnosischain Validator, this will cover the full set up on a local device installed with Ubuntu 20.04 LTS. We will be using Lighthouse for consensus layer client and Nethermind for our Execution layer client. Gnosischain merge is on the horizon, this guide is intended to be merge ready the set up will cover steps and configuration needed to run post merge, and today. Gnosischain is using Ethereum Proof of Stake consensus with the Beacon chain to select validator...
GLCstakedAztec Sequencer- Public Testnet
This is a full guide to setup an Aztec Sequencer on Public Testnet, using Docker Compose and your own Sepolia Ethereum node (same device)Aztec Network- A privacy first Layer 2 on EthereumAztec is a zk-rollup allowing developers to build decentralised applications that preserve user privacy without compromising security or decentralisation. Aztec team co-developed Plonk, a highly efficient and universal zk-SNARK proving system that has since become foundational across the ZK ecosystem. Plonk’s...
$ETH Solo Staker #stakefromhome
Subscribe to GLCstaked
Subscribe to GLCstaked
<100 subscribers
<100 subscribers
Share Dialog
Share Dialog
Lava Protocol, a crypto-market which powers a decentralized RPC layer for Web3. How to setup a Validator node with Cosmovisor
This Guide will focus on the setup of a Validator node which is also a Full node for Lava chain, with cosmovisor
Cosmovisor: Cosmovisor is a tool for automating the upgrades process. it runs as a small process manager for Cosmos SDK application binaries that monitors the governance module for incoming chain upgrade proposals and can automatically download new binaries.
A validator can be setup without this tool, where the binaries must be updated manually
Hardware Requirements: 4vCPU/8GB/100GB SSD OS: Ubuntu 20.04LTS
2.5m+ users, 30+ chains supported, 70b+ RPC calls - you are using Lava without knowing. Lava is the infrastructure that powers access to all blockchains, enabling essential onchain actions such as minting, swapping and transacting.
Switch to root user, can exit any time with exit
sudo -i
Update your system and repositories
apt update && apt upgrade -y
Install Dependencies
The following packages required for lava node
apt install logrotate git jq sed wget curl coreutils systemd unzip -y
Install GO
Download and unpack installation file to /usr/local/
ver="1.19.4"
wget "https://golang.org/dl/go$ver.linux-amd64.tar.gz"
rm -rf /usr/local/go
tar -C /usr/local -xzf "go$ver.linux-amd64.tar.gz"
rm "go$ver.linux-amd64.tar.gz"
Add to PATH
echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.bash_profile
source $HOME/.bash_profile
Confirm installation with go version and echo $PATH
Firewall Settings
Outbound - allow all traffic. Inbound - open the following ports: 1317 - REST, 26657 - TENDERMINT_RPC, 26656 - Cosmos
sudo ufw allow 1317
sudo ufw allow 26657
sudo ufw allow 26656
sudo ufw allow ssh
sudo ufw enable
Default setting ufw is to allow all outgoing, if your server is remote ensure to allow 22 for ssh.
git clone https://github.com/lavanet/lava-config.git
cd lava-config/testnet-1
Copy Config Files
mkdir -p $HOME/.lava/config
cp default_lavad_config_files/* $HOME/.lava/config
Copy the genesis.json file to the Lava config folder
cp genesis_json/genesis.json $HOME/.lava/config/
from home
go install github.com/cosmos/cosmos-sdk/cosmovisor/cmd/cosmovisor@v1.0.0
Create the Cosmovisor folder and copy config files to it
mkdir -p $HOME/.lava/cosmovisor
mkdir -p $HOME/.lava/data
Download the latest cosmovisor-upgrades from S3
wget https://lava-binary-upgrades.s3.amazonaws.com/testnet/cosmovisor-upgrades/cosmovisor-upgrades.zip
unzip cosmovisor-upgrades.zip
cp -r cosmovisor-upgrades/* $HOME/.lava/cosmovisor
Set environment variables
echo "# Setup Cosmovisor" >> ~/.bash_profile
echo "export DAEMON_NAME=lavad" >> ~/.bash_profile
echo "export CHAIN_ID=lava-testnet-1" >> ~/.bash_profile
echo "export DAEMON_HOME=$HOME/.lava" >> ~/.bash_profile
echo "export DAEMON_ALLOW_DOWNLOAD_BINARIES=true" >> ~/.bash_profile
echo "export DAEMON_LOG_BUFFER_SIZE=512" >> ~/.bash_profile
echo "export DAEMON_RESTART_AFTER_UPGRADE=true" >> ~/.bash_profile
echo "export UNSAFE_SKIP_BACKUP=true" >> ~/.bash_profile
source ~/.bash_profile
Initialize the chain
from lava-config/testnet-1 from home?
$HOME/lava_validator/cosmovisor/genesis/bin/lavad init \
my-node \
--chain-id lava-testnet-1 \
--home $HOME/lava_validator \
--overwrite cp genesis_json/genesis.json $HOME/.lava/config/genesis.json
this will create an error, but ignore for now
confirm installation with cosmovisor version
echo "[Unit]
Description=Cosmovisor daemon
After=network-online.target
[Service]
Environment="DAEMON_NAME=lavad"
Environment="DAEMON_HOME=$HOME/.lava"
Environment="DAEMON_RESTART_AFTER_UPGRADE=true"
Environment="DAEMON_ALLOW_DOWNLOAD_BINARIES=true"
Environment="DAEMON_LOG_BUFFER_SIZE=512"
Environment="UNSAFE_SKIP_BACKUP=true"
User=$USER
ExecStart=$HOME/go/bin/cosmovisor start --home=$HOME/.lava
Restart=always
RestartSec=3
LimitNOFILE=infinity
LimitNPROC=infinity
[Install]
WantedBy=multi-user.target
" >cosmovisor.service
sudo mv cosmovisor.service /lib/systemd/system/cosmovisor.service
Optional: add seed node with the flag --p2p.seeds $seed_node
systemctl daemon-reload
systemctl enable cosmovisor.service
systemctl start cosmovisor
Logs
sudo journalctl -u cosmovisor -f
Without any seeds node or addrbook it can take a while to find peers and start syncing.
Lava Protocol, a crypto-market which powers a decentralized RPC layer for Web3. How to setup a Validator node with Cosmovisor
This Guide will focus on the setup of a Validator node which is also a Full node for Lava chain, with cosmovisor
Cosmovisor: Cosmovisor is a tool for automating the upgrades process. it runs as a small process manager for Cosmos SDK application binaries that monitors the governance module for incoming chain upgrade proposals and can automatically download new binaries.
A validator can be setup without this tool, where the binaries must be updated manually
Hardware Requirements: 4vCPU/8GB/100GB SSD OS: Ubuntu 20.04LTS
2.5m+ users, 30+ chains supported, 70b+ RPC calls - you are using Lava without knowing. Lava is the infrastructure that powers access to all blockchains, enabling essential onchain actions such as minting, swapping and transacting.
Switch to root user, can exit any time with exit
sudo -i
Update your system and repositories
apt update && apt upgrade -y
Install Dependencies
The following packages required for lava node
apt install logrotate git jq sed wget curl coreutils systemd unzip -y
Install GO
Download and unpack installation file to /usr/local/
ver="1.19.4"
wget "https://golang.org/dl/go$ver.linux-amd64.tar.gz"
rm -rf /usr/local/go
tar -C /usr/local -xzf "go$ver.linux-amd64.tar.gz"
rm "go$ver.linux-amd64.tar.gz"
Add to PATH
echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.bash_profile
source $HOME/.bash_profile
Confirm installation with go version and echo $PATH
Firewall Settings
Outbound - allow all traffic. Inbound - open the following ports: 1317 - REST, 26657 - TENDERMINT_RPC, 26656 - Cosmos
sudo ufw allow 1317
sudo ufw allow 26657
sudo ufw allow 26656
sudo ufw allow ssh
sudo ufw enable
Default setting ufw is to allow all outgoing, if your server is remote ensure to allow 22 for ssh.
git clone https://github.com/lavanet/lava-config.git
cd lava-config/testnet-1
Copy Config Files
mkdir -p $HOME/.lava/config
cp default_lavad_config_files/* $HOME/.lava/config
Copy the genesis.json file to the Lava config folder
cp genesis_json/genesis.json $HOME/.lava/config/
from home
go install github.com/cosmos/cosmos-sdk/cosmovisor/cmd/cosmovisor@v1.0.0
Create the Cosmovisor folder and copy config files to it
mkdir -p $HOME/.lava/cosmovisor
mkdir -p $HOME/.lava/data
Download the latest cosmovisor-upgrades from S3
wget https://lava-binary-upgrades.s3.amazonaws.com/testnet/cosmovisor-upgrades/cosmovisor-upgrades.zip
unzip cosmovisor-upgrades.zip
cp -r cosmovisor-upgrades/* $HOME/.lava/cosmovisor
Set environment variables
echo "# Setup Cosmovisor" >> ~/.bash_profile
echo "export DAEMON_NAME=lavad" >> ~/.bash_profile
echo "export CHAIN_ID=lava-testnet-1" >> ~/.bash_profile
echo "export DAEMON_HOME=$HOME/.lava" >> ~/.bash_profile
echo "export DAEMON_ALLOW_DOWNLOAD_BINARIES=true" >> ~/.bash_profile
echo "export DAEMON_LOG_BUFFER_SIZE=512" >> ~/.bash_profile
echo "export DAEMON_RESTART_AFTER_UPGRADE=true" >> ~/.bash_profile
echo "export UNSAFE_SKIP_BACKUP=true" >> ~/.bash_profile
source ~/.bash_profile
Initialize the chain
from lava-config/testnet-1 from home?
$HOME/lava_validator/cosmovisor/genesis/bin/lavad init \
my-node \
--chain-id lava-testnet-1 \
--home $HOME/lava_validator \
--overwrite cp genesis_json/genesis.json $HOME/.lava/config/genesis.json
this will create an error, but ignore for now
confirm installation with cosmovisor version
echo "[Unit]
Description=Cosmovisor daemon
After=network-online.target
[Service]
Environment="DAEMON_NAME=lavad"
Environment="DAEMON_HOME=$HOME/.lava"
Environment="DAEMON_RESTART_AFTER_UPGRADE=true"
Environment="DAEMON_ALLOW_DOWNLOAD_BINARIES=true"
Environment="DAEMON_LOG_BUFFER_SIZE=512"
Environment="UNSAFE_SKIP_BACKUP=true"
User=$USER
ExecStart=$HOME/go/bin/cosmovisor start --home=$HOME/.lava
Restart=always
RestartSec=3
LimitNOFILE=infinity
LimitNPROC=infinity
[Install]
WantedBy=multi-user.target
" >cosmovisor.service
sudo mv cosmovisor.service /lib/systemd/system/cosmovisor.service
Optional: add seed node with the flag --p2p.seeds $seed_node
systemctl daemon-reload
systemctl enable cosmovisor.service
systemctl start cosmovisor
Logs
sudo journalctl -u cosmovisor -f
Without any seeds node or addrbook it can take a while to find peers and start syncing.
No activity yet