Subnet Creation

A quick review of creating a Subnet on Avalanche - the foundation for our permissioned L1

In the Avalanche Fundamentals course, you learned how to quickly set up an L1 using the Developer Console. This section provides an in depth review of that flow, understanding what comes pre-configured in our genesis, and laying the foundation for what we will need for our Permissioned L1.

Creating a Subnet

Let's create a fresh new Subnet that we can use during this course to test all of the tools and flows for managing Permissioned L1s.

Create Builder Account & Fund Wallet

Before creating your Subnet, we recommend setting up an Avalanche Builder Account for easier access to testnet resources.

Benefits of a Builder Account:

  • Faucet: C-Chain and P-Chain Testnet AVAX directly sent to your account without needing to claim
  • Free Managed Testnet Infrastructure: Access free managed testnet nodes and ICM relayers for your L1
  • No Docker Required: Launch and manage nodes directly from the Builder Console without local setup

After creating your account:

  1. Download Core Wallet if not already installed
  2. Set Core to Testnet mode (upper-right toggle button)
  3. Visit the Builder Console to claim test AVAX on both C-Chain and P-Chain

Create Subnet and Blockchain Records

Create the Subnet by issuing two transactions on the P-Chain (hence the need for test AVAX on the P-chain).

These transactions are:

  1. CreateSubnetTx - Creates a Subnet identified by the transaction hash
  2. CreateChainTx - Adds a blockchain to the Subnet

For this guide, we will create our blockchain as an uncustomized EVM so you just need to rename it (if you want).

On Step 2: Create a Chain select the Genesis JSON tab to the right and skim through it. No need to understand it all but good to get familiar with it before the next section.

Key Parameters:

  • Subnet Owner: P-chain address of your connected wallet
  • Chain Name: Your blockchain's name
  • VM ID: Default value srEX...Dy when creating with an uncustomized VM
  • Genesis Data: Initial blockchain configuration

Set Up Validator Node

Launch a node to track your Subnet. This node will become a validator for your Subnet, and later will be managed by the Validator Manager contract when we convert to L1.

Use our free managed testnet infrastructure - no Docker installation or AWS account required:

Managing Your Nodes

After creating nodes, you can view and manage them at the Testnet Infrastructure Console.

Managed nodes automatically shut down after 3 days. For production or extended testing, see the self-hosted option below.

Production & Extended Testing Environments

For production environments or extended testing periods, you should use Docker to run your nodes.

Docker Setup Guide:

Builder Console

L1 Node Setup with Docker

This will start a Docker container running an RPC or validator node that tracks your L1.

Set up Instance

Set up a linux server with any cloud provider, like AWS, GCP, Azure, or Digital Ocean. Low specs (e.g. 2 vCPUs, 4GB RAM, 20GB storage) are sufficient for basic tests. For more extensive test and production L1s use a larger instance with appropriate resources (e.g. 8 vCPUs, 16GB RAM, 1 TB storage).

If you do not have access to a server, you can also run a node for educational purposes locally. Simply select the "RPC Node (Local)" option in the next step.

Docker Installation

Make sure you have Docker installed on your system. You can use the following commands to install it:

# Install Docker using convenience script
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh
sudo usermod -aG docker $USER
newgrp docker
 
# Test installation
docker run -it --rm hello-world
 

If you do not want to use Docker, you can follow the instructions here.

Select L1

Enter the Avalanche Subnet ID of the L1 you want to run a node for.

Key Takeaways

  • P-Chain Registry: All validators and blockchains are registered on the P-Chain
  • Subnet Foundation: Your Subnet provides the blockchain infrastructure necessary for this course
  • Managed Infrastructure or Self-Hosted: Builder Hub provides free managed testnet nodes, eliminating the need for Docker or AWS setup - you can also choose to run it yourself.

Optional Alternative: Self-Hosted Infrastructure

The free managed testnet nodes are a great option for playing around with Avalanche L1s, but are not intended for running on production environments. They are shut down automatically after 3 days. If you want to test out your production environment, running beyond 3 days, or anything more complex you should run nodes on your own infrastructure using Docker:

Builder Console

L1 Node Setup with Docker

This will start a Docker container running an RPC or validator node that tracks your L1.

Set up Instance

Set up a linux server with any cloud provider, like AWS, GCP, Azure, or Digital Ocean. Low specs (e.g. 2 vCPUs, 4GB RAM, 20GB storage) are sufficient for basic tests. For more extensive test and production L1s use a larger instance with appropriate resources (e.g. 8 vCPUs, 16GB RAM, 1 TB storage).

If you do not have access to a server, you can also run a node for educational purposes locally. Simply select the "RPC Node (Local)" option in the next step.

Docker Installation

Make sure you have Docker installed on your system. You can use the following commands to install it:

# Install Docker using convenience script
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh
sudo usermod -aG docker $USER
newgrp docker
 
# Test installation
docker run -it --rm hello-world
 

If you do not want to use Docker, you can follow the instructions here.

Select L1

Enter the Avalanche Subnet ID of the L1 you want to run a node for.

Is this guide helpful?

Report Issue