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
Setup a full Node for StarkNet, for direct access to the StarkNet layer 2 network. Using Docker compose with Pathfinder or Juno clients.
(document last update: 1/8/23)
StarkNet is a permissionless & decentralised ZK-Rollup which operates as Layer 2 over Ethereum. supporting scale, while preserving the security of L1 Ethereum by producing STARK proofs off-chain, and then verifying those proofs on-chain.
Full Node: a full node, this is the L2 equivalent of a full node on Ethereum, which connects to other full nodes via peer-to-peer networking, stores full blockchain data and verifies all blocks and states. There are a few clients for a full node on StarkNet
Pathfinder: by Eqlabs is a full node implementation written in Rust.
Juno: by Nethermind is a full node implementation written in Golang.
Hardware Requirements: Recommended RAM 8GB, CPU 4core, Storage: 100GB (starting)
Ubuntu 20.04 LTS installed
Access to an Ethereum Full Node
Ports:
Juno: RPC 6060, ws 6061,
Pathfinder: RPC 9545, ws 9546
for easy deployment, you can run this script (based of this guide), installs dependencies, select which client and Ethereum endpoint and auto configures the node for you based on client selection
https://github.com/GLCNI/RPC-node-deployments/tree/main#starknet
Install Prerequisite software
Update System
sudo apt update && sudo apt upgrade -y
Install Docker & Docker-compose
Remove any existing installation
sudo apt-get remove docker docker-engine docker.io containerd runc
Install Docker & Docker-compose via script
sudo apt install curl -y
curl -fsSL https://get.docker.com -o get-docker.sh
sh get-docker.sh
Remove the script, and add your user to the docker group, for use without sudo
sudo rm -r get-docker.sh
sudo usermod -aG docker $USER
Requires a Restart to work, then check installed with
docker --version
docker compose version
StarkNet requires a connection to an Ethereum Node, as it is a layer 2 on top of Ethereum. There are a few ways to achieve this
Set up an Ethereum full node
If you don’t have access to a full node for Ethereum, which consists of and Execution and Consensus client, You can use an easy node deployment tool such as Nethermind Sedge.
Note: it may take a while to sync depending on hardware used (quality of SSD & RAM), from 12 hours to a few days.
Host node on the same device
You shouldn’t have to do anything for ports or on firewall. The following are the arguments and changes to the docker-compose.yml file for later in Step 3.
#for Pathfinder
--ethereum.url 'http://localhost:8545'
or
--ethereum.url 'ws://localhost:8546'
#For Juno (requires ws)
--eth-node 'ws://localhost:8546'
NOTE: 8545 is the default RPC port, 8546 is the default ws port, if Ethereum node is configured for a different port then change accordingly.
Sedge Users: If you used Sedge to deploy the eth-node the default may be different you can find the port here under /<sedge-working-folder-path>/docker-compose.yml
Networks: If you are using a local node deployed via Sedge, I found in order to get it too work I had to add the following to `docker-compose.yml`, under ` starknet-node:` service
network_mode: "host"
Node on a separate (local) device
Normally: Keep 8545 (or 8000-9000 for CL) closed except for the trusted machines - this is the JSON RPC port which gives admin access to the node.
You are advised to open the port to your StarkNet node IP like so, from your Ethereum Node. were going to allow only to our own IP. What this does is exposes our Ethereum node only to a trusted device hosting the L2 node.
sudo ufw allow <PORT> from <ip of destination device>
sudo ufw enable
If you still have problems connecting, you may need to Port forward from your router. This will vary based on your ISP and router, check the manual. Option 2: Use a 3rd party service (not recommended) You can get an L1 endpoint URL from providers such as Alchemy/Infura/ and others, note that these are centralised endpoints where the node is hosted by someone else. StarkNet calls to L1 node generally exceed the free tier with Infura or similar services, but this is useful for testing deployment and initial syncing, but for production use I would not recommend using unless paying for a higher tier, in which case it would make sense just to host your own node. URL will look similar to this This is the to be used in configuration later NOTE: for Juno Client use the websocket endpoint which will look like this 3. Configure Node Make a working directory mkdir -p starknet-node/data Grant permissions to folder sudo chown -R 1000:1000 starknet-node/data Create configuration file for docker compose nano starknet-node/docker-compose.yml Now copy the chosen client configuration templates into this file, replace accordingly Option 1: Configure for Pathfinder client Find the latest release from here: version: '3.3' services: starknet-node: image: 'eqlabs/pathfinder:v0.6.7' user: 1000:1000 restart: always stop_grace_period: 30s network_mode: "host" volumes: - /home/$USER/starknet-node/data:/usr/share/pathfinder/data ports: - '0.0.0.0:9545:9545' - '0.0.0.0:9546:9546' command: --data-directory "/usr/share/pathfinder/data" --ethereum.url "<ETH-NODE-ADDRESS>" --network "mainnet" --rpc.websocket --http-rpc "0.0.0.0:9545" environment: - RUST_LOG=info - PATHFINDER_RPC_WEBSOCKET=0.0.0.0:9546 logging: driver: json-file options: max-size: 10m max-file: "10" Option 2: Configure for Juno client Find the latest release from here: version: '3.3' services: starknet-node: image: 'nethermindeth/juno:v0.4.0' user: 1000:1000 restart: always stop_grace_period: 30s network_mode: "host" volumes: - /home/$USER/starknet-node/data:/var/lib/juno ports: - '0.0.0.0:6060:6060' - '0.0.0.0:6061:6061' command: --db-path '/var/lib/juno' --eth-node '<ETH-NODE-ADDRESS>' --log-level 'info' --network 'mainnet' --http-port '6060' --ws-port '6061' logging: driver: json-file options: max-size: 10m max-file: "10" 4. Run the node cd starknet-node docker compose up -d view logs docker compose logs -f starknet-node If your node can successfully connect to an L1 endpoint, it will start to sync blocks Other commands
Setup a full Node for StarkNet, for direct access to the StarkNet layer 2 network. Using Docker compose with Pathfinder or Juno clients.
(document last update: 1/8/23)
StarkNet is a permissionless & decentralised ZK-Rollup which operates as Layer 2 over Ethereum. supporting scale, while preserving the security of L1 Ethereum by producing STARK proofs off-chain, and then verifying those proofs on-chain.
Full Node: a full node, this is the L2 equivalent of a full node on Ethereum, which connects to other full nodes via peer-to-peer networking, stores full blockchain data and verifies all blocks and states. There are a few clients for a full node on StarkNet
Pathfinder: by Eqlabs is a full node implementation written in Rust.
Juno: by Nethermind is a full node implementation written in Golang.
Hardware Requirements: Recommended RAM 8GB, CPU 4core, Storage: 100GB (starting)
Ubuntu 20.04 LTS installed
Access to an Ethereum Full Node
Ports:
Juno: RPC 6060, ws 6061,
Pathfinder: RPC 9545, ws 9546
for easy deployment, you can run this script (based of this guide), installs dependencies, select which client and Ethereum endpoint and auto configures the node for you based on client selection
https://github.com/GLCNI/RPC-node-deployments/tree/main#starknet
Install Prerequisite software
Update System
sudo apt update && sudo apt upgrade -y
Install Docker & Docker-compose
Remove any existing installation
sudo apt-get remove docker docker-engine docker.io containerd runc
Install Docker & Docker-compose via script
sudo apt install curl -y
curl -fsSL https://get.docker.com -o get-docker.sh
sh get-docker.sh
Remove the script, and add your user to the docker group, for use without sudo
sudo rm -r get-docker.sh
sudo usermod -aG docker $USER
Requires a Restart to work, then check installed with
docker --version
docker compose version
StarkNet requires a connection to an Ethereum Node, as it is a layer 2 on top of Ethereum. There are a few ways to achieve this
Set up an Ethereum full node
If you don’t have access to a full node for Ethereum, which consists of and Execution and Consensus client, You can use an easy node deployment tool such as Nethermind Sedge.
Note: it may take a while to sync depending on hardware used (quality of SSD & RAM), from 12 hours to a few days.
Host node on the same device
You shouldn’t have to do anything for ports or on firewall. The following are the arguments and changes to the docker-compose.yml file for later in Step 3.
#for Pathfinder
--ethereum.url 'http://localhost:8545'
or
--ethereum.url 'ws://localhost:8546'
#For Juno (requires ws)
--eth-node 'ws://localhost:8546'
NOTE: 8545 is the default RPC port, 8546 is the default ws port, if Ethereum node is configured for a different port then change accordingly.
Sedge Users: If you used Sedge to deploy the eth-node the default may be different you can find the port here under /<sedge-working-folder-path>/docker-compose.yml
Networks: If you are using a local node deployed via Sedge, I found in order to get it too work I had to add the following to `docker-compose.yml`, under ` starknet-node:` service
network_mode: "host"
Node on a separate (local) device
Normally: Keep 8545 (or 8000-9000 for CL) closed except for the trusted machines - this is the JSON RPC port which gives admin access to the node.
You are advised to open the port to your StarkNet node IP like so, from your Ethereum Node. were going to allow only to our own IP. What this does is exposes our Ethereum node only to a trusted device hosting the L2 node.
sudo ufw allow <PORT> from <ip of destination device>
sudo ufw enable
If you still have problems connecting, you may need to Port forward from your router. This will vary based on your ISP and router, check the manual. Option 2: Use a 3rd party service (not recommended) You can get an L1 endpoint URL from providers such as Alchemy/Infura/ and others, note that these are centralised endpoints where the node is hosted by someone else. StarkNet calls to L1 node generally exceed the free tier with Infura or similar services, but this is useful for testing deployment and initial syncing, but for production use I would not recommend using unless paying for a higher tier, in which case it would make sense just to host your own node. URL will look similar to this This is the to be used in configuration later NOTE: for Juno Client use the websocket endpoint which will look like this 3. Configure Node Make a working directory mkdir -p starknet-node/data Grant permissions to folder sudo chown -R 1000:1000 starknet-node/data Create configuration file for docker compose nano starknet-node/docker-compose.yml Now copy the chosen client configuration templates into this file, replace accordingly Option 1: Configure for Pathfinder client Find the latest release from here: version: '3.3' services: starknet-node: image: 'eqlabs/pathfinder:v0.6.7' user: 1000:1000 restart: always stop_grace_period: 30s network_mode: "host" volumes: - /home/$USER/starknet-node/data:/usr/share/pathfinder/data ports: - '0.0.0.0:9545:9545' - '0.0.0.0:9546:9546' command: --data-directory "/usr/share/pathfinder/data" --ethereum.url "<ETH-NODE-ADDRESS>" --network "mainnet" --rpc.websocket --http-rpc "0.0.0.0:9545" environment: - RUST_LOG=info - PATHFINDER_RPC_WEBSOCKET=0.0.0.0:9546 logging: driver: json-file options: max-size: 10m max-file: "10" Option 2: Configure for Juno client Find the latest release from here: version: '3.3' services: starknet-node: image: 'nethermindeth/juno:v0.4.0' user: 1000:1000 restart: always stop_grace_period: 30s network_mode: "host" volumes: - /home/$USER/starknet-node/data:/var/lib/juno ports: - '0.0.0.0:6060:6060' - '0.0.0.0:6061:6061' command: --db-path '/var/lib/juno' --eth-node '<ETH-NODE-ADDRESS>' --log-level 'info' --network 'mainnet' --http-port '6060' --ws-port '6061' logging: driver: json-file options: max-size: 10m max-file: "10" 4. Run the node cd starknet-node docker compose up -d view logs docker compose logs -f starknet-node If your node can successfully connect to an L1 endpoint, it will start to sync blocks Other commands
starknet-nodestarknet-node
No activity yet