Avalanche L1 Nodes
Learn how to run an Avalanche node that tracks an Avalanche L1.
This article describes how to run a node that tracks an Avalanche L1. It requires building AvalancheGo, adding Virtual Machine binaries as plugins to your local data directory, and running AvalancheGo to track these binaries.
This tutorial specifically covers tracking an Avalanche L1 built with Avalanche's Subnet-EVM, the default Virtual Machine run by Avalanche L1s on Avalanche.
Build AvalancheGo
It is recommended that you first complete this comprehensive guide which demonstrates how to build and run a basic Avalanche node. Below are the high level details.
Manage the Avalanche L1 Binaries
After building AvalancheGo successfully,
1. Clone Subnet-EVM
2. Build the Binary and Save as a Plugin
In the Subnet-EVM directory, run the build script, and save it in the “plugins” folder of your .avalanchego data directory. Name the plugin after the VMID of the Avalanche L1 you wish to track. The VMID of the WAGMI Avalanche L1 is the value beginning with “srEX...”.
3. Specify the Plugin with a Config.JSON
Create a file named config.json and add a track-subnets field that is populated with the SubnetID you wish to track. The SubnetID of the WAGMI Avalanche L1 is the value beginning with “28nr...”.
Run the Node
Run AvalancheGo with the —config-file flag to start your node and ensure it tracks the Avalanche L1s included in the configuration file.
Note: The above command includes the --network-id=fuji command because the WAGMI Avalanche L1 is deployed on Fuji Testnet.
You should now see terminal filled with logs and information to suggest the node is properly running and has began bootstrapping to the network.
Bootstrapping and RPC Details
It may take a few hours for the node to fully bootstrap to the Avalanche Primary Network and tracked Avalanche L1s.
When finished bootstrapping, the endpoint will be:
if run locally, or:
if run on a cloud provider. The “X”s should be replaced with the public IP of your EC2 instance.
For more information on the requests available at these endpoints, please see the Subnet-EVM API Reference documentation.
Because each node is also tracking the Primary Network, those RPC endpoints are available as well.
Last updated on