logoAcademy

Create a Blockchain

Environment Setup

In order to send messages between two chains, we need to create a blockchain. In this guide, we will spin up a local Avalanche network that has it's own Primary Network (C-, P- and X-Chain) using the Avalanche CLI. Furthermore, we will create a blockchain in that Avalanche network, so we can send messages between the C-Chain and the newly created blockchain in the next chapters.

In the following commands, make sure to substitute the name of your Avalanche L1 for <subnetName> (including the <>). You can choose whatever name you want, but I recommend using myblockchain as the name to avoid the need for some manual configuration.

To create an Avalanche L1 configuration run the following command

avalanche blockchain create <subnetName>

For example:

avalanche blockchain create myblockchain

You will be prompted a Wizard to set the Avalanche L1 config. For now, follow the default options where possible, except when asked for the Airdrop. Select the ewoq address for the airdrop. This address is the default address for the Avalanche test environments and is used for testing purposes.

For convenience, the private key 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027 of the default ewoq address is stored in the environment variable $PK.

PLACEHOLDER VIDEO subnet create

After the finishing, you should see something like this:

@martineckardt ➜ /workspaces/avalanche-starter-kit (main) $ avalanche blockchain create myblockchain
✔ Avalanche L1-EVM
✔ Use latest release version
Installing subnet-evm-v0.6.3...
subnet-evm-v0.6.3 installation successful
creating genesis for subnet myblockchain
Enter your subnet's ChainId. It can be any positive integer.
ChainId: 9999
Select a symbol for your subnet's native token
Token symbol: TOK
✔ Low disk use    / Low Throughput    1.5 mil gas/s (C-Chain's setting)
✔ Airdrop 1 million tokens to the default ewoq address (do not use in production)
✔ No
✔ Yes
✔ Yes
generating stored key "cli-teleporter-deployer" for teleporter deploys
  (evm address, genesis balance) = (0x59560360Cb5EA935849C07af1952fF0910bA690D, 600000000000000000000)
using latest teleporter version (v1.0.0)
✓ Successfully created subnet configuration

This command creates the config files genesis.json and sidecar.json inside: ~/.avalanche-cli/subnets/<subnetName>. If you want, you can retrieve the current config with the following command:

avalanche subnet describe <subnetName>

Start your Local Network (optional)

Now that we created our Avalanche L1 config, we need a network that will host that Avalanche L1. The following command will launch 5 nodes running locally:

avalanche network start

The result should be something like this:

@martineckardt ➜ /workspaces/avalanche-starter-kit (main) $ avalanche network start
Backend controller started, pid: 10949, output at: /home/vscode/.avalanche-cli/runs/server_20240328_200709/avalanche-cli-backend.log
Installing avalanchego-v1.11.3...
avalanchego-v1.11.3 installation successful
Starting previously deployed and stopped snapshot
Booting Network. Wait until healthy...
Node logs directory: /home/vscode/.avalanche-cli/runs/network_20240328_200711/network_20240328_200712/node<i>/logs
Network ready to use.

You can check at any time if the network is running by issuing the following command:

avalanche network status

If you don't start your network manually it will be automatically started when you deploy your first Avalanche L1 with the avalanche subnet deploy <subnetName> command.

Deploy your Avalanche L1

To deploy your Avalanche L1, run

avalanche subnet deploy <subnetName>

When prompted select Local Network to deploy on. After the deployment your should see something like this:

@martineckardt ➜ /workspaces/avalanche-starter-kit (main) $ avalanche subnet deploy myblockchain
Deploying [myblockchain] to Local Network

Deploying Blockchain. Wait until network acknowledges...

Teleporter Messenger successfully deployed to c-chain (0x253b2784c75e510dD0fF1da844684a1aC0aa5fcf)
Interchain Messaging Registry successfully deployed to c-chain (0x17aB05351fC94a1a67Bf3f56DdbB941aE6c63E25)

Teleporter Messenger successfully deployed to myblockchain (0x253b2784c75e510dD0fF1da844684a1aC0aa5fcf)
Interchain Messaging Registry successfully deployed to myblockchain (0x0a3D3aa12Ddc6cfbF21764592cc1223e56F143F4)

using awm-relayer version (v1.3.3)
Executing AWM-Relayer...

Blockchain ready to use

+-------------------+----------------------------------------------------------------------------------------------------------------------------+
|                                                               myblockchain RPC URLs                                                                |
+-------------------+----------------------------------------------------------------------------------------------------------------------------+
| Localhost         | http://127.0.0.1:9650/ext/bc/myblockchain/rpc                                                                                  |
+                   +----------------------------------------------------------------------------------------------------------------------------+
|                   | http://127.0.0.1:9650/ext/bc/2rrM1F6UNo6soe9UuyAHCHtUNLpGbHSrU4CYzvkv6UspxYFGW5/rpc                                        |
+-------------------+----------------------------------------------------------------------------------------------------------------------------+
| Codespace         | https://ideal-funicular-g4qxwg9pqxxh9gr4-9650.app.github.dev/ext/bc/myblockchain/rpc                                           |
+                   +----------------------------------------------------------------------------------------------------------------------------+
|                   | https://ideal-funicular-g4qxwg9pqxxh9gr4-9650.app.github.dev/ext/bc/2rrM1F6UNo6soe9UuyAHCHtUNLpGbHSrU4CYzvkv6UspxYFGW5/rpc |
+-------------------+----------------------------------------------------------------------------------------------------------------------------+

+-------+------------------------------------------+-----------------------+--------------------------------------------------------------+
|                                                                  Nodes                                                                  |
+-------+------------------------------------------+-----------------------+--------------------------------------------------------------+
| Name  | Node ID                                  | Localhost Endpoint    | Codespace Endpoint                                           |
+-------+------------------------------------------+-----------------------+--------------------------------------------------------------+
| node1 | NodeID-7Xhw2mDxuDS44j42TCB6U5579esbSt3Lg | http://127.0.0.1:9650 | https://ideal-funicular-g4qxwg9pqxxh9gr4-9650.app.github.dev |
+-------+------------------------------------------+-----------------------+--------------------------------------------------------------+
| node2 | NodeID-MFrZFVCXPv5iCn6M9K6XduxGTYp891xXZ | http://127.0.0.1:9652 | https://ideal-funicular-g4qxwg9pqxxh9gr4-9652.app.github.dev |
+-------+------------------------------------------+-----------------------+--------------------------------------------------------------+
| node3 | NodeID-NFBbbJ4qCmNaCzeW7sxErhvWqvEQMnYcN | http://127.0.0.1:9654 | https://ideal-funicular-g4qxwg9pqxxh9gr4-9654.app.github.dev |
+-------+------------------------------------------+-----------------------+--------------------------------------------------------------+
| node4 | NodeID-GWPcbFJZFfZreETSoWjPimr846mXEKCtu | http://127.0.0.1:9656 | https://ideal-funicular-g4qxwg9pqxxh9gr4-9656.app.github.dev |
+-------+------------------------------------------+-----------------------+--------------------------------------------------------------+
| node5 | NodeID-P7oB2McjBGgW2NXXWVYjV8JEDFoW9xDE5 | http://127.0.0.1:9658 | https://ideal-funicular-g4qxwg9pqxxh9gr4-9658.app.github.dev |
+-------+------------------------------------------+-----------------------+--------------------------------------------------------------+

Browser Extension connection details (any node URL from above works):
RPC URL:           http://127.0.0.1:9650/ext/bc/2rrM1F6UNo6soe9UuyAHCHtUNLpGbHSrU4CYzvkv6UspxYFGW5/rpc
Codespace RPC URL: https://ideal-funicular-g4qxwg9pqxxh9gr4-9650.app.github.dev/ext/bc/2rrM1F6UNo6soe9UuyAHCHtUNLpGbHSrU4CYzvkv6UspxYFGW5/rpc
Funded address:    0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC with 1000000 (10^18) - private key: 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027
Funded address:    0xD6Fb3Cb2170A973A84b900Dff2479D0c9e8597DB with 600 (10^18)
Network name:      myblockchain
Chain ID:          99999
Currency Symbol:   TOK

This output includes the endpoints of your 5 nodes where you can connect to interact with your Avalanche L1. You're running a Avalanche L1-EVM, this means you can use those RPC URLs to connect to EVM compatible wallet or tools.

Make RPC-Endpoint publicly accessible

Since the Avalanche Network is running in a Github Codespace the localhost (127.0.0.1) will only be accessible from inside the Codespace. Connecting your wallet using the localhost RPC URL will not work, since your wallet will be running on your computer, and not the local environment where the network is running (the Codespace cloud).

Therefore, we need to make the RPC-Endpoint publicly accessible. Click on the little antenna icon in the bottom bar of the Codespace:

There select the row with the port 9650 and right-click to open the port:

Previous

Close and Reopen Codespace

Next

Networks

Updated:

On this page

No Headings
Edit on Github