From 18203a2b6a5da967d64c69619057de98e4d42060 Mon Sep 17 00:00:00 2001 From: owenwahlgren Date: Wed, 21 Aug 2024 12:53:14 -0400 Subject: [PATCH 01/10] replace: subnet -> blockchain --- .../cross-chain/teleporter/teleporter-on-devnet.mdx | 2 +- .../teleporter/teleporter-on-local-network.mdx | 10 +++++----- content/docs/subnets/avalanche-cli-subnets.mdx | 8 ++++---- content/docs/subnets/build-first-subnet.mdx | 8 ++++---- .../docs/subnets/deploy-a-subnet/avalanche-mainnet.mdx | 2 +- .../subnets/deploy-a-subnet/custom-virtual-machine.mdx | 6 +++--- content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx | 6 +++--- content/docs/subnets/deploy-a-subnet/local-network.mdx | 8 ++++---- content/docs/subnets/deploy-a-subnet/multisig-auth.mdx | 2 +- content/docs/subnets/maintain/view-subnets.mdx | 4 ++-- content/docs/subnets/troubleshooting.mdx | 6 +++--- .../docs/subnets/upgrade/subnet-virtual-machine.mdx | 2 +- content/docs/tooling/avalanche-cli.mdx | 8 ++++---- .../create-avalanche-nodes/deploy-custom-vm.mdx | 4 ++-- .../tooling/create-deploy-subnets/create-subnet.mdx | 8 ++++---- .../tooling/create-deploy-subnets/deploy-locally.mdx | 8 ++++---- .../create-deploy-subnets/deploy-on-fuji-testnet.mdx | 6 +++--- .../create-deploy-subnets/deploy-on-mainnet.mdx | 2 +- .../tooling/create-deploy-subnets/view-subnets.mdx | 8 ++++---- content/docs/tooling/cross-chain/teleporter-devnet.mdx | 2 +- .../tooling/cross-chain/teleporter-local-network.mdx | 10 +++++----- 21 files changed, 60 insertions(+), 60 deletions(-) diff --git a/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx b/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx index 9cc06894673..4b5e743d68a 100644 --- a/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx +++ b/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx @@ -202,7 +202,7 @@ By executing `subnet describe` on a Teleporter enabled Subnet, the following rel Let's get the information for ``: ``` -avalanche subnet describe +avalanche blockchain describe _____ _ _ _ | __ \ | | (_) | diff --git a/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx b/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx index de4e9e94168..a7bc8d60619 100644 --- a/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx +++ b/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx @@ -18,7 +18,7 @@ Create Subnet Configurations[​](#create-subnet-configurations "Direct link to Let's create a Subnet called `` with the latest Subnet-EVM version, a chain ID of 1, TOKEN1 as the token name, and with default Subnet-EVM parameters (more information regarding Subnet creation can be found [here](/subnets/build-first-subnet#create-your-subnet-configuration)): ``` -avalanche subnet create --evm --latest\ +avalanche blockchain create --evm --latest\ --evm-chain-id 1 --evm-token TOKEN1 --evm-defaults creating genesis for @@ -38,7 +38,7 @@ To disable Relayer in your Subnet, use the flag `--relayer=false` when creating Now let's create a second Subnet called ``, with similar settings: ``` -avalanche subnet create --evm --latest\ +avalanche blockchain create --evm --latest\ --evm-chain-id 2 --evm-token TOKEN2 --evm-defaults creating genesis for @@ -55,7 +55,7 @@ Deploy the Subnets to Local Network[​](#deploy-the-subnets-to-local-network "D Let's deploy ``: ``` -avalanche subnet deploy --local +avalanche blockchain deploy --local Deploying [] to Local Network Backend controller started, pid: 149427, output at: ~/.avalanche-cli/runs/server_20240229_165923/avalanche-cli-backend.log @@ -109,7 +109,7 @@ CLI configures the Relayer to enable every Subnet to send messages to all other When deploying Subnet ``, the two Teleporter contracts will not be deployed to C-Chain in Local Network as they have already been deployed when we deployed the first Subnet. ``` -avalanche subnet deploy --local +avalanche blockchain deploy --local Deploying [] to Local Network @@ -197,7 +197,7 @@ By executing `subnet describe` on a Teleporter enabled Subnet, the following rel Let's get the information for ``: ``` -avalanche subnet describe +avalanche blockchain describe _____ _ _ _ | __ \ | | (_) | diff --git a/content/docs/subnets/avalanche-cli-subnets.mdx b/content/docs/subnets/avalanche-cli-subnets.mdx index 4588f1c73a6..61d68be38a4 100644 --- a/content/docs/subnets/avalanche-cli-subnets.mdx +++ b/content/docs/subnets/avalanche-cli-subnets.mdx @@ -5,7 +5,7 @@ description: Learn about Avalanche CLI and its different commands for Subnets. Avalanche-CLI is a command-line tool that gives developers access to everything Avalanche. This release specializes in helping developers build and test Subnets. -To get started, look at the documentation for the subcommands or jump right in with `avalanche subnet create myNewSubnet`. +To get started, look at the documentation for the subcommands or jump right in with `avalanche blockchain create myNewSubnet`. [Install Avalanche CLI](/tooling/guides/get-avalanche-cli) @@ -176,7 +176,7 @@ By default, running the command with a `subnetName` that already exists causes t **Usage**: ```bash -avalanche subnet create [subnetName] [flags] +avalanche blockchain create [subnetName] [flags] ``` **Flags**: @@ -229,7 +229,7 @@ Avalanche-CLI only supports deploying an individual Subnet once per network. Sub **Usage**: ```bash -avalanche subnet deploy [subnetName] [flags] +avalanche blockchain deploy [subnetName] [flags] ``` **Flags**: @@ -264,7 +264,7 @@ The `subnet describe` command prints the details of a Subnet configuration to th **Usage**: ```bash -avalanche subnet describe [subnetName] [flags] +avalanche blockchain describe [subnetName] [flags] ``` **Flags**: diff --git a/content/docs/subnets/build-first-subnet.mdx b/content/docs/subnets/build-first-subnet.mdx index 2916eb0a64e..dd1b5246ab7 100644 --- a/content/docs/subnets/build-first-subnet.mdx +++ b/content/docs/subnets/build-first-subnet.mdx @@ -38,7 +38,7 @@ The Subnet command suite provides a collection of tools for developing and deplo The Subnet Creation Wizard walks you through the process of creating your Subnet. To get started, first pick a name for your Subnet. This tutorial uses `mySubnet`, but feel free to substitute that with any name you like. Once you've picked your name, run: ```bash -avalanche subnet create mySubnet +avalanche blockchain create mySubnet ``` The following sections walk through each question in the wizard. @@ -91,7 +91,7 @@ Deploying Subnets Locally[​](#deploying-subnets-locally "Direct link to headin To deploy your Subnet, run: ```bash -avalanche subnet deploy mySubnet +avalanche blockchain deploy mySubnet ``` Make sure to substitute the name of your Subnet if you used a different one than `mySubnet`. @@ -105,7 +105,7 @@ Note: If you run `bash` on your shell and are running Avalanche-CLI on ARM64 on If all works as expected, the command output should look something like this: ```bash -avalanche subnet deploy mySubnet +avalanche blockchain deploy mySubnet # output ✔ Local Network @@ -195,7 +195,7 @@ In the Core Extension click, `See All Networks` and then select the `+` icon in ![Add network](/images/deploy-subnet5.png) -Enter your Subnet's details, found in the output of your `avalanche subnet deploy` [command](#deploying-subnets-locally), into the form and click `Save`. +Enter your Subnet's details, found in the output of your `avalanche blockchain deploy` [command](#deploying-subnets-locally), into the form and click `Save`. ![Add network 2](/images/deploy-subnet6.png) diff --git a/content/docs/subnets/deploy-a-subnet/avalanche-mainnet.mdx b/content/docs/subnets/deploy-a-subnet/avalanche-mainnet.mdx index f587f346db3..35308b60e27 100644 --- a/content/docs/subnets/deploy-a-subnet/avalanche-mainnet.mdx +++ b/content/docs/subnets/deploy-a-subnet/avalanche-mainnet.mdx @@ -104,7 +104,7 @@ Deploy the Subnet[​](#deploy-the-subnet "Direct link to heading") With your Ledger unlocked and running the Avalanche app, run ```bash -avalanche subnet deploy testsubnet +avalanche blockchain deploy testsubnet ``` This is going to start a new prompt series. diff --git a/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx b/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx index 88a99be8d14..e46f15ca48e 100644 --- a/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx +++ b/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx @@ -107,7 +107,7 @@ Create the Subnet Configuration[​](#create-the-subnet-configuration "Direct li Now that you have your binary, it's time to create the Subnet configuration. This tutorial uses `myCustomSubnet` as it Subnet name. Invoke the Subnet Creation Wizard with this command: ```bash -avalanche subnet create myCustomSubnet +avalanche blockchain create myCustomSubnet ``` ### Choose Your VM[​](#choose-your-vm "Direct link to heading") @@ -146,7 +146,7 @@ Now it's time to deploy it. Deploy the Subnet Locally[​](#deploy-the-subnet-locally "Direct link to heading") --------------------------------------------------------------------------------- -To deploy your Subnet, run: `avalanche subnet deploy myCustomSubnet` +To deploy your Subnet, run: `avalanche blockchain deploy myCustomSubnet` Make sure to substitute the name of your Subnet if you used a different one than `myCustomSubnet`. @@ -165,7 +165,7 @@ This command boots a five node Avalanche network on your machine. It needs to do If all works as expected, the command output should look something like this: ```bash -> avalanche subnet deploy myCustomSubnet +> avalanche blockchain deploy myCustomSubnet ✔ Local Network Deploying [myCustomSubnet] to Local Network Backend controller started, pid: 26110, output at: /home/fm/.avalanche-cli/runs/server_20230816_131014/avalanche-cli-backend.log diff --git a/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx b/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx index cc4bb76c33a..fa9c2e7533e 100644 --- a/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx +++ b/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx @@ -181,7 +181,7 @@ Creating a Subnet with `Avalanche-CLI` for `Fuji` works the same way as with a l To create an EVM Subnet, run the `subnet create` command with a name of your choice: ```bash -avalanche subnet create testsubnet +avalanche blockchain create testsubnet ``` This is going to start a series of prompts to customize your EVM Subnet to your needs. Most prompts have some validation to reduce issues due to invalid input. The first prompt asks for the type of the virtual machine (see [Virtual Machine](#virtual-machine)). @@ -261,7 +261,7 @@ At this point, CLI creates the specification of the new Subnet on disk, but isn' Print the specification to disk by running the `describe` command: ```bash -avalanche subnet describe testsubnet +avalanche blockchain describe testsubnet _____ _ _ _ | __ \ | | (_) | | | | | ___| |_ __ _ _| |___ @@ -379,7 +379,7 @@ To deploy the Subnet, you will need some testnet AVAX on the P-chain. To deploy the new Subnet, run: ```bash -avalanche subnet deploy testsubnet +avalanche blockchain deploy testsubnet ``` This is going to start a new prompt series. diff --git a/content/docs/subnets/deploy-a-subnet/local-network.mdx b/content/docs/subnets/deploy-a-subnet/local-network.mdx index 5ca5a3e598d..560084a0c80 100644 --- a/content/docs/subnets/deploy-a-subnet/local-network.mdx +++ b/content/docs/subnets/deploy-a-subnet/local-network.mdx @@ -15,13 +15,13 @@ In the following commands, make sure to substitute the name of your Subnet confi To deploy your Subnet, run ```bash -avalanche subnet deploy +avalanche blockchain deploy ``` and, select `Local Network` to deploy on. Alternatively, you can bypass this prompt by providing the `--local` flag. For example: ```bash -avalanche subnet deploy --local +avalanche blockchain deploy --local ``` The command may take a couple minutes to run. @@ -35,7 +35,7 @@ If you run `bash` on your shell and are running Avalanche-CLI on ARM64 on Mac, y If all works as expected, the command output should look something like this: ```bash -> avalanche subnet deploy mySubnet +> avalanche blockchain deploy mySubnet ✔ Local Network Deploying [mySubnet] to Local Network Installing subnet-evm-v0.4.3... @@ -86,5 +86,5 @@ To redeploy the Subnet, you first need to wipe the Subnet state. This permanentl You are now free to redeploy your Subnet with: ```bash -avalanche subnet deploy --local +avalanche blockchain deploy --local ``` diff --git a/content/docs/subnets/deploy-a-subnet/multisig-auth.mdx b/content/docs/subnets/deploy-a-subnet/multisig-auth.mdx index 47bfb0a7066..a97e7ea70d2 100644 --- a/content/docs/subnets/deploy-a-subnet/multisig-auth.mdx +++ b/content/docs/subnets/deploy-a-subnet/multisig-auth.mdx @@ -28,7 +28,7 @@ When issuing the transactions to create the Subnet, you need to sign the TXs wit Start the Subnet deployment with ```bash -avalanche subnet deploy testsubnet +avalanche blockchain deploy testsubnet ``` First step is to specify `Fuji` or `Mainnet` as the network: diff --git a/content/docs/subnets/maintain/view-subnets.mdx b/content/docs/subnets/maintain/view-subnets.mdx index ba39030af01..f2b1e6a6562 100644 --- a/content/docs/subnets/maintain/view-subnets.mdx +++ b/content/docs/subnets/maintain/view-subnets.mdx @@ -30,7 +30,7 @@ avalanche subnet list --deployed ``` ```bash -avalanche subnet describe firstsubnet +avalanche blockchain describe firstsubnet #output _____ _ _ _ @@ -117,7 +117,7 @@ No precompiles set If you'd like to see the raw genesis file, supply the `--genesis` flag to the describe command: ```bash -avalanche subnet describe firstsubnet --genesis +avalanche blockchain describe firstsubnet --genesis # output { diff --git a/content/docs/subnets/troubleshooting.mdx b/content/docs/subnets/troubleshooting.mdx index 943e56ba208..70d1ec73587 100644 --- a/content/docs/subnets/troubleshooting.mdx +++ b/content/docs/subnets/troubleshooting.mdx @@ -9,7 +9,7 @@ Deployment Times Out[​](#deployment-times-out "Direct link to heading") During a local deployment, your network may fail to start. Your error may look something like this: ```bash -[~]$ avalanche subnet deploy mySubnet +[~]$ avalanche blockchain deploy mySubnet ✔ Local Network Deploying [mySubnet] to Local Network Backend controller started, pid: 26388, output at: /Users/user/.avalanche-cli/runs/server_20221231_111605/avalanche-cli-backend @@ -47,7 +47,7 @@ Incompatible RPC Version for Custom VM[​](#incompatible-rpc-version-for-custom If you're locally deploying a custom VM, you may run into this error message. ```bash -[~]$ avalanche subnet deploy mySubnet +[~]$ avalanche blockchain deploy mySubnet ✔ Local Network Deploying [mySubnet] to Local Network Backend controller started, pid: 26388, output at: /Users/user/.avalanche-cli/runs/server_20221231_111605/avalanche-cli-backend @@ -123,7 +123,7 @@ Updates to AvalancheGo's RPC version are **not** tied to its semantic version sc Fix for MacBook Air M1/M2: ‘Bad CPU type in executable' Error[​](#fix-for-macbook-air-m1m2-bad-cpu-type-in-executable-error "Direct link to heading") ----------------------------------------------------------------------------------------------------------------------------------------------------- -When running `avalanche subnet deploy` via the Avalanche-CLI, the terminal may throw an error that contains the following: +When running `avalanche blockchain deploy` via the Avalanche-CLI, the terminal may throw an error that contains the following: ```bash zsh: bad CPU type in executable: diff --git a/content/docs/subnets/upgrade/subnet-virtual-machine.mdx b/content/docs/subnets/upgrade/subnet-virtual-machine.mdx index 90b6c67254e..28646b28346 100644 --- a/content/docs/subnets/upgrade/subnet-virtual-machine.mdx +++ b/content/docs/subnets/upgrade/subnet-virtual-machine.mdx @@ -32,7 +32,7 @@ After starting the Subnet Upgrade Wizard, you should see something like this: Existing local deployment ``` -If you select the first option, Avalanche-CLI updates your Subnet's config and any future calls to `avalanche subnet deploy` use the new version you select. However, any existing local deployments continue to use the old version. +If you select the first option, Avalanche-CLI updates your Subnet's config and any future calls to `avalanche blockchain deploy` use the new version you select. However, any existing local deployments continue to use the old version. If you select the second option, the opposite occurs. The existing local deployment switches to the new VM but subsequent deploys use the original. diff --git a/content/docs/tooling/avalanche-cli.mdx b/content/docs/tooling/avalanche-cli.mdx index cc89e6e2494..cb7bbffc914 100644 --- a/content/docs/tooling/avalanche-cli.mdx +++ b/content/docs/tooling/avalanche-cli.mdx @@ -3,7 +3,7 @@ title: Introduction description: Avalanche-CLI is a command-line tool that gives developers access to everything Avalanche. --- -To get started, look at the documentation for the subcommands or jump right in with `avalanche subnet create myNewSubnet`. +To get started, look at the documentation for the subcommands or jump right in with `avalanche blockchain create myNewSubnet`. [Install Avalanche CLI](/tooling/guides/get-avalanche-cli) @@ -176,7 +176,7 @@ By default, running the command with a `subnetName` that already exists causes t **Usage**: ```bash -avalanche subnet create [subnetName] [flags] +avalanche blockchain create [subnetName] [flags] ``` **Flags**: @@ -231,7 +231,7 @@ Avalanche-CLI only supports deploying an individual Subnet once per network. Sub **Usage**: ```bash -avalanche subnet deploy [subnetName] [flags] +avalanche blockchain deploy [subnetName] [flags] ``` **Flags**: @@ -266,7 +266,7 @@ The `subnet describe` command prints the details of a Subnet configuration to th **Usage**: ```bash -avalanche subnet describe [subnetName] [flags] +avalanche blockchain describe [subnetName] [flags] ``` **Flags**: diff --git a/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx b/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx index 9afdd4ba4c4..58ae8351372 100644 --- a/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx +++ b/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx @@ -88,7 +88,7 @@ Create the Subnet[​](#create-the-subnet "Direct link to heading") Let's create a Subnet called ``, with custom VM binary and genesis. ```bash -avalanche subnet create +avalanche blockchain create ``` Choose custom @@ -131,7 +131,7 @@ Successfully created subnet configuration For this example, we will deploy the Subnet and blockchain on Fuji. Run: ```bash -avalanche subnet deploy +avalanche blockchain deploy ``` Choose Fuji: diff --git a/content/docs/tooling/create-deploy-subnets/create-subnet.mdx b/content/docs/tooling/create-deploy-subnets/create-subnet.mdx index 8d0f3cd60bc..c7b0716d749 100644 --- a/content/docs/tooling/create-deploy-subnets/create-subnet.mdx +++ b/content/docs/tooling/create-deploy-subnets/create-subnet.mdx @@ -36,7 +36,7 @@ The Subnet command suite provides a collection of tools for developing and deplo The Subnet Creation Wizard walks you through the process of creating your Subnet. To get started, first pick a name for your Subnet. This tutorial uses `mySubnet`, but feel free to substitute that with any name you like. Once you've picked your name, run: ```bash -avalanche subnet create mySubnet +avalanche blockchain create mySubnet ``` The following sections walk through each question in the wizard. @@ -89,7 +89,7 @@ Deploying Subnets Locally[​](#deploying-subnets-locally "Direct link to headin To deploy your Subnet, run: ```bash -avalanche subnet deploy mySubnet +avalanche blockchain deploy mySubnet ``` Make sure to substitute the name of your Subnet if you used a different one than `mySubnet`. @@ -103,7 +103,7 @@ Note: If you run `bash` on your shell and are running Avalanche-CLI on ARM64 on If all works as expected, the command output should look something like this: ```bash -> avalanche subnet deploy mySubnet +> avalanche blockchain deploy mySubnet ✔ Local Network Deploying [mySubnet] to Local Network Installing subnet-evm-v0.4.3... @@ -191,7 +191,7 @@ In the Core Extension click, `See All Networks` and then select the `+` icon in ![](/images/create-subnet5.png) -Enter your Subnet's details, found in the output of your `avalanche subnet deploy` [command](#deploying-subnets-locally), into the form and click `Save`. +Enter your Subnet's details, found in the output of your `avalanche blockchain deploy` [command](#deploying-subnets-locally), into the form and click `Save`. ![](/images/create-subnet5.png) diff --git a/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx b/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx index da2ad734ee7..93a7786c39a 100644 --- a/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx +++ b/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx @@ -18,13 +18,13 @@ In the following commands, make sure to substitute the name of your Subnet confi To deploy your Subnet, run: ```bash -avalanche subnet deploy +avalanche blockchain deploy ``` and select `Local Network` to deploy on. Alternatively, you can bypass this prompt by providing the `--local` flag. For example: ```bash -avalanche subnet deploy --local +avalanche blockchain deploy --local ``` The command may take a couple minutes to run. @@ -36,7 +36,7 @@ Note: If you run `bash` on your shell and are running Avalanche-CLI on ARM64 on If all works as expected, the command output should look something like this: ```bash -> avalanche subnet deploy mySubnet +> avalanche blockchain deploy mySubnet ✔ Local Network Deploying [mySubnet] to Local Network Installing subnet-evm-v0.4.3... @@ -88,5 +88,5 @@ To redeploy the Subnet, you first need to wipe the Subnet state. This permanentl You are now free to redeploy your Subnet with ```bash -avalanche subnet deploy --local +avalanche blockchain deploy --local ``` diff --git a/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx b/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx index 54e8ecfebb6..fa79dc2fe25 100644 --- a/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx +++ b/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx @@ -181,7 +181,7 @@ Creating a Subnet with `Avalanche-CLI` for `Fuji` works the same way as with a l To create an EVM Subnet, run the `subnet create` command with a name of your choice: ```bash -avalanche subnet create testsubnet +avalanche blockchain create testsubnet ``` This is going to start a series of prompts to customize your EVM Subnet to your needs. Most prompts have some validation to reduce issues due to invalid input. The first prompt asks for the type of the virtual machine (see [Virtual Machine](#virtual-machine)). @@ -261,7 +261,7 @@ At this point, CLI creates the specification of the new Subnet on disk, but isn' Print the specification to disk by running the `describe` command: ```bash -avalanche subnet describe testsubnet +avalanche blockchain describe testsubnet _____ _ _ _ | __ \ | | (_) | | | | | ___| |_ __ _ _| |___ @@ -375,7 +375,7 @@ Deploy the Subnet[​](#deploy-the-subnet "Direct link to heading") To deploy the new Subnet, run ```bash -avalanche subnet deploy testsubnet +avalanche blockchain deploy testsubnet ``` This is going to start a new prompt series. diff --git a/content/docs/tooling/create-deploy-subnets/deploy-on-mainnet.mdx b/content/docs/tooling/create-deploy-subnets/deploy-on-mainnet.mdx index 2acfd362344..837c51fdb9b 100644 --- a/content/docs/tooling/create-deploy-subnets/deploy-on-mainnet.mdx +++ b/content/docs/tooling/create-deploy-subnets/deploy-on-mainnet.mdx @@ -105,7 +105,7 @@ Deploy the Subnet[​](#deploy-the-subnet "Direct link to heading") With your Ledger unlocked and running the Avalanche app, run ```bash -avalanche subnet deploy testsubnet +avalanche blockchain deploy testsubnet ``` This is going to start a new prompt series. diff --git a/content/docs/tooling/create-deploy-subnets/view-subnets.mdx b/content/docs/tooling/create-deploy-subnets/view-subnets.mdx index 2b181b07b74..f8fd85f91fb 100644 --- a/content/docs/tooling/create-deploy-subnets/view-subnets.mdx +++ b/content/docs/tooling/create-deploy-subnets/view-subnets.mdx @@ -34,12 +34,12 @@ To see detailed information about your deployed Subnets, add the `--deployed` fl ## Describe Subnet Configurations -To see the details of a specific configuration, run: `avalanche subnet describe ` +To see the details of a specific configuration, run: `avalanche blockchain describe ` Example: ```bash -> avalanche subnet describe firstsubnet +> avalanche blockchain describe firstsubnet _____ _ _ _ | __ \ | | (_) | @@ -123,12 +123,12 @@ No precompiles set ## Viewing a Genesis File -If you'd like to see the raw genesis file, supply the `--genesis` flag to the describe command: `avalanche subnet describe --genesis` +If you'd like to see the raw genesis file, supply the `--genesis` flag to the describe command: `avalanche blockchain describe --genesis` Example: ```bash -> avalanche subnet describe firstsubnet --genesis +> avalanche blockchain describe firstsubnet --genesis { "config": { "chainId": 12345, diff --git a/content/docs/tooling/cross-chain/teleporter-devnet.mdx b/content/docs/tooling/cross-chain/teleporter-devnet.mdx index 50aa152d03a..fb51ecccea3 100644 --- a/content/docs/tooling/cross-chain/teleporter-devnet.mdx +++ b/content/docs/tooling/cross-chain/teleporter-devnet.mdx @@ -202,7 +202,7 @@ By executing `subnet describe` on a Teleporter enabled Subnet, the following rel Let's get the information for ``: ```bash -avalanche subnet describe +avalanche blockchain describe _____ _ _ _ | __ \ | | (_) | diff --git a/content/docs/tooling/cross-chain/teleporter-local-network.mdx b/content/docs/tooling/cross-chain/teleporter-local-network.mdx index 552961cc17a..2aaba5b2639 100644 --- a/content/docs/tooling/cross-chain/teleporter-local-network.mdx +++ b/content/docs/tooling/cross-chain/teleporter-local-network.mdx @@ -21,7 +21,7 @@ Create Subnet Configurations[​](#create-subnet-configurations "Direct link to Let's create a Subnet called `` with the latest Subnet-EVM version, a chain ID of 1, TOKEN1 as the token name, and with default Subnet-EVM parameters (more information regarding Subnet creation can be found [here](/subnets/build-first-subnet#create-your-subnet-configuration)): ```bash -avalanche subnet create --evm --latest\ +avalanche blockchain create --evm --latest\ --evm-chain-id 1 --evm-token TOKEN1 --evm-defaults creating genesis for @@ -41,7 +41,7 @@ To disable Relayer in your Subnet, use the flag `--relayer=false` when creating Now let's create a second Subnet called ``, with similar settings: ```bash -avalanche subnet create --evm --latest\ +avalanche blockchain create --evm --latest\ --evm-chain-id 2 --evm-token TOKEN2 --evm-defaults creating genesis for @@ -58,7 +58,7 @@ Deploy the Subnets to Local Network[​](#deploy-the-subnets-to-local-network "D Let's deploy ``: ```bash -avalanche subnet deploy --local +avalanche blockchain deploy --local Deploying [] to Local Network Backend controller started, pid: 149427, output at: ~/.avalanche-cli/runs/server_20240229_165923/avalanche-cli-backend.log @@ -112,7 +112,7 @@ CLI configures the Relayer to enable every Subnet to send messages to all other When deploying Subnet ``, the two Teleporter contracts will not be deployed to C-Chain in Local Network as they have already been deployed when we deployed the first Subnet. ```bash -avalanche subnet deploy --local +avalanche blockchain deploy --local Deploying [] to Local Network @@ -200,7 +200,7 @@ By executing `subnet describe` on a Teleporter enabled Subnet, the following rel Let's get the information for ``: ```bash -avalanche subnet describe +avalanche blockchain describe _____ _ _ _ | __ \ | | (_) | From 30184163103e8fcf96afe50f4b1cb187595b3020 Mon Sep 17 00:00:00 2001 From: owenwahlgren Date: Fri, 23 Aug 2024 16:29:13 -0400 Subject: [PATCH 02/10] replace: subnet -> blockchain --- .../docs/subnets/avalanche-cli-subnets.mdx | 44 ++-- .../deploy-a-subnet/avalanche-mainnet.mdx | 10 +- .../subnets/deploy-a-subnet/fuji-testnet.mdx | 14 +- .../subnets/deploy-a-subnet/multisig-auth.mdx | 2 +- .../make-subnet-permissionless.mdx | 80 ------ .../subnets/elastic-subnets/parameters.mdx | 238 ------------------ .../docs/subnets/maintain/delete-subnet.mdx | 2 +- .../docs/subnets/maintain/view-subnets.mdx | 4 +- .../upgrade/subnet-precompile-config.mdx | 28 +-- .../upgrade/subnet-virtual-machine.mdx | 2 +- content/docs/tooling/avalanche-cli.mdx | 44 ++-- .../deploy-custom-vm.mdx | 8 +- .../deploy-on-fuji-testnet.mdx | 14 +- .../deploy-on-mainnet.mdx | 10 +- .../create-deploy-subnets/view-subnets.mdx | 6 +- content/docs/tooling/guides/import-subnet.mdx | 2 +- next.config.mjs | 10 - 17 files changed, 95 insertions(+), 423 deletions(-) delete mode 100644 content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx delete mode 100644 content/docs/subnets/elastic-subnets/parameters.mdx diff --git a/content/docs/subnets/avalanche-cli-subnets.mdx b/content/docs/subnets/avalanche-cli-subnets.mdx index 61d68be38a4..0e357d2e52f 100644 --- a/content/docs/subnets/avalanche-cli-subnets.mdx +++ b/content/docs/subnets/avalanche-cli-subnets.mdx @@ -64,7 +64,7 @@ This command currently only works on Subnets deployed to either the Fuji Testnet **Usage**: ```bash -avalanche subnet addValidator [subnetName] [flags] +avalanche blockchain addValidator [subnetName] [flags] ``` **Flags**: @@ -97,7 +97,7 @@ This command removes a node as a validator in a Subnet. **Usage**: ```bash -avalanche subnet removeValidator [subnetName] [flags] +avalanche blockchain removeValidator [subnetName] [flags] ``` **Flags**: @@ -122,7 +122,7 @@ The `subnet changeOwner` changes the owner of the deployed Subnet. This command **Usage**: ```bash -avalanche subnet changeOwner [subnetName] [flags] +avalanche blockchain changeOwner [subnetName] [flags] ``` **Flags**: @@ -153,7 +153,7 @@ AvalancheGo nodes support several different configuration files. Subnets have th **Usage**: ```bash -avalanche subnet configure [subnetName] [flags] +avalanche blockchain configure [subnetName] [flags] ``` **Flags**: @@ -209,7 +209,7 @@ The `subnet delete` command deletes an existing Subnet configuration. **Usage**: ```bash -avalanche subnet delete [flags] +avalanche blockchain delete [flags] ``` **Flags**: @@ -281,7 +281,7 @@ The `subnet export` command write the details of an existing Subnet deploy to a **Usage**: ```bash -avalanche subnet export [subnetName] [flags] +avalanche blockchain export [subnetName] [flags] ``` **Flags**: @@ -304,7 +304,7 @@ To import from a file, you can optionally provide the path as a command-line arg **Usage**: ```bash -avalanche subnet import file [subnetPath] [flags] +avalanche blockchain import file [subnetPath] [flags] ``` **Flags**: @@ -326,7 +326,7 @@ The genesis file should be available from the disk for this to work. By default, **Usage**: ```bash -avalanche subnet import public [subnetPath] [flags] +avalanche blockchain import public [subnetPath] [flags] ``` **Flags**: @@ -358,7 +358,7 @@ This command currently only supports Subnets deployed on the Fuji Testnet and Ma **Usage**: ```bash -avalanche subnet join [subnetName] [flags] +avalanche blockchain join [subnetName] [flags] ``` **Flags**: @@ -385,7 +385,7 @@ The `subnet list` command prints the names of all created Subnet configurations. **Usage**: ```bash -avalanche subnet list [flags] +avalanche blockchain list [flags] ``` **Flags**: @@ -402,7 +402,7 @@ The `subnet publish` command publishes the Subnet's VM to a repository. **Usage**: ```bash -avalanche subnet publish [subnetName] [flags] +avalanche blockchain publish [subnetName] [flags] ``` **Flags**: @@ -424,7 +424,7 @@ The `subnet stats` command prints validator statistics for the given Subnet. **Usage**: ```bash -avalanche subnet stats [subnetName] [flags] +avalanche blockchain stats [subnetName] [flags] ``` **Flags**: @@ -443,7 +443,7 @@ The `subnet vmid` command prints the virtual machine ID (VMID) for the given Sub **Usage**: ```bash -avalanche subnet vmid [subnetName] +avalanche blockchain vmid [subnetName] ``` Elastic Subnet[​](#elastic-subnet "Direct link to heading") @@ -456,7 +456,7 @@ This command transforms your permissioned Subnet into an Elastic Subnet (NOTE: t **Usage**: ```bash -avalanche subnet elastic [subnetName] [flags] +avalanche blockchain elastic [subnetName] [flags] ``` **Flags**: @@ -489,7 +489,7 @@ This command adds a node as a permissionless validator in an Elastic Subnet. **Usage**: ```bash -avalanche subnet join [subnetName] --elastic [flags] +avalanche blockchain join [subnetName] --elastic [flags] ``` **Flags**: @@ -515,7 +515,7 @@ This command delegates stake to a permissionless validator in an Elastic Subnet. **Usage**: ```bash -avalanche subnet addPermissionlessDelegator [subnetName] [flags] +avalanche blockchain addPermissionlessDelegator [subnetName] [flags] ``` **Flags**: @@ -550,7 +550,7 @@ After you update your validator's configuration, you need to restart your valida **Usage**: ```bash -avalanche subnet upgrade apply [subnetName] [flags] +avalanche blockchain upgrade apply [subnetName] [flags] ``` **Flags**: @@ -574,7 +574,7 @@ Export the upgrade bytes file to a location of choice on disk. **Usage**: ```bash -avalanche subnet upgrade export [subnetName] [flags] +avalanche blockchain upgrade export [subnetName] [flags] ``` **Flags**: @@ -592,7 +592,7 @@ The `subnet upgrade generate` command builds a new upgrade.json file to customiz **Usage**: ```bash -avalanche subnet upgrade generate [subnetName] [flags] +avalanche blockchain upgrade generate [subnetName] [flags] ``` **Flags**: @@ -608,7 +608,7 @@ Import the upgrade bytes file into the local environment. **Usage**: ```bash -avalanche subnet upgrade import [subnetName] [flags] +avalanche blockchain upgrade import [subnetName] [flags] ``` **Flags**: @@ -625,7 +625,7 @@ Print the upgrade.json file content. **Usage**: ```bash -avalanche subnet upgrade print [subnetName] [flags] +avalanche blockchain upgrade print [subnetName] [flags] ``` **Flags**: @@ -643,7 +643,7 @@ The command walks the user through an interactive wizard. The user can skip the **Usage**: ```bash -avalanche subnet upgrade export [subnetName] [flags] +avalanche blockchain upgrade export [subnetName] [flags] ``` **Flags**: diff --git a/content/docs/subnets/deploy-a-subnet/avalanche-mainnet.mdx b/content/docs/subnets/deploy-a-subnet/avalanche-mainnet.mdx index 35308b60e27..0f8cfd3ba07 100644 --- a/content/docs/subnets/deploy-a-subnet/avalanche-mainnet.mdx +++ b/content/docs/subnets/deploy-a-subnet/avalanche-mainnet.mdx @@ -217,7 +217,7 @@ See [here](/nodes/validate/node-validator#add-a-validator-with-core-extension) o First, request permission to validate by running the `join` command along with the Subnet name: ```bash -avalanche subnet join testsubnet +avalanche blockchain join testsubnet ``` Note: Running `join` does not guarantee that your node is a validator of the Subnet! The owner of the Subnet must approve your node to be a validator afterwards by calling `addValidator` as described in the next section. @@ -334,7 +334,7 @@ Now that the node has joined the Subnet, a Subnet control key holder must call ` To whitelist a node as a recognized validator on the Subnet, run: ```bash -avalanche subnet addValidator testsubnet +avalanche blockchain addValidator testsubnet ``` You need to repeat this process for every validator you add to the network. @@ -488,7 +488,7 @@ Subnet Export[​](#subnet-export "Direct link to heading") Because you need to setup multiple validators on multiple different machines, you need to export your Subnet's configuration and import it on each validator. ```bash -avalanche subnet export testsubnet +avalanche blockchain export testsubnet ✔ Enter file path to write export data to: /tmp/testsubnet-export.dat ``` @@ -500,14 +500,14 @@ Subnet Import[​](#subnet-import "Direct link to heading") To import a VM configuration, move the file you exported in the previous section to your desired machine and issue the `import` command with the path to the file. ```bash -avalanche subnet import /tmp/testsubnet-export.dat +avalanche blockchain import /tmp/testsubnet-export.dat Subnet imported successfully ``` After this the whole Subnet configuration should be available on the target machine: ```bash -avalanche subnet list +avalanche blockchain list +---------------+---------------+----------+-----------+----------+ | SUBNET | CHAIN | CHAIN ID | TYPE | DEPLOYED | +---------------+---------------+----------+-----------+----------+ diff --git a/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx b/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx index fa9c2e7533e..c9be159dc1f 100644 --- a/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx +++ b/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx @@ -345,7 +345,7 @@ No precompiles set Also you can list the available Subnets: ```bash -avalanche subnet list +avalanche blockchain list go run main.go subnet list +-------------+-------------+----------+---------------------------------------------------+------------+-----------+ | SUBNET | CHAIN | CHAIN ID | VM ID | TYPE | FROM REPO | @@ -357,7 +357,7 @@ go run main.go subnet list List deployed information: ```bash -avalanche subnet list --deployed +avalanche blockchain list --deployed go run main.go subnet list --deployed +-------------+-------------+---------------------------------------------------+---------------+-----------------------------------------------------------------+---------+ | SUBNET | CHAIN | VM ID | LOCAL NETWORK | FUJI (TESTNET) | MAINNET | @@ -478,7 +478,7 @@ See [here](/nodes/validate/node-validator#add-a-validator-with-core-extension) o First, request permission to validate by running the `join` command along with the Subnet name: ```bash -avalanche subnet join testsubnet +avalanche blockchain join testsubnet ``` Note: Running `join` does not guarantee that your node is a validator of the Subnet! The owner of the Subnet must approve your node to be a validator afterwards by calling `addValidator` as described in the next section. @@ -580,7 +580,7 @@ Now that the node has joined the Subnet, a Subnet control key holder must call ` To whitelist a node as a recognized validator on the Subnet, run: ```bash -avalanche subnet addValidator testsubnet +avalanche blockchain addValidator testsubnet ``` As this operation involves a new transaction, you will need to specify which private key to use: @@ -680,7 +680,7 @@ Subnet Export[​](#subnet-export "Direct link to heading") This tool is most useful on the machine where a validator is or is going to be running. In order to allow a VM to run on a different machine, you can export the configuration. Just need to provide a path to where to export the data: ```bash -avalanche subnet export testsubnet +avalanche blockchain export testsubnet ✔ Enter file path to write export data to: /tmp/testsubnet-export.dat ``` @@ -692,14 +692,14 @@ Subnet Import[​](#subnet-import "Direct link to heading") To import a VM specification exported in the previous section, just issue the `import` command with the path to the file after having copied the file over: ```bash -avalanche subnet import /tmp/testsubnet-export.dat +avalanche blockchain import /tmp/testsubnet-export.dat Subnet imported successfully ``` After this the whole Subnet configuration should be available on the target machine: ```bash -avalanche subnet list +avalanche blockchain list +---------------+---------------+----------+-----------+----------+ | SUBNET | CHAIN | CHAIN ID | TYPE | DEPLOYED | +---------------+---------------+----------+-----------+----------+ diff --git a/content/docs/subnets/deploy-a-subnet/multisig-auth.mdx b/content/docs/subnets/deploy-a-subnet/multisig-auth.mdx index a97e7ea70d2..d5192171a54 100644 --- a/content/docs/subnets/deploy-a-subnet/multisig-auth.mdx +++ b/content/docs/subnets/deploy-a-subnet/multisig-auth.mdx @@ -303,7 +303,7 @@ Add Validators Using the Multisig[​](#add-validators-using-the-multisig "Direc The `addValidator` command also requires use of the multisig. Before starting, make sure to connect, unlock, and run the Avalanche Ledger app. ```bash -avalanche subnet addValidator testsubnet +avalanche blockchain addValidator testsubnet ``` ### Select Network[​](#select-network "Direct link to heading") diff --git a/content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx b/content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx deleted file mode 100644 index 75c9ffd7aea..00000000000 --- a/content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: Make Subnet Permissionless -description: Learn how to transform a Permissioned Subnet into an Elastic Subnet. ---- - -Elastic Subnets are permissionless Subnets. More information can be found [here](/subnets/elastic-subnets/parameters). - -This how-to guide focuses on taking an already created permissioned Subnet and transforming it to an elastic (or permissionless) Subnet. - -## Prerequisites - -- [Avalanche-CLI installed](/tooling/guides/get-avalanche-cli) -- You have deployed a permissioned Subnet on [local](/subnets/deploy-a-subnet/local-network), on [Fuji](/subnets/deploy-a-subnet/fuji-testnet) or on [Mainnet](/subnets/deploy-a-subnet/avalanche-mainnet) - -Getting Started[​](#getting-started "Direct link to heading") -------------------------------------------------------------- - -In the following commands, make sure to substitute the name of your Subnet configuration for ``. - -To transform your permissioned Subnet into an Elastic Subnet (NOTE: this action is irreversible), run: - -```bash -avalanche subnet elastic -``` - -and, select the network that you want to transform the Subnet on. Alternatively, you can bypass this prompt by providing the `--local`, `--fuji`, or `--mainnet` flag. - -Provide the name and the symbol for the permissionless Subnet's native token. You can also bypass this prompt by providing the `--tokenName` and `--tokenSymbol` flags. - -Next, select the Elastic Subnet config. You can choose to use the default values detailed [here](/subnets/elastic-subnets/parameters#primary-network-parameters-on-mainnet) or customize the Elastic Subnet config. To bypass the prompt, you can use `--default` flag to use the default Elastic Subnet config. - -The command may take a couple minutes to run. - -### Elastic Subnet Transformation on Fuji and Mainnet[​](#elastic-subnet-transformation-on-fuji-and-mainnet "Direct link to heading") - -Elastic Subnet transformation on public network requires private key loaded into the tool, or a connected ledger device. - -Both stored key usage and ledger usage are enabled on Fuji (see more on creating keys [here](/subnets/deploy-a-subnet/fuji-testnet#private-key)) while only ledger usage is enabled on Mainnet (see more on setting up your ledger [here](/subnets/deploy-a-subnet/avalanche-mainnet#setting-up-your-ledger)). - -To transform a permissioned Subnet into Elastic Subnet on public networks, users are required to provide the keys that control the Subnet defined during the Subnet deployment process (more info on keys in Fuji can be found [here](/subnets/deploy-a-subnet/fuji-testnet#deploy-the-subnet), while more info on ledger signing in Mainnet can be found [here](/subnets/deploy-a-subnet/avalanche-mainnet#deploy-the-subnet)). - -### Results[​](#results "Direct link to heading") - -If all works as expected, you then have the option to automatically transform all existing permissioned validators to permissionless validators. - -You can also to skip automatic transformation at this point and choose to manually add permissionless validators later. - -You can use the output details such as the Asset ID and Elastic Subnet ID to connect to and interact with your Elastic Subnet. - -Adding Permissionless Validators to Elastic Subnet[​](#adding-permissionless-validators-to-elastic-subnet "Direct link to heading") ------------------------------------------------------------------------------------------------------------------------------------ - -If you are running this command on local network, you will need to first remove permissioned validators (by running `avalanche subnet removeValidator `) so that you can have a list of local nodes to choose from to be added as a permissionless validator in the Elastic Subnet. - -To add permissionless validators to an Elastic Subnet, run: - -```bash -avalanche subnet join --elastic -``` - -You will be prompted with which node you would like to add as a permissionless validator. You can skip this prompt by using `--nodeID` flag. - -You will then be prompted with the amount of the Subnet native token that you like to stake in the validator. Alternatively, you can bypass this prompt by providing the `--stake-amount` flag. Note that choosing to add the maximum validator stake amount (defined during Elastic Subnet transformation step above) means that you effectively disable delegation in your validator. - -Next, select when the validator will start validating and how long it will be validating for. You can also bypass these prompts by using `--start-time` and `--staking-period` flags. - -Adding Permissionless Delegator to a Permissionless Validator in Elastic Subnet[​](#adding-permissionless-delegator-to-a-permissionless-validator-in-elastic-subnet "Direct link to heading") ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- - -To add permissionless delegators, run: - -```bash -avalanche subnet addPermissionlessDelegator -``` - -You will be prompted with which Subnet validator you would like to delegate to. You can skip this prompt by using `--nodeID` flag. - -You will then be prompted with the amount of the Subnet native token that you like to stake in the validator. Alternatively, you can bypass this prompt by providing the `--stake-amount` flag. The amount that can be delegated to a validator is detailed [here](/subnets/elastic-subnets/parameters#delegators-weight-checks). - -Next, select when you want to start delegating and how long you want to delegate for. You can also bypass these prompts by using `--start-time` and `--staking-period` flags. \ No newline at end of file diff --git a/content/docs/subnets/elastic-subnets/parameters.mdx b/content/docs/subnets/elastic-subnets/parameters.mdx deleted file mode 100644 index 280ffc386df..00000000000 --- a/content/docs/subnets/elastic-subnets/parameters.mdx +++ /dev/null @@ -1,238 +0,0 @@ ---- -title: Parameters -description: Learn about the different parameters of Elastic Subnets. ---- - -Avalanche Permissioned Subnets can be turned into Elastic Subnets via the `TransformSubnetTx` transaction. `TransformSubnetTx` specifies a set of structural parameters for the Elastic Subnet. - -This reference document describes these structural parameters and illustrates the constraints they must satisfy. - -## Elastic Subnet Parameters - -### `Subnet` - -`Subnet` has type `ids.ID` and it's the Subnet ID. `Subnet` is the ID of the `CreateSubnetTx` transaction that created the Subnet in the first place. The following constraints apply: - -- `Subnet` must be different from `PrimaryNetworkID`. - -### `AssetID` - -`AssetID` has type `ids.ID` and it's the ID of the asset to use when staking on the Subnet. The following constraints apply: - -- `AssetID` must not be the `Empty ID`. -- `AssetID` must not be `AVAX ID`, the Primary Network asset. - -### `InitialSupply` - -`InitialSupply` has type `uint64` and it's the initial amount of `AssetID` transferred in the Elastic Subnet upon its transformation. Such amount is available for distributing staking rewards. The following constraints apply: - -- `InitialSupply` must be larger than zero. - -### `MaximumSupply` - -`MaximumSupply` has type `uint64` and it's the maximum amount of `AssetID` that Subnet has available for staking and rewards at any time. The following constraints apply: - -- `MaximumSupply` must be larger or equal to `InitialSupply`. - -A Subnet supply can vary in time but it should be no larger than the configured maximum at any point in time, including at Subnet creation. - -### `MinConsumptionRate` - -`MinConsumptionRate` has type `uint64` and it's the minimal rate a validator can earn if the `UptimeRequirement` is satisfied. If `StakingPeriod` == `MinStakeDuration`, the validator will earn the `MinConsumptionRate`. - -You can find more details about it in the [Reward Formula section](#reward-formula). The following constraints apply: - -- `MinConsumptionRate` must be smaller or equal to `PercentDenominator`. - -See [Notes on Percentages](#notes-on-percentages) section to understand `PercentDenominator` role. - -### `MaxConsumptionRate` - -`MaxConsumptionRate` has type `uint64` and it's the maximal rate a validator can earn if the `UptimeRequirement` is satisfied. If `StakingPeriod` == `MaxStakeDuration` == `MintingPeriod`, the validator will earn the `MaxConsumptionRate`. - -You can find more details about it in the [Reward Formula section](#reward-formula). The following constraints apply: - -- `MaxConsumptionRate` must be larger or equal to `MinConsumptionRate`. -- `MaxConsumptionRate` must be smaller or equal to `PercentDenominator`. - -See [Notes on Percentages](#notes-on-percentages) section to understand `PercentDenominator` role. - -### `MinValidatorStake` - -`MinValidatorStake` has type `uint64` and it's the minimum amount of funds required to become a validator. The following constraints apply: - -- `MinValidatorStake` must be larger than zero -- `MinValidatorStake` must be smaller or equal to `InitialSupply` - -### `MaxValidatorStake` - -`MaxValidatorStake` has type `uint64` and it's the maximum amount of funds a single validator can be allocated, including delegated funds. The following constraints apply: - -- `MaxValidatorStake` must be larger or equal to `MinValidatorStake` -- `MaxValidatorStake` must be smaller or equal to `MaximumSupply` - -### `MinStakeDuration` - -`MinStakeDuration` has type `uint32` and it's the minimum number of seconds a staker can stake for. The following constraints apply: - -- `MinStakeDuration` must be larger than zero. - -### `MaxStakeDuration` - -`MaxStakeDuration` has type `uint32` and it's the maximum number of seconds a staker can stake for. The following constraints apply: - -- `MaxStakeDuration` must be larger or equal to `MinStakeDuration`. -- `MaxStakeDuration` must be smaller or equal to `GlobalMaxStakeDuration`. - -`GlobalMaxStakeDuration` is defined in genesis and applies to both the Primary Network and all Subnets. - -Its Mainnet value is $365 \times 24 \times time.Hour$. - -### `MinDelegationFee` - -`MinDelegationFee` has type `uint32` and it's the minimum fee rate a delegator must pay to its validator for delegating. `MinDelegationFee` is a percentage; the actual fee is calculated multiplying the fee rate for the delegator reward. The following constraints apply: - -- `MinDelegationFee` must be smaller or equal to `PercentDenominator`. - -The `MinDelegationFee` rate applies to Primary Network as well. Its Mainnet value is $2\%$. - -### `MinDelegatorStake` - -`MinDelegatorStake` has type `uint64` and it's the minimum amount of funds required to become a delegator. The following constraints apply: - -- `MinDelegatorStake` must be larger than zero. - -### `MaxValidatorWeightFactor` - -`MaxValidatorWeightFactor` has type `uint8` and it's the factor which calculates the maximum amount of delegation a validator can receive. A value of 1 effectively disables delegation. You can find more details about it in the [Delegators Weight Checks section](#delegators-weight-checks). The following constraints apply: - -- `MaxValidatorWeightFactor` must be larger than zero. - -### `UptimeRequirement` - -`UptimeRequirement` has type `uint32` and it's the minimum percentage of its staking time that a validator must be online and responsive for to receive a reward. The following constraints apply: - -- `UptimeRequirement` must be smaller or equal `PercentDenominator`. - -See [Notes on Percentages](#notes-on-percentages) section to understand `PercentDenominator` role. - -## Reward Formula - -Consider an Elastic Subnet validator which stakes a $Stake$ amount `AssetID` for $StakingPeriod$ seconds. - -Assume that at the start of the staking period there is a $Supply$ amount of `AssetID` in the Subnet. The maximum amount of Subnet asset is $MaximumSupply$ `AssetID`. - -Then at the end of its staking period, a responsive Elastic Subnet validator receives a reward calculated as follows: - -$$ -Reward = \left(MaximumSupply - Supply \right) \times \frac{Stake}{Supply} \times \frac{Staking Period}{Minting Period} \times EffectiveConsumptionRate -$$ - -where, - -$$ -MaximumSupply - Supply = \text{the number of tokens left to emit in the subnet} -$$ - -$$ -\frac{Stake}{Supply} = \text{the individual's stake as a percentage of all available tokens in the network} -$$ - -$$ -\frac{StakingPeriod}{MintingPeriod} = \text{time tokens are locked up divided by the $MintingPeriod$} -$$ - -$$ -\text{$MintingPeriod$ is one year as configured by the Primary Network).} -$$ - -$$ -EffectiveConsumptionRate = -$$ - -$$ -\frac{MinConsumptionRate}{PercentDenominator} \times \left(1- \frac{Staking Period}{Minting Period}\right) + \frac{MaxConsumptionRate}{PercentDenominator} \times \frac{Staking Period}{Minting Period} -$$ - -Note that $StakingPeriod$ is the staker's entire staking period, not just the staker's uptime, that is the aggregated time during which the staker has been responsive. The uptime comes into play only to decide whether a staker should be rewarded; to calculate the actual reward only the staking period duration is taken into account. - -$EffectiveConsumptionRate$ is the rate at which the validator is rewarded based on $StakingPeriod$ selection. - -$MinConsumptionRate$ and $MaxConsumptionRate$ bound $EffectiveConsumptionRate$: - -$$ -MinConsumptionRate \leq EffectiveConsumptionRate \leq MaxConsumptionRate -$$ - -The larger $StakingPeriod$ is, the closer $EffectiveConsumptionRate$ is to $MaxConsumptionRate$. The smaller $StakingPeriod$ is, the closer $EffectiveConsumptionRate$ is to $MinConsumptionRate$. - -A staker achieves the maximum reward for its stake if $StakingPeriod$ = $Minting Period$. The reward is: - -$$ -Max Reward = \left(MaximumSupply - Supply \right) \times \frac{Stake}{Supply} \times \frac{MaxConsumptionRate}{PercentDenominator} -$$ - -Note that this formula is the same as the reward formula at the top of this section because $EffectiveConsumptionRate$ = $MaxConsumptionRate$. - -The reward formula above is used in the Primary Network to calculate stakers reward. For reference, you can find Primary network parameters in [the section below](#primary-network-parameters-on-mainnet). - -## Delegators Weight Checks - -There are bounds set of the maximum amount of delegators' stake that a validator can receive. - -The maximum weight $MaxWeight$ a validator $Validator$ can have is: - -$$ -MaxWeight = \min(Validator.Weight \times MaxValidatorWeightFactor, MaxValidatorStake) -$$ - -where $MaxValidatorWeightFactor$ and $MaxValidatorStake$ are the Elastic Subnet Parameters described above. - -A delegator won't be added to a validator if the combination of their weights and all other validator's delegators' weight is larger than $MaxWeight$. Note that this must be true at any point in time. - -Note that setting $MaxValidatorWeightFactor$ to 1 disables delegation since the $MaxWeight = Validator.Weight$. - -## Notes on Percentages - -`PercentDenominator = 1_000_000` is the denominator used to calculate percentages. - -It allows you to specify percentages up to 4 digital positions. To denominate your percentage in `PercentDenominator` just multiply it by `10_000`. For example: - -- `100%` corresponds to `100 * 10_000 = 1_000_000` -- `1%` corresponds to `1* 10_000 = 10_000` -- `0.02%` corresponds to `0.002 * 10_000 = 200` -- `0.0007%` corresponds to `0.0007 * 10_000 = 7` - -## Primary Network Parameters on Mainnet - -An Elastic Subnet is free to pick any parameters affecting rewards, within the constraints specified above. For reference we list below Primary Network parameters on Mainnet: - -- `AssetID = Avax` -- `InitialSupply = 240_000_000 Avax` -- `MaximumSupply = 720_000_000 Avax`. -- `MinConsumptionRate = 0.10 * reward.PercentDenominator`. -- `MaxConsumptionRate = 0.12 * reward.PercentDenominator`. -- `Minting Period = 365 * 24 * time.Hour`. -- `MinValidatorStake = 2_000 Avax`. -- `MaxValidatorStake = 3_000_000 Avax`. -- `MinStakeDuration = 2 * 7 * 24 * time.Hour`. -- `MaxStakeDuration = 365 * 24 * time.Hour`. -- `MinDelegationFee = 20000`, that is `2%`. -- `MinDelegatorStake = 25 Avax`. -- `MaxValidatorWeightFactor = 5`. This is a platformVM parameter rather than a genesis one, so it's shared across networks. -- `UptimeRequirement = 0.8`, that is `80%`. - -### Interactive Graph - -The graph below demonstrates the reward as a function of the length of time -staked. The x-axis depicts $\frac{StakingPeriod}{MintingPeriod}$ as a percentage -while the y-axis depicts $Reward$ as a percentage of $MaximumSupply - Supply$, -the amount of tokens left to be emitted. - -Graph variables correspond to those defined above: - -- `h` (high) = $MaxConsumptionRate$ -- `l` (low) = $MinConsumptionRate$ -- `s` = $\frac{Stake}{Supply}$ - - \ No newline at end of file diff --git a/content/docs/subnets/maintain/delete-subnet.mdx b/content/docs/subnets/maintain/delete-subnet.mdx index 03f244ca806..016114382c1 100644 --- a/content/docs/subnets/maintain/delete-subnet.mdx +++ b/content/docs/subnets/maintain/delete-subnet.mdx @@ -9,7 +9,7 @@ Deleting a Subnet Configuration[​](#deleting-a-subnet-configuration "Direct li To delete a created Subnet configuration, run: ```bash -avalanche subnet delete +avalanche blockchain delete ``` Deleting a Deployed Subnet[​](#deleting-a-deployed-subnet "Direct link to heading") diff --git a/content/docs/subnets/maintain/view-subnets.mdx b/content/docs/subnets/maintain/view-subnets.mdx index f2b1e6a6562..f42bcb2fade 100644 --- a/content/docs/subnets/maintain/view-subnets.mdx +++ b/content/docs/subnets/maintain/view-subnets.mdx @@ -4,7 +4,7 @@ description: Learn how to view Subnets deployed using Avalanche-CLI. --- ```bash -avalanche subnet list +avalanche blockchain list # output +-------------+-------------+----------+---------------------------------------------------+------------+-----------+ @@ -17,7 +17,7 @@ avalanche subnet list To see detailed information about your deployed Subnets, add the `--deployed` flag: ```bash -avalanche subnet list --deployed +avalanche blockchain list --deployed # output +-------------+-------------+---------------------------------------------------+---------------+-----------------------------------------------------------------+---------+ diff --git a/content/docs/subnets/upgrade/subnet-precompile-config.mdx b/content/docs/subnets/upgrade/subnet-precompile-config.mdx index 03f8b1925a1..20c4fd3085b 100644 --- a/content/docs/subnets/upgrade/subnet-precompile-config.mdx +++ b/content/docs/subnets/upgrade/subnet-precompile-config.mdx @@ -23,13 +23,13 @@ The [Precompiles](/subnets/upgrade/customize-subnet#network-upgrades-enabledisab To generate a valid `upgrade.json` file, run: ```bash -avalanche subnet upgrade generate testSubnet +avalanche blockchain upgrade generate testSubnet ``` If you didn't create `testSubnet` yet, you would see this result: ```bash -avalanche subnet upgrade generate testSubnet +avalanche blockchain upgrade generate testSubnet The provided subnet name "testSubnet" does not exist ``` @@ -38,7 +38,7 @@ Again, it makes no sense to try the upgrade command if the Subnet doesn't exist. If the Subnet definition exists, the tool launches a wizard. It may feel a bit redundant, but you first see some warnings, to draw focus to the dangers involved: ```bash -avalanche subnet upgrade generate testSubnet +avalanche blockchain upgrade generate testSubnet Performing a network upgrade requires coordinating the upgrade network-wide. A network upgrade changes the rule set used to process and verify blocks, such that any node that upgrades incorrectly or fails to upgrade by the time that upgrade goes into effect may become @@ -229,16 +229,16 @@ If the preceding requirements aren't met, the network upgrade command fails. Therefore, to apply your generated or imported upgrade configuration: ```bash -avalanche subnet upgrade apply testSubnet +avalanche blockchain upgrade apply testSubnet ``` A number of checks run. For example, if you created the Subnet but didn't deploy it locally: ```bash -avalanche subnet upgrade apply testSubnet +avalanche blockchain upgrade apply testSubnet Error: no deployment target available Usage: - avalanche subnet upgrade apply [subnetName] [flags] + avalanche blockchain upgrade apply [subnetName] [flags] Flags: --avalanchego-chain-config-dir string avalanchego's chain config file directory (default "/home/fabio/.avalanchego/chains") @@ -259,7 +259,7 @@ Go ahead and [deploy](/subnets/deploy-a-subnet/local-network) first your Subnet If you already had deployed the Subnet instead, you see something like this: ```bash -avalanche subnet upgrade apply testSubnet +avalanche blockchain upgrade apply testSubnet Use the arrow keys to navigate: ↓ ↑ → ← ? What deployment would you like to upgrade: ▸ Existing local deployment @@ -299,7 +299,7 @@ For this scenario to work, you should also have deployed the Subnet to the publi Assuming the Subnet has been already deployed to Fuji, when running the `apply` command, the tool notices the deployment: ```bash -avalanche subnet upgrade apply testSubnet +avalanche blockchain upgrade apply testSubnet Use the arrow keys to navigate: ↓ ↑ → ← ? What deployment would you like to upgrade: Existing local deployment @@ -317,7 +317,7 @@ If this is the case, the tool tries to install the upgrade file at the expected If you are _not_ using default paths, you can configure the path by providing the flag `--avalanchego-chain-config-dir` to the tool. For example: ```bash -avalanche subnet upgrade apply testSubnet --avalanchego-chain-config-dir /path/to/your/chains +avalanche blockchain upgrade apply testSubnet --avalanchego-chain-config-dir /path/to/your/chains ``` Make sure to identify correctly where your chain config dir is, or the node might fail to find it. @@ -325,7 +325,7 @@ Make sure to identify correctly where your chain config dir is, or the node migh If all is correct, the file gets installed: ```bash -avalanche subnet upgrade apply testSubnet +avalanche blockchain upgrade apply testSubnet ✔ Fuji The chain config dir avalanchego uses is set at /home/fabio/.avalanchego/chains Trying to install the upgrade files at the provided /home/fabio/.avalanchego/chains path @@ -337,7 +337,7 @@ If however the node is _not_ running on this same machine where you are executin To see the instructions about how to go about this, add the `--print` flag: ```bash -avalanche subnet upgrade apply testSubnet --print +avalanche blockchain upgrade apply testSubnet --print ✔ Fuji To install the upgrade file on your validator: @@ -377,14 +377,14 @@ Export the Upgrade File[​](#export-the-upgrade-file "Direct link to heading") If you have generated the upgrade file, you can export it: ```bash -avalanche subnet upgrade export testSubnet +avalanche blockchain upgrade export testSubnet ✔ Provide a path where we should export the file to: /tmp/testSubnet-upgrade.json ``` Just provide a valid path to the prompt, and the tool exports the file there. ```bash -avalanche subnet upgrade export testSubnet +avalanche blockchain upgrade export testSubnet Provide a path where we should export the file to: /tmp/testSubnet-upgrade.json Writing the upgrade bytes file to "/tmp/testSubnet-upgrade.json"... File written successfully. @@ -400,7 +400,7 @@ You or someone else might have generated the file elsewhere, or on another machi You can import the file: ```bash -avalanche subnet upgrade import testSubnet +avalanche blockchain upgrade import testSubnet Provide the path to the upgrade file to import: /tmp/testSubnet-upgrade.json ``` diff --git a/content/docs/subnets/upgrade/subnet-virtual-machine.mdx b/content/docs/subnets/upgrade/subnet-virtual-machine.mdx index 28646b28346..1c0742d578c 100644 --- a/content/docs/subnets/upgrade/subnet-virtual-machine.mdx +++ b/content/docs/subnets/upgrade/subnet-virtual-machine.mdx @@ -17,7 +17,7 @@ Next, you need to select the new VM to run your Subnet on. If you're running a S Start the upgrade wizard with: ```bash -avalanche subnet upgrade vm +avalanche blockchain upgrade vm ``` where you replace `` with the name of the Subnet you would like to upgrade. diff --git a/content/docs/tooling/avalanche-cli.mdx b/content/docs/tooling/avalanche-cli.mdx index cb7bbffc914..04eb16c592b 100644 --- a/content/docs/tooling/avalanche-cli.mdx +++ b/content/docs/tooling/avalanche-cli.mdx @@ -62,7 +62,7 @@ This command currently only works on Subnets deployed to either the Fuji Testnet **Usage**: ```bash -avalanche subnet addValidator [subnetName] [flags] +avalanche blockchain addValidator [subnetName] [flags] ``` **Flags**: @@ -95,7 +95,7 @@ This command removes a node as a validator in a Subnet. **Usage**: ```bash -avalanche subnet removeValidator [subnetName] [flags] +avalanche blockchain removeValidator [subnetName] [flags] ``` **Flags**: @@ -122,7 +122,7 @@ This command currently only works on Subnets deployed to Devnet, Fuji or Mainnet **Usage**: ```bash -avalanche subnet changeOwner [subnetName] [flags] +avalanche blockchain changeOwner [subnetName] [flags] ``` **Flags**: @@ -153,7 +153,7 @@ AvalancheGo nodes support several different configuration files. Subnets have th **Usage**: ```bash -avalanche subnet configure [subnetName] [flags] +avalanche blockchain configure [subnetName] [flags] ``` **Flags**: @@ -211,7 +211,7 @@ The `subnet delete` command deletes an existing Subnet configuration. **Usage**: ```bash -avalanche subnet delete [flags] +avalanche blockchain delete [flags] ``` **Flags**: @@ -285,7 +285,7 @@ The command prompts for an output path. You can also provide one with the `--out **Usage**: ```bash -avalanche subnet export [subnetName] [flags] +avalanche blockchain export [subnetName] [flags] ``` **Flags**: @@ -308,7 +308,7 @@ To import from a file, you can optionally provide the path as a command-line arg **Usage**: ```bash -avalanche subnet import file [subnetPath] [flags] +avalanche blockchain import file [subnetPath] [flags] ``` **Flags**: @@ -330,7 +330,7 @@ The genesis file should be available from the disk for this to work. By default, **Usage**: ```bash -avalanche subnet import public [subnetPath] [flags] +avalanche blockchain import public [subnetPath] [flags] ``` **Flags**: @@ -362,7 +362,7 @@ This command currently only supports Subnets deployed on the Fuji Testnet and Ma **Usage**: ```bash -avalanche subnet join [subnetName] [flags] +avalanche blockchain join [subnetName] [flags] ``` **Flags**: @@ -389,7 +389,7 @@ The `subnet list` command prints the names of all created Subnet configurations. **Usage**: ```bash -avalanche subnet list [flags] +avalanche blockchain list [flags] ``` **Flags**: @@ -406,7 +406,7 @@ The `subnet publish` command publishes the Subnet's VM to a repository. **Usage**: ```bash -avalanche subnet publish [subnetName] [flags] +avalanche blockchain publish [subnetName] [flags] ``` **Flags**: @@ -428,7 +428,7 @@ The `subnet stats` command prints validator statistics for the given Subnet. **Usage**: ```bash -avalanche subnet stats [subnetName] [flags] +avalanche blockchain stats [subnetName] [flags] ``` **Flags**: @@ -447,7 +447,7 @@ The `subnet vmid` command prints the virtual machine ID (VMID) for the given Sub **Usage**: ```bash -avalanche subnet vmid [subnetName] +avalanche blockchain vmid [subnetName] ``` Elastic Subnet[​](#elastic-subnet "Direct link to heading") @@ -460,7 +460,7 @@ This command transforms your permissioned Subnet into an Elastic Subnet (NOTE: t **Usage**: ```bash -avalanche subnet elastic [subnetName] [flags] +avalanche blockchain elastic [subnetName] [flags] ``` **Flags**: @@ -493,7 +493,7 @@ This command adds a node as a permissionless validator in an Elastic Subnet. **Usage**: ```bash -avalanche subnet join [subnetName] --elastic [flags] +avalanche blockchain join [subnetName] --elastic [flags] ``` **Flags**: @@ -519,7 +519,7 @@ This command delegates stake to a permissionless validator in an Elastic Subnet. **Usage**: ```bash -avalanche subnet addPermissionlessDelegator [subnetName] [flags] +avalanche blockchain addPermissionlessDelegator [subnetName] [flags] ``` **Flags**: @@ -554,7 +554,7 @@ After you update your validator's configuration, you need to restart your valida **Usage**: ```bash -avalanche subnet upgrade apply [subnetName] [flags] +avalanche blockchain upgrade apply [subnetName] [flags] ``` **Flags**: @@ -578,7 +578,7 @@ Export the upgrade bytes file to a location of choice on disk. **Usage**: ```bash -avalanche subnet upgrade export [subnetName] [flags] +avalanche blockchain upgrade export [subnetName] [flags] ``` **Flags**: @@ -596,7 +596,7 @@ The `subnet upgrade generate` command builds a new upgrade.json file to customiz **Usage**: ```bash -avalanche subnet upgrade generate [subnetName] [flags] +avalanche blockchain upgrade generate [subnetName] [flags] ``` **Flags**: @@ -612,7 +612,7 @@ Import the upgrade bytes file into the local environment. **Usage**: ```bash -avalanche subnet upgrade import [subnetName] [flags] +avalanche blockchain upgrade import [subnetName] [flags] ``` **Flags**: @@ -629,7 +629,7 @@ Print the upgrade.json file content. **Usage**: ```bash -avalanche subnet upgrade print [subnetName] [flags] +avalanche blockchain upgrade print [subnetName] [flags] ``` **Flags**: @@ -643,7 +643,7 @@ The command walks the user through an interactive wizard. The user can skip the **Usage**: ```bash -avalanche subnet upgrade export [subnetName] [flags] +avalanche blockchain upgrade export [subnetName] [flags] ``` **Flags**: diff --git a/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx b/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx index 58ae8351372..d2be564a3b3 100644 --- a/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx +++ b/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx @@ -244,7 +244,7 @@ into a file with path `` (for example `~/morpheusvm_avago.json`) Then set the Subnet to use it by executing: ```bash -avalanche subnet configure subnetName +avalanche blockchain configure subnetName ``` Select node-config.json: @@ -307,7 +307,7 @@ in a known file path (for example `~/morpheusvm_chain.json`): Then set the Subnet to use it by executing: ```bash -avalanche subnet configure subnetName +avalanche blockchain configure subnetName ``` Select chain.json: @@ -352,7 +352,7 @@ in a known path (for example `~/morpheusvm_subnet.json`): Then set the Subnet to use it by executing: ```bash -avalanche subnet configure subnetName +avalanche blockchain configure subnetName ``` Select `subnet.json`: @@ -389,7 +389,7 @@ Save the following content (currently with no network upgrades) in a known path Then set the Subnet to use it by executing: ```bash -avalanche subnet upgrade import subnetName +avalanche blockchain upgrade import subnetName ``` Provide the path to the network upgrades file: diff --git a/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx b/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx index fa79dc2fe25..4603681fcf1 100644 --- a/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx +++ b/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx @@ -345,7 +345,7 @@ No precompiles set Also you can list the available Subnets: ```bash -avalanche subnet list +avalanche blockchain list go run main.go subnet list +-------------+-------------+----------+---------------------------------------------------+------------+-----------+ | SUBNET | CHAIN | CHAIN ID | VM ID | TYPE | FROM REPO | @@ -357,7 +357,7 @@ go run main.go subnet list List deployed information: ```bash -avalanche subnet list --deployed +avalanche blockchain list --deployed go run main.go subnet list --deployed +-------------+-------------+---------------------------------------------------+---------------+-----------------------------------------------------------------+---------+ | SUBNET | CHAIN | VM ID | LOCAL NETWORK | FUJI (TESTNET) | MAINNET | @@ -472,7 +472,7 @@ See [here](/nodes/validate/node-validator#add-a-validator-with-core-extension) o First, request permission to validate by running the `join` command along with the Subnet name: ```bash -avalanche subnet join testsubnet +avalanche blockchain join testsubnet ``` Note: Running `join` does not guarantee that your node is a validator of the Subnet! The owner of the Subnet must approve your node to be a validator afterwards by calling `addValidator` as described in the next section. @@ -574,7 +574,7 @@ Now that the node has joined the Subnet, a Subnet control key holder must call ` To whitelist a node as a recognized validator on the Subnet, run: ```bash -avalanche subnet addValidator testsubnet +avalanche blockchain addValidator testsubnet ``` As this operation involves a new transaction, you will need to specify which private key to use: @@ -676,7 +676,7 @@ Subnet Export[​](#subnet-export "Direct link to heading") This tool is most useful on the machine where a validator is or is going to be running. In order to allow a VM to run on a different machine, you can export the configuration. Just need to provide a path to where to export the data: ```bash -avalanche subnet export testsubnet +avalanche blockchain export testsubnet ✔ Enter file path to write export data to: /tmp/testsubnet-export.dat ``` @@ -688,14 +688,14 @@ Subnet Import[​](#subnet-import "Direct link to heading") To import a VM specification exported in the previous section, just issue the `import` command with the path to the file after having copied the file over: ```bash -avalanche subnet import /tmp/testsubnet-export.dat +avalanche blockchain import /tmp/testsubnet-export.dat Subnet imported successfully ``` After this the whole Subnet configuration should be available on the target machine: ```bash -avalanche subnet list +avalanche blockchain list +---------------+---------------+----------+-----------+----------+ | SUBNET | CHAIN | CHAIN ID | TYPE | DEPLOYED | +---------------+---------------+----------+-----------+----------+ diff --git a/content/docs/tooling/create-deploy-subnets/deploy-on-mainnet.mdx b/content/docs/tooling/create-deploy-subnets/deploy-on-mainnet.mdx index 837c51fdb9b..f9dbd269f9b 100644 --- a/content/docs/tooling/create-deploy-subnets/deploy-on-mainnet.mdx +++ b/content/docs/tooling/create-deploy-subnets/deploy-on-mainnet.mdx @@ -218,7 +218,7 @@ See [here](/nodes/validate/node-validator#add-a-validator-with-core-extension) o First, request permission to validate by running the `join` command along with the Subnet name: ```bash -avalanche subnet join testsubnet +avalanche blockchain join testsubnet ``` Note: Running `join` does not guarantee that your node is a validator of the Subnet! The owner of the Subnet must approve your node to be a validator afterwards by calling `addValidator` as described in the next section. @@ -335,7 +335,7 @@ Now that the node has joined the Subnet, a Subnet control key holder must call ` To whitelist a node as a recognized validator on the Subnet, run: ```bash -avalanche subnet addValidator testsubnet +avalanche blockchain addValidator testsubnet ``` You need to repeat this process for every validator you add to the network. @@ -489,7 +489,7 @@ Subnet Export[​](#subnet-export "Direct link to heading") Because you need to setup multiple validators on multiple different machines, you need to export your Subnet's configuration and import it on each validator. ```bash -avalanche subnet export testsubnet +avalanche blockchain export testsubnet ✔ Enter file path to write export data to: /tmp/testsubnet-export.dat ``` @@ -501,14 +501,14 @@ Subnet Import[​](#subnet-import "Direct link to heading") To import a VM configuration, move the file you exported in the previous section to your desired machine and issue the `import` command with the path to the file. ```bash -avalanche subnet import /tmp/testsubnet-export.dat +avalanche blockchain import /tmp/testsubnet-export.dat Subnet imported successfully ``` After this the whole Subnet configuration should be available on the target machine: ```bash -avalanche subnet list +avalanche blockchain list +---------------+---------------+----------+-----------+----------+ | SUBNET | CHAIN | CHAIN ID | TYPE | DEPLOYED | +---------------+---------------+----------+-----------+----------+ diff --git a/content/docs/tooling/create-deploy-subnets/view-subnets.mdx b/content/docs/tooling/create-deploy-subnets/view-subnets.mdx index f8fd85f91fb..f787ae5e0e1 100644 --- a/content/docs/tooling/create-deploy-subnets/view-subnets.mdx +++ b/content/docs/tooling/create-deploy-subnets/view-subnets.mdx @@ -5,12 +5,12 @@ description: CLI commands for viewing subnets. ## List Subnet Configurations -You can list the Subnets you've created with: `avalanche subnet list` +You can list the Subnets you've created with: `avalanche blockchain list` Example: ```bash -> avalanche subnet list +> avalanche blockchain list +-------------+-------------+----------+---------------------------------------------------+------------+-----------+ | SUBNET | CHAIN | CHAIN ID | VM ID | TYPE | FROM REPO | +-------------+-------------+----------+---------------------------------------------------+------------+-----------+ @@ -21,7 +21,7 @@ Example: To see detailed information about your deployed Subnets, add the `--deployed` flag: ```bash -> avalanche subnet list --deployed +> avalanche blockchain list --deployed +-------------+-------------+---------------------------------------------------+---------------+-----------------------------------------------------------------+---------+ | SUBNET | CHAIN | VM ID | LOCAL NETWORK | FUJI (TESTNET) | MAINNET | +-------------+-------------+---------------------------------------------------+---------------+-----------------------------------------------------------------+---------+ diff --git a/content/docs/tooling/guides/import-subnet.mdx b/content/docs/tooling/guides/import-subnet.mdx index 4c5f4c303bd..2ebaa8df426 100644 --- a/content/docs/tooling/guides/import-subnet.mdx +++ b/content/docs/tooling/guides/import-subnet.mdx @@ -27,7 +27,7 @@ For these use cases, Avalanche-CLI now supports the `import public` command. Start the import by issuing ``` -avalanche subnet import public +avalanche blockchain import public ``` The tool prompts for the network from which to import. The invariant assumption here is that the network is a public network, either the Fuji testnet or Mainnet. In other words, importing from a local network isn't supported. diff --git a/next.config.mjs b/next.config.mjs index 978210323f0..600548e9eaa 100644 --- a/next.config.mjs +++ b/next.config.mjs @@ -110,16 +110,6 @@ const config = { destination: '/subnets/upgrade/considerations', permanent: true, }, - { - source: '/build/subnet/elastic/transform-to-elastic-subnet', - destination: '/subnets/elastic-subnets/make-subnet-permissionless', - permanent: true, - }, - { - source: '/build/subnet/elastic/elastic-parameters', - destination: '/subnets/elastic-subnets/parameters', - permanent: true, - }, { source: '/build/subnet/deploy/mainnet-subnet', destination: '/subnets/deploy-a-subnet/avalanche-mainnet', From 8f05aa2a1334bd8c64282f7db49e73fa1187fa3f Mon Sep 17 00:00:00 2001 From: owenwahlgren Date: Fri, 23 Aug 2024 16:35:17 -0400 Subject: [PATCH 03/10] fix: readd elastic subnet docs --- .../make-subnet-permissionless.mdx | 80 ++++++ .../subnets/elastic-subnets/parameters.mdx | 238 ++++++++++++++++++ next.config.mjs | 10 + 3 files changed, 328 insertions(+) create mode 100644 content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx create mode 100644 content/docs/subnets/elastic-subnets/parameters.mdx diff --git a/content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx b/content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx new file mode 100644 index 00000000000..75c9ffd7aea --- /dev/null +++ b/content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx @@ -0,0 +1,80 @@ +--- +title: Make Subnet Permissionless +description: Learn how to transform a Permissioned Subnet into an Elastic Subnet. +--- + +Elastic Subnets are permissionless Subnets. More information can be found [here](/subnets/elastic-subnets/parameters). + +This how-to guide focuses on taking an already created permissioned Subnet and transforming it to an elastic (or permissionless) Subnet. + +## Prerequisites + +- [Avalanche-CLI installed](/tooling/guides/get-avalanche-cli) +- You have deployed a permissioned Subnet on [local](/subnets/deploy-a-subnet/local-network), on [Fuji](/subnets/deploy-a-subnet/fuji-testnet) or on [Mainnet](/subnets/deploy-a-subnet/avalanche-mainnet) + +Getting Started[​](#getting-started "Direct link to heading") +------------------------------------------------------------- + +In the following commands, make sure to substitute the name of your Subnet configuration for ``. + +To transform your permissioned Subnet into an Elastic Subnet (NOTE: this action is irreversible), run: + +```bash +avalanche subnet elastic +``` + +and, select the network that you want to transform the Subnet on. Alternatively, you can bypass this prompt by providing the `--local`, `--fuji`, or `--mainnet` flag. + +Provide the name and the symbol for the permissionless Subnet's native token. You can also bypass this prompt by providing the `--tokenName` and `--tokenSymbol` flags. + +Next, select the Elastic Subnet config. You can choose to use the default values detailed [here](/subnets/elastic-subnets/parameters#primary-network-parameters-on-mainnet) or customize the Elastic Subnet config. To bypass the prompt, you can use `--default` flag to use the default Elastic Subnet config. + +The command may take a couple minutes to run. + +### Elastic Subnet Transformation on Fuji and Mainnet[​](#elastic-subnet-transformation-on-fuji-and-mainnet "Direct link to heading") + +Elastic Subnet transformation on public network requires private key loaded into the tool, or a connected ledger device. + +Both stored key usage and ledger usage are enabled on Fuji (see more on creating keys [here](/subnets/deploy-a-subnet/fuji-testnet#private-key)) while only ledger usage is enabled on Mainnet (see more on setting up your ledger [here](/subnets/deploy-a-subnet/avalanche-mainnet#setting-up-your-ledger)). + +To transform a permissioned Subnet into Elastic Subnet on public networks, users are required to provide the keys that control the Subnet defined during the Subnet deployment process (more info on keys in Fuji can be found [here](/subnets/deploy-a-subnet/fuji-testnet#deploy-the-subnet), while more info on ledger signing in Mainnet can be found [here](/subnets/deploy-a-subnet/avalanche-mainnet#deploy-the-subnet)). + +### Results[​](#results "Direct link to heading") + +If all works as expected, you then have the option to automatically transform all existing permissioned validators to permissionless validators. + +You can also to skip automatic transformation at this point and choose to manually add permissionless validators later. + +You can use the output details such as the Asset ID and Elastic Subnet ID to connect to and interact with your Elastic Subnet. + +Adding Permissionless Validators to Elastic Subnet[​](#adding-permissionless-validators-to-elastic-subnet "Direct link to heading") +----------------------------------------------------------------------------------------------------------------------------------- + +If you are running this command on local network, you will need to first remove permissioned validators (by running `avalanche subnet removeValidator `) so that you can have a list of local nodes to choose from to be added as a permissionless validator in the Elastic Subnet. + +To add permissionless validators to an Elastic Subnet, run: + +```bash +avalanche subnet join --elastic +``` + +You will be prompted with which node you would like to add as a permissionless validator. You can skip this prompt by using `--nodeID` flag. + +You will then be prompted with the amount of the Subnet native token that you like to stake in the validator. Alternatively, you can bypass this prompt by providing the `--stake-amount` flag. Note that choosing to add the maximum validator stake amount (defined during Elastic Subnet transformation step above) means that you effectively disable delegation in your validator. + +Next, select when the validator will start validating and how long it will be validating for. You can also bypass these prompts by using `--start-time` and `--staking-period` flags. + +Adding Permissionless Delegator to a Permissionless Validator in Elastic Subnet[​](#adding-permissionless-delegator-to-a-permissionless-validator-in-elastic-subnet "Direct link to heading") +--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- + +To add permissionless delegators, run: + +```bash +avalanche subnet addPermissionlessDelegator +``` + +You will be prompted with which Subnet validator you would like to delegate to. You can skip this prompt by using `--nodeID` flag. + +You will then be prompted with the amount of the Subnet native token that you like to stake in the validator. Alternatively, you can bypass this prompt by providing the `--stake-amount` flag. The amount that can be delegated to a validator is detailed [here](/subnets/elastic-subnets/parameters#delegators-weight-checks). + +Next, select when you want to start delegating and how long you want to delegate for. You can also bypass these prompts by using `--start-time` and `--staking-period` flags. \ No newline at end of file diff --git a/content/docs/subnets/elastic-subnets/parameters.mdx b/content/docs/subnets/elastic-subnets/parameters.mdx new file mode 100644 index 00000000000..280ffc386df --- /dev/null +++ b/content/docs/subnets/elastic-subnets/parameters.mdx @@ -0,0 +1,238 @@ +--- +title: Parameters +description: Learn about the different parameters of Elastic Subnets. +--- + +Avalanche Permissioned Subnets can be turned into Elastic Subnets via the `TransformSubnetTx` transaction. `TransformSubnetTx` specifies a set of structural parameters for the Elastic Subnet. + +This reference document describes these structural parameters and illustrates the constraints they must satisfy. + +## Elastic Subnet Parameters + +### `Subnet` + +`Subnet` has type `ids.ID` and it's the Subnet ID. `Subnet` is the ID of the `CreateSubnetTx` transaction that created the Subnet in the first place. The following constraints apply: + +- `Subnet` must be different from `PrimaryNetworkID`. + +### `AssetID` + +`AssetID` has type `ids.ID` and it's the ID of the asset to use when staking on the Subnet. The following constraints apply: + +- `AssetID` must not be the `Empty ID`. +- `AssetID` must not be `AVAX ID`, the Primary Network asset. + +### `InitialSupply` + +`InitialSupply` has type `uint64` and it's the initial amount of `AssetID` transferred in the Elastic Subnet upon its transformation. Such amount is available for distributing staking rewards. The following constraints apply: + +- `InitialSupply` must be larger than zero. + +### `MaximumSupply` + +`MaximumSupply` has type `uint64` and it's the maximum amount of `AssetID` that Subnet has available for staking and rewards at any time. The following constraints apply: + +- `MaximumSupply` must be larger or equal to `InitialSupply`. + +A Subnet supply can vary in time but it should be no larger than the configured maximum at any point in time, including at Subnet creation. + +### `MinConsumptionRate` + +`MinConsumptionRate` has type `uint64` and it's the minimal rate a validator can earn if the `UptimeRequirement` is satisfied. If `StakingPeriod` == `MinStakeDuration`, the validator will earn the `MinConsumptionRate`. + +You can find more details about it in the [Reward Formula section](#reward-formula). The following constraints apply: + +- `MinConsumptionRate` must be smaller or equal to `PercentDenominator`. + +See [Notes on Percentages](#notes-on-percentages) section to understand `PercentDenominator` role. + +### `MaxConsumptionRate` + +`MaxConsumptionRate` has type `uint64` and it's the maximal rate a validator can earn if the `UptimeRequirement` is satisfied. If `StakingPeriod` == `MaxStakeDuration` == `MintingPeriod`, the validator will earn the `MaxConsumptionRate`. + +You can find more details about it in the [Reward Formula section](#reward-formula). The following constraints apply: + +- `MaxConsumptionRate` must be larger or equal to `MinConsumptionRate`. +- `MaxConsumptionRate` must be smaller or equal to `PercentDenominator`. + +See [Notes on Percentages](#notes-on-percentages) section to understand `PercentDenominator` role. + +### `MinValidatorStake` + +`MinValidatorStake` has type `uint64` and it's the minimum amount of funds required to become a validator. The following constraints apply: + +- `MinValidatorStake` must be larger than zero +- `MinValidatorStake` must be smaller or equal to `InitialSupply` + +### `MaxValidatorStake` + +`MaxValidatorStake` has type `uint64` and it's the maximum amount of funds a single validator can be allocated, including delegated funds. The following constraints apply: + +- `MaxValidatorStake` must be larger or equal to `MinValidatorStake` +- `MaxValidatorStake` must be smaller or equal to `MaximumSupply` + +### `MinStakeDuration` + +`MinStakeDuration` has type `uint32` and it's the minimum number of seconds a staker can stake for. The following constraints apply: + +- `MinStakeDuration` must be larger than zero. + +### `MaxStakeDuration` + +`MaxStakeDuration` has type `uint32` and it's the maximum number of seconds a staker can stake for. The following constraints apply: + +- `MaxStakeDuration` must be larger or equal to `MinStakeDuration`. +- `MaxStakeDuration` must be smaller or equal to `GlobalMaxStakeDuration`. + +`GlobalMaxStakeDuration` is defined in genesis and applies to both the Primary Network and all Subnets. + +Its Mainnet value is $365 \times 24 \times time.Hour$. + +### `MinDelegationFee` + +`MinDelegationFee` has type `uint32` and it's the minimum fee rate a delegator must pay to its validator for delegating. `MinDelegationFee` is a percentage; the actual fee is calculated multiplying the fee rate for the delegator reward. The following constraints apply: + +- `MinDelegationFee` must be smaller or equal to `PercentDenominator`. + +The `MinDelegationFee` rate applies to Primary Network as well. Its Mainnet value is $2\%$. + +### `MinDelegatorStake` + +`MinDelegatorStake` has type `uint64` and it's the minimum amount of funds required to become a delegator. The following constraints apply: + +- `MinDelegatorStake` must be larger than zero. + +### `MaxValidatorWeightFactor` + +`MaxValidatorWeightFactor` has type `uint8` and it's the factor which calculates the maximum amount of delegation a validator can receive. A value of 1 effectively disables delegation. You can find more details about it in the [Delegators Weight Checks section](#delegators-weight-checks). The following constraints apply: + +- `MaxValidatorWeightFactor` must be larger than zero. + +### `UptimeRequirement` + +`UptimeRequirement` has type `uint32` and it's the minimum percentage of its staking time that a validator must be online and responsive for to receive a reward. The following constraints apply: + +- `UptimeRequirement` must be smaller or equal `PercentDenominator`. + +See [Notes on Percentages](#notes-on-percentages) section to understand `PercentDenominator` role. + +## Reward Formula + +Consider an Elastic Subnet validator which stakes a $Stake$ amount `AssetID` for $StakingPeriod$ seconds. + +Assume that at the start of the staking period there is a $Supply$ amount of `AssetID` in the Subnet. The maximum amount of Subnet asset is $MaximumSupply$ `AssetID`. + +Then at the end of its staking period, a responsive Elastic Subnet validator receives a reward calculated as follows: + +$$ +Reward = \left(MaximumSupply - Supply \right) \times \frac{Stake}{Supply} \times \frac{Staking Period}{Minting Period} \times EffectiveConsumptionRate +$$ + +where, + +$$ +MaximumSupply - Supply = \text{the number of tokens left to emit in the subnet} +$$ + +$$ +\frac{Stake}{Supply} = \text{the individual's stake as a percentage of all available tokens in the network} +$$ + +$$ +\frac{StakingPeriod}{MintingPeriod} = \text{time tokens are locked up divided by the $MintingPeriod$} +$$ + +$$ +\text{$MintingPeriod$ is one year as configured by the Primary Network).} +$$ + +$$ +EffectiveConsumptionRate = +$$ + +$$ +\frac{MinConsumptionRate}{PercentDenominator} \times \left(1- \frac{Staking Period}{Minting Period}\right) + \frac{MaxConsumptionRate}{PercentDenominator} \times \frac{Staking Period}{Minting Period} +$$ + +Note that $StakingPeriod$ is the staker's entire staking period, not just the staker's uptime, that is the aggregated time during which the staker has been responsive. The uptime comes into play only to decide whether a staker should be rewarded; to calculate the actual reward only the staking period duration is taken into account. + +$EffectiveConsumptionRate$ is the rate at which the validator is rewarded based on $StakingPeriod$ selection. + +$MinConsumptionRate$ and $MaxConsumptionRate$ bound $EffectiveConsumptionRate$: + +$$ +MinConsumptionRate \leq EffectiveConsumptionRate \leq MaxConsumptionRate +$$ + +The larger $StakingPeriod$ is, the closer $EffectiveConsumptionRate$ is to $MaxConsumptionRate$. The smaller $StakingPeriod$ is, the closer $EffectiveConsumptionRate$ is to $MinConsumptionRate$. + +A staker achieves the maximum reward for its stake if $StakingPeriod$ = $Minting Period$. The reward is: + +$$ +Max Reward = \left(MaximumSupply - Supply \right) \times \frac{Stake}{Supply} \times \frac{MaxConsumptionRate}{PercentDenominator} +$$ + +Note that this formula is the same as the reward formula at the top of this section because $EffectiveConsumptionRate$ = $MaxConsumptionRate$. + +The reward formula above is used in the Primary Network to calculate stakers reward. For reference, you can find Primary network parameters in [the section below](#primary-network-parameters-on-mainnet). + +## Delegators Weight Checks + +There are bounds set of the maximum amount of delegators' stake that a validator can receive. + +The maximum weight $MaxWeight$ a validator $Validator$ can have is: + +$$ +MaxWeight = \min(Validator.Weight \times MaxValidatorWeightFactor, MaxValidatorStake) +$$ + +where $MaxValidatorWeightFactor$ and $MaxValidatorStake$ are the Elastic Subnet Parameters described above. + +A delegator won't be added to a validator if the combination of their weights and all other validator's delegators' weight is larger than $MaxWeight$. Note that this must be true at any point in time. + +Note that setting $MaxValidatorWeightFactor$ to 1 disables delegation since the $MaxWeight = Validator.Weight$. + +## Notes on Percentages + +`PercentDenominator = 1_000_000` is the denominator used to calculate percentages. + +It allows you to specify percentages up to 4 digital positions. To denominate your percentage in `PercentDenominator` just multiply it by `10_000`. For example: + +- `100%` corresponds to `100 * 10_000 = 1_000_000` +- `1%` corresponds to `1* 10_000 = 10_000` +- `0.02%` corresponds to `0.002 * 10_000 = 200` +- `0.0007%` corresponds to `0.0007 * 10_000 = 7` + +## Primary Network Parameters on Mainnet + +An Elastic Subnet is free to pick any parameters affecting rewards, within the constraints specified above. For reference we list below Primary Network parameters on Mainnet: + +- `AssetID = Avax` +- `InitialSupply = 240_000_000 Avax` +- `MaximumSupply = 720_000_000 Avax`. +- `MinConsumptionRate = 0.10 * reward.PercentDenominator`. +- `MaxConsumptionRate = 0.12 * reward.PercentDenominator`. +- `Minting Period = 365 * 24 * time.Hour`. +- `MinValidatorStake = 2_000 Avax`. +- `MaxValidatorStake = 3_000_000 Avax`. +- `MinStakeDuration = 2 * 7 * 24 * time.Hour`. +- `MaxStakeDuration = 365 * 24 * time.Hour`. +- `MinDelegationFee = 20000`, that is `2%`. +- `MinDelegatorStake = 25 Avax`. +- `MaxValidatorWeightFactor = 5`. This is a platformVM parameter rather than a genesis one, so it's shared across networks. +- `UptimeRequirement = 0.8`, that is `80%`. + +### Interactive Graph + +The graph below demonstrates the reward as a function of the length of time +staked. The x-axis depicts $\frac{StakingPeriod}{MintingPeriod}$ as a percentage +while the y-axis depicts $Reward$ as a percentage of $MaximumSupply - Supply$, +the amount of tokens left to be emitted. + +Graph variables correspond to those defined above: + +- `h` (high) = $MaxConsumptionRate$ +- `l` (low) = $MinConsumptionRate$ +- `s` = $\frac{Stake}{Supply}$ + + \ No newline at end of file diff --git a/next.config.mjs b/next.config.mjs index 600548e9eaa..978210323f0 100644 --- a/next.config.mjs +++ b/next.config.mjs @@ -110,6 +110,16 @@ const config = { destination: '/subnets/upgrade/considerations', permanent: true, }, + { + source: '/build/subnet/elastic/transform-to-elastic-subnet', + destination: '/subnets/elastic-subnets/make-subnet-permissionless', + permanent: true, + }, + { + source: '/build/subnet/elastic/elastic-parameters', + destination: '/subnets/elastic-subnets/parameters', + permanent: true, + }, { source: '/build/subnet/deploy/mainnet-subnet', destination: '/subnets/deploy-a-subnet/avalanche-mainnet', From 275f3c23f912950253e26c2fbea45014a429ab46 Mon Sep 17 00:00:00 2001 From: owenwahlgren Date: Fri, 23 Aug 2024 16:47:43 -0400 Subject: [PATCH 04/10] replace: -> , mySubnet -> myblockchain --- .../teleporter/teleporter-on-devnet.mdx | 20 +++--- .../teleporter-on-local-network.mdx | 70 +++++++++---------- content/docs/subnets/build-first-subnet.mdx | 26 +++---- .../subnets/deploy-a-subnet/local-network.mdx | 16 ++--- .../docs/subnets/maintain/pause-resume.mdx | 10 +-- content/docs/subnets/troubleshooting.mdx | 8 +-- .../create-deploy-subnets/create-subnet.mdx | 26 +++---- .../create-deploy-subnets/deploy-locally.mdx | 16 ++--- .../tooling/cross-chain/teleporter-devnet.mdx | 20 +++--- .../cross-chain/teleporter-local-network.mdx | 70 +++++++++---------- 10 files changed, 141 insertions(+), 141 deletions(-) diff --git a/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx b/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx index 4b5e743d68a..887a0b3f2b2 100644 --- a/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx +++ b/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx @@ -22,17 +22,17 @@ Note: the tutorial uses AWS hosts, but Devnets can also be created and operated Create Subnets Configurations[​](#create-subnets-configurations "Direct link to heading") ----------------------------------------------------------------------------------------- -For this section we will follow this [steps](/tooling/cross-chain/teleporter-local-network#create-subnets-configurations), to create two Teleporter-enabled Subnets, `` and ``. +For this section we will follow this [steps](/tooling/cross-chain/teleporter-local-network#create-subnets-configurations), to create two Teleporter-enabled Subnets, `` and ``. Create a Devnet and Deploy a Subnet in It[​](#create-a-devnet-and-deploy-a-subnet-in-it "Direct link to heading") ----------------------------------------------------------------------------------------------------------------- -Let's use the `devnet wiz` command to create a devnet `` and deploy `` in it. +Let's use the `devnet wiz` command to create a devnet `` and deploy `` in it. The devnet will be created in the `us-east-1` region of AWS, and will consist of 5 validators only. ``` -avalanche node devnet wiz --aws --node-type default --region us-east-1 --num-validators 5 --num-apis 0 --enable-monitoring=false --default-validator-params +avalanche node devnet wiz --aws --node-type default --region us-east-1 --num-validators 5 --num-apis 0 --enable-monitoring=false --default-validator-params Creating the devnet... @@ -61,7 +61,7 @@ updating configuration file ~/.avalanche-cli/nodes/i-0f1815c016b555fcc/services/ Devnet is successfully created and is now validating subnet subnet1! -Subnet RPC URL: http://67.202.23.231:9650/ext/bc/fqcM24LNb3kTV7KD1mAvUJXYy5XunwP8mrE44YuNwPjgZHY6p/rpc +Subnet RPC URL: http://67.202.23.231:9650/ext/bc/fqcM24LNb3kTV7KD1mAvUJXYy5XunwP8mrE44YuNwPjgZHY6p/rpc ✓ Cluster information YAML file can be found at ~/.avalanche-cli/nodes/inventories//clusterInfo.yaml at local host ``` @@ -127,12 +127,12 @@ Apr 05 14:15:08 ip-172-31-47-187 awm-relayer[6886]: {"level":"info","timestamp": Deploying the Second Subnet[​](#deploying-the-second-subnet "Direct link to heading") ------------------------------------------------------------------------------------- -Let's use the `devnet wiz` command again to deploy ``. +Let's use the `devnet wiz` command again to deploy ``. -When deploying Subnet ``, the two Teleporter contracts will not be deployed to C-Chain in Local Network as they have already been deployed when we deployed the first Subnet. +When deploying Subnet ``, the two Teleporter contracts will not be deployed to C-Chain in Local Network as they have already been deployed when we deployed the first Subnet. ``` -avalanche node devnet wiz --default-validator-params +avalanche node devnet wiz --default-validator-params Adding subnet into existing devnet ... ... @@ -158,7 +158,7 @@ updating configuration file ~/.avalanche-cli/nodes/i-0f1815c016b555fcc/services/ Devnet is now validating subnet subnet2 -Subnet RPC URL: http://67.202.23.231:9650/ext/bc/7gKt6evRnkA2uVHRfmk9WrH3dYZH9gEVVxDAknwtjvtaV3XuQ/rpc +Subnet RPC URL: http://67.202.23.231:9650/ext/bc/7gKt6evRnkA2uVHRfmk9WrH3dYZH9gEVVxDAknwtjvtaV3XuQ/rpc ✓ Cluster information YAML file can be found at ~/.avalanche-cli/nodes/inventories//clusterInfo.yaml at local host ``` @@ -199,10 +199,10 @@ By executing `subnet describe` on a Teleporter enabled Subnet, the following rel - Teleporter Messenger address - Teleporter Registry address -Let's get the information for ``: +Let's get the information for ``: ``` -avalanche blockchain describe +avalanche blockchain describe _____ _ _ _ | __ \ | | (_) | diff --git a/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx b/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx index a7bc8d60619..4faded9a03d 100644 --- a/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx +++ b/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx @@ -15,14 +15,14 @@ Note that currently only [Subnet-EVM](https://github.com/ava-labs/subnet-evm) an Create Subnet Configurations[​](#create-subnet-configurations "Direct link to heading") --------------------------------------------------------------------------------------- -Let's create a Subnet called `` with the latest Subnet-EVM version, a chain ID of 1, TOKEN1 as the token name, and with default Subnet-EVM parameters (more information regarding Subnet creation can be found [here](/subnets/build-first-subnet#create-your-subnet-configuration)): +Let's create a Subnet called `` with the latest Subnet-EVM version, a chain ID of 1, TOKEN1 as the token name, and with default Subnet-EVM parameters (more information regarding Subnet creation can be found [here](/subnets/build-first-subnet#create-your-subnet-configuration)): ``` -avalanche blockchain create --evm --latest\ +avalanche blockchain create --evm --latest\ --evm-chain-id 1 --evm-token TOKEN1 --evm-defaults creating genesis for -configuring airdrop to stored key "subnet__airdrop" with address 0x0EF8151A3e6ad1d4e17C8ED4128b20EB5edc58B1 +configuring airdrop to stored key "subnet__airdrop" with address 0x0EF8151A3e6ad1d4e17C8ED4128b20EB5edc58B1 loading stored key "cli-teleporter-deployer" for teleporter deploys (evm address, genesis balance) = (0xE932784f56774879e03F3624fbeC6261154ec711, 600000000000000000000) using latest teleporter version (v1.0.0) @@ -35,14 +35,14 @@ To disable Teleporter in your Subnet, use the flag `--teleporter=false` when cre To disable Relayer in your Subnet, use the flag `--relayer=false` when creating the Subnet. -Now let's create a second Subnet called ``, with similar settings: +Now let's create a second Subnet called ``, with similar settings: ``` -avalanche blockchain create --evm --latest\ +avalanche blockchain create --evm --latest\ --evm-chain-id 2 --evm-token TOKEN2 --evm-defaults creating genesis for -configuring airdrop to stored key "subnet__airdrop" with address 0x0EF815FFFF6ad1d4e17C8ED4128b20EB5edAABBB +configuring airdrop to stored key "subnet__airdrop" with address 0x0EF815FFFF6ad1d4e17C8ED4128b20EB5edAABBB loading stored key "cli-teleporter-deployer" for teleporter deploys (evm address, genesis balance) = (0xE932784f56774879e03F3624fbeC6261154ec711, 600000000000000000000) using latest teleporter version (v1.0.0) @@ -52,12 +52,12 @@ using latest teleporter version (v1.0.0) Deploy the Subnets to Local Network[​](#deploy-the-subnets-to-local-network "Direct link to heading") ----------------------------------------------------------------------------------------------------- -Let's deploy ``: +Let's deploy ``: ``` -avalanche blockchain deploy --local +avalanche blockchain deploy --local -Deploying [] to Local Network +Deploying [] to Local Network Backend controller started, pid: 149427, output at: ~/.avalanche-cli/runs/server_20240229_165923/avalanche-cli-backend.log Booting Network. Wait until healthy... @@ -69,8 +69,8 @@ Deploying Blockchain. Wait until network acknowledges... Teleporter Messenger successfully deployed to c-chain (0xF7cBd95f1355f0d8d659864b92e2e9fbfaB786f7) Teleporter Registry successfully deployed to c-chain (0x17aB05351fC94a1a67Bf3f56DdbB941aE6c63E25) -Teleporter Messenger successfully deployed to (0xF7cBd95f1355f0d8d659864b92e2e9fbfaB786f7) -Teleporter Registry successfully deployed to (0x9EDc4cB4E781413b1b82CC3A92a60131FC111F58) +Teleporter Messenger successfully deployed to (0xF7cBd95f1355f0d8d659864b92e2e9fbfaB786f7) +Teleporter Registry successfully deployed to (0x9EDc4cB4E781413b1b82CC3A92a60131FC111F58) Using latest awm-relayer version (v1.1.0) Executing AWM-Relayer... @@ -79,21 +79,21 @@ Blockchain ready to use. Local network node endpoints: +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ | NODE | VM | URL | ALIAS URL | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ -| node1 | | http://127.0.0.1:9650/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9650/ext/bc//rpc | +| node1 | | http://127.0.0.1:9650/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9650/ext/bc//rpc | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ -| node2 | | http://127.0.0.1:9652/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9652/ext/bc//rpc | +| node2 | | http://127.0.0.1:9652/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9652/ext/bc//rpc | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ -| node3 | | http://127.0.0.1:9654/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9654/ext/bc//rpc | +| node3 | | http://127.0.0.1:9654/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9654/ext/bc//rpc | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ -| node4 | | http://127.0.0.1:9656/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9656/ext/bc//rpc | +| node4 | | http://127.0.0.1:9656/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9656/ext/bc//rpc | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ -| node5 | | http://127.0.0.1:9658/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9658/ext/bc//rpc | +| node5 | | http://127.0.0.1:9658/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9658/ext/bc//rpc | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ Browser Extension connection details (any node URL from above works): RPC URL: http://127.0.0.1:9650/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc Funded address: 0x0EF8151A3e6ad1d4e17C8ED4128b20EB5edc58B1 with 1000000 (10^18) - private key: 16289399c9466912ffffffdc093c9b51124f0dc54ac7a766b2bc5ccf558d8eee -Network name: +Network name: Chain ID: 1 Currency Symbol: TOKEN1 ``` @@ -106,19 +106,19 @@ Notice some details here: CLI configures the Relayer to enable every Subnet to send messages to all other Subnets. If you add more Subnets, the Relayer will be automatically reconfigured. -When deploying Subnet ``, the two Teleporter contracts will not be deployed to C-Chain in Local Network as they have already been deployed when we deployed the first Subnet. +When deploying Subnet ``, the two Teleporter contracts will not be deployed to C-Chain in Local Network as they have already been deployed when we deployed the first Subnet. ``` -avalanche blockchain deploy --local +avalanche blockchain deploy --local -Deploying [] to Local Network +Deploying [] to Local Network Deploying Blockchain. Wait until network acknowledges... Teleporter Messenger has already been deployed to c-chain -Teleporter Messenger successfully deployed to (0xF7cBd95f1355f0d8d659864b92e2e9fbfaB786f7) -Teleporter Registry successfully deployed to (0x9EDc4cB4E781413b1b82CC3A92a60131FC111F58) +Teleporter Messenger successfully deployed to (0xF7cBd95f1355f0d8d659864b92e2e9fbfaB786f7) +Teleporter Registry successfully deployed to (0x9EDc4cB4E781413b1b82CC3A92a60131FC111F58) Using latest awm-relayer version (v1.1.0) Executing AWM-Relayer... @@ -127,31 +127,31 @@ Blockchain ready to use. Local network node endpoints: +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ | NODE | VM | URL | ALIAS URL | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node1 | | http://127.0.0.1:9650/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9650/ext/bc//rpc | +| node1 | | http://127.0.0.1:9650/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9650/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node1 | | http://127.0.0.1:9650/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9650/ext/bc//rpc | +| node1 | | http://127.0.0.1:9650/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9650/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node2 | | http://127.0.0.1:9652/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9652/ext/bc//rpc | +| node2 | | http://127.0.0.1:9652/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9652/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node2 | | http://127.0.0.1:9652/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9652/ext/bc//rpc | +| node2 | | http://127.0.0.1:9652/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9652/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node3 | | http://127.0.0.1:9654/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9654/ext/bc//rpc | +| node3 | | http://127.0.0.1:9654/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9654/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node3 | | http://127.0.0.1:9654/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9654/ext/bc//rpc | +| node3 | | http://127.0.0.1:9654/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9654/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node4 | | http://127.0.0.1:9656/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9656/ext/bc//rpc | +| node4 | | http://127.0.0.1:9656/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9656/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node4 | | http://127.0.0.1:9656/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9656/ext/bc//rpc | +| node4 | | http://127.0.0.1:9656/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9656/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node5 | | http://127.0.0.1:9658/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9658/ext/bc//rpc | +| node5 | | http://127.0.0.1:9658/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9658/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node5 | | http://127.0.0.1:9658/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9658/ext/bc//rpc | +| node5 | | http://127.0.0.1:9658/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9658/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ Browser Extension connection details (any node URL from above works): RPC URL: http://127.0.0.1:9650/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc Funded address: 0x0EF815FFFF6ad1d4e17C8ED4128b20EB5edAABBB with 1000000 (10^18) - private key: 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027 -Network name: +Network name: Chain ID: 2 Currency Symbol: TOKEN2 ``` @@ -194,10 +194,10 @@ By executing `subnet describe` on a Teleporter enabled Subnet, the following rel - Teleporter Messenger address - Teleporter Registry address -Let's get the information for ``: +Let's get the information for ``: ``` -avalanche blockchain describe +avalanche blockchain describe _____ _ _ _ | __ \ | | (_) | diff --git a/content/docs/subnets/build-first-subnet.mdx b/content/docs/subnets/build-first-subnet.mdx index dd1b5246ab7..dc711b4c2d7 100644 --- a/content/docs/subnets/build-first-subnet.mdx +++ b/content/docs/subnets/build-first-subnet.mdx @@ -35,10 +35,10 @@ This tutorials teaches you how to create an Ethereum Virtual Machine (EVM) based The Subnet command suite provides a collection of tools for developing and deploying Subnets. -The Subnet Creation Wizard walks you through the process of creating your Subnet. To get started, first pick a name for your Subnet. This tutorial uses `mySubnet`, but feel free to substitute that with any name you like. Once you've picked your name, run: +The Subnet Creation Wizard walks you through the process of creating your Subnet. To get started, first pick a name for your Subnet. This tutorial uses `myblockchain`, but feel free to substitute that with any name you like. Once you've picked your name, run: ```bash -avalanche blockchain create mySubnet +avalanche blockchain create myblockchain ``` The following sections walk through each question in the wizard. @@ -91,10 +91,10 @@ Deploying Subnets Locally[​](#deploying-subnets-locally "Direct link to headin To deploy your Subnet, run: ```bash -avalanche blockchain deploy mySubnet +avalanche blockchain deploy myblockchain ``` -Make sure to substitute the name of your Subnet if you used a different one than `mySubnet`. +Make sure to substitute the name of your Subnet if you used a different one than `myblockchain`. Next, select `Local Network`. @@ -105,11 +105,11 @@ Note: If you run `bash` on your shell and are running Avalanche-CLI on ARM64 on If all works as expected, the command output should look something like this: ```bash -avalanche blockchain deploy mySubnet +avalanche blockchain deploy myblockchain # output ✔ Local Network -Deploying [mySubnet] to Local Network +Deploying [myblockchain] to Local Network Installing subnet-evm-v0.4.3... subnet-evm-v0.4.3 installation successful Backend controller started, pid: 93928, output at: /Users/subnet-developer/.avalanche-cli/runs/server_20221122_173138/avalanche-cli-backend @@ -124,21 +124,21 @@ Network ready to use. Local network node endpoints: +-------+----------+------------------------------------------------------------------------------------+ | NODE | VM | URL | +-------+----------+------------------------------------------------------------------------------------+ -| node2 | mySubnet | http://127.0.0.1:9652/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node2 | myblockchain | http://127.0.0.1:9652/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node3 | mySubnet | http://127.0.0.1:9654/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node3 | myblockchain | http://127.0.0.1:9654/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node4 | mySubnet | http://127.0.0.1:9656/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node4 | myblockchain | http://127.0.0.1:9656/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node5 | mySubnet | http://127.0.0.1:9658/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node5 | myblockchain | http://127.0.0.1:9658/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node1 | mySubnet | http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node1 | myblockchain | http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ Browser Extension connection details (any node URL from above works): RPC URL: http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc Funded address: 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC with 1000000 (10^18) - private key: 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027 -Network name: mySubnet +Network name: myblockchain Chain ID: 54325 Currency Symbol: TUTORIAL ``` @@ -158,7 +158,7 @@ To allow API calls from other machines, use `--http-host=0.0.0.0` in the config. Browser Extension connection details (any node URL from above works): RPC URL: http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc Funded address: 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC with 1000000 (10^18) - private key: 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027 -Network name: mySubnet +Network name: myblockchain Chain ID: 54325 Currency Symbol: TUTORIAL ``` diff --git a/content/docs/subnets/deploy-a-subnet/local-network.mdx b/content/docs/subnets/deploy-a-subnet/local-network.mdx index 560084a0c80..258a69885d2 100644 --- a/content/docs/subnets/deploy-a-subnet/local-network.mdx +++ b/content/docs/subnets/deploy-a-subnet/local-network.mdx @@ -35,9 +35,9 @@ If you run `bash` on your shell and are running Avalanche-CLI on ARM64 on Mac, y If all works as expected, the command output should look something like this: ```bash -> avalanche blockchain deploy mySubnet +> avalanche blockchain deploy myblockchain ✔ Local Network -Deploying [mySubnet] to Local Network +Deploying [myblockchain] to Local Network Installing subnet-evm-v0.4.3... subnet-evm-v0.4.3 installation successful Backend controller started, pid: 93928, output at: /Users/subnet-developer/.avalanche-cli/runs/server_20221122_173138/avalanche-cli-backend @@ -52,21 +52,21 @@ Network ready to use. Local network node endpoints: +-------+----------+------------------------------------------------------------------------------------+ | NODE | VM | URL | +-------+----------+------------------------------------------------------------------------------------+ -| node2 | mySubnet | http://127.0.0.1:9652/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node2 | myblockchain | http://127.0.0.1:9652/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node3 | mySubnet | http://127.0.0.1:9654/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node3 | myblockchain | http://127.0.0.1:9654/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node4 | mySubnet | http://127.0.0.1:9656/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node4 | myblockchain | http://127.0.0.1:9656/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node5 | mySubnet | http://127.0.0.1:9658/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node5 | myblockchain | http://127.0.0.1:9658/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node1 | mySubnet | http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node1 | myblockchain | http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ Browser Extension connection details (any node URL from above works): RPC URL: http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc Funded address: 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC with 1000000 (10^18) - private key: 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027 -Network name: mySubnet +Network name: myblockchain Chain ID: 54325 Currency Symbol: TUTORIAL ``` diff --git a/content/docs/subnets/maintain/pause-resume.mdx b/content/docs/subnets/maintain/pause-resume.mdx index b75de9ce27e..98a1abeb21b 100644 --- a/content/docs/subnets/maintain/pause-resume.mdx +++ b/content/docs/subnets/maintain/pause-resume.mdx @@ -32,15 +32,15 @@ Network ready to use. Local network node endpoints: +-------+----------+------------------------------------------------------------------------------------+ | NODE | VM | URL | +-------+----------+------------------------------------------------------------------------------------+ -| node5 | mySubnet | http://127.0.0.1:9658/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node5 | myblockchain | http://127.0.0.1:9658/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node1 | mySubnet | http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node1 | myblockchain | http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node2 | mySubnet | http://127.0.0.1:9652/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node2 | myblockchain | http://127.0.0.1:9652/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node3 | mySubnet | http://127.0.0.1:9654/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node3 | myblockchain | http://127.0.0.1:9654/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node4 | mySubnet | http://127.0.0.1:9656/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node4 | myblockchain | http://127.0.0.1:9656/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ ``` diff --git a/content/docs/subnets/troubleshooting.mdx b/content/docs/subnets/troubleshooting.mdx index 70d1ec73587..a2217b86630 100644 --- a/content/docs/subnets/troubleshooting.mdx +++ b/content/docs/subnets/troubleshooting.mdx @@ -9,9 +9,9 @@ Deployment Times Out[​](#deployment-times-out "Direct link to heading") During a local deployment, your network may fail to start. Your error may look something like this: ```bash -[~]$ avalanche blockchain deploy mySubnet +[~]$ avalanche blockchain deploy myblockchain ✔ Local Network -Deploying [mySubnet] to Local Network +Deploying [myblockchain] to Local Network Backend controller started, pid: 26388, output at: /Users/user/.avalanche-cli/runs/server_20221231_111605/avalanche-cli-backend VMs ready. Starting network... @@ -47,9 +47,9 @@ Incompatible RPC Version for Custom VM[​](#incompatible-rpc-version-for-custom If you're locally deploying a custom VM, you may run into this error message. ```bash -[~]$ avalanche blockchain deploy mySubnet +[~]$ avalanche blockchain deploy myblockchain ✔ Local Network -Deploying [mySubnet] to Local Network +Deploying [myblockchain] to Local Network Backend controller started, pid: 26388, output at: /Users/user/.avalanche-cli/runs/server_20221231_111605/avalanche-cli-backend VMs ready. Starting network... diff --git a/content/docs/tooling/create-deploy-subnets/create-subnet.mdx b/content/docs/tooling/create-deploy-subnets/create-subnet.mdx index c7b0716d749..e688b7a06e2 100644 --- a/content/docs/tooling/create-deploy-subnets/create-subnet.mdx +++ b/content/docs/tooling/create-deploy-subnets/create-subnet.mdx @@ -33,10 +33,10 @@ This tutorials teaches you how to create an Ethereum Virtual Machine (EVM) based The Subnet command suite provides a collection of tools for developing and deploying Subnets. -The Subnet Creation Wizard walks you through the process of creating your Subnet. To get started, first pick a name for your Subnet. This tutorial uses `mySubnet`, but feel free to substitute that with any name you like. Once you've picked your name, run: +The Subnet Creation Wizard walks you through the process of creating your Subnet. To get started, first pick a name for your Subnet. This tutorial uses `myblockchain`, but feel free to substitute that with any name you like. Once you've picked your name, run: ```bash -avalanche blockchain create mySubnet +avalanche blockchain create myblockchain ``` The following sections walk through each question in the wizard. @@ -89,10 +89,10 @@ Deploying Subnets Locally[​](#deploying-subnets-locally "Direct link to headin To deploy your Subnet, run: ```bash -avalanche blockchain deploy mySubnet +avalanche blockchain deploy myblockchain ``` -Make sure to substitute the name of your Subnet if you used a different one than `mySubnet`. +Make sure to substitute the name of your Subnet if you used a different one than `myblockchain`. Next, select `Local Network`. @@ -103,9 +103,9 @@ Note: If you run `bash` on your shell and are running Avalanche-CLI on ARM64 on If all works as expected, the command output should look something like this: ```bash -> avalanche blockchain deploy mySubnet +> avalanche blockchain deploy myblockchain ✔ Local Network -Deploying [mySubnet] to Local Network +Deploying [myblockchain] to Local Network Installing subnet-evm-v0.4.3... subnet-evm-v0.4.3 installation successful Backend controller started, pid: 93928, output at: /Users/subnet-developer/.avalanche-cli/runs/server_20221122_173138/avalanche-cli-backend @@ -120,21 +120,21 @@ Network ready to use. Local network node endpoints: +-------+----------+------------------------------------------------------------------------------------+ | NODE | VM | URL | +-------+----------+------------------------------------------------------------------------------------+ -| node2 | mySubnet | http://127.0.0.1:9652/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node2 | myblockchain | http://127.0.0.1:9652/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node3 | mySubnet | http://127.0.0.1:9654/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node3 | myblockchain | http://127.0.0.1:9654/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node4 | mySubnet | http://127.0.0.1:9656/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node4 | myblockchain | http://127.0.0.1:9656/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node5 | mySubnet | http://127.0.0.1:9658/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node5 | myblockchain | http://127.0.0.1:9658/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node1 | mySubnet | http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node1 | myblockchain | http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ Browser Extension connection details (any node URL from above works): RPC URL: http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc Funded address: 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC with 1000000 (10^18) - private key: 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027 -Network name: mySubnet +Network name: myblockchain Chain ID: 54325 Currency Symbol: TUTORIAL ``` @@ -154,7 +154,7 @@ To allow API calls from other machines, use `--http-host=0.0.0.0` in the config. Browser Extension connection details (any node URL from above works): RPC URL: http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc Funded address: 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC with 1000000 (10^18) - private key: 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027 -Network name: mySubnet +Network name: myblockchain Chain ID: 54325 Currency Symbol: TUTORIAL ``` diff --git a/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx b/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx index 93a7786c39a..8cd88822472 100644 --- a/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx +++ b/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx @@ -36,9 +36,9 @@ Note: If you run `bash` on your shell and are running Avalanche-CLI on ARM64 on If all works as expected, the command output should look something like this: ```bash -> avalanche blockchain deploy mySubnet +> avalanche blockchain deploy myblockchain ✔ Local Network -Deploying [mySubnet] to Local Network +Deploying [myblockchain] to Local Network Installing subnet-evm-v0.4.3... subnet-evm-v0.4.3 installation successful Backend controller started, pid: 93928, output at: /Users/subnet-developer/.avalanche-cli/runs/server_20221122_173138/avalanche-cli-backend @@ -53,21 +53,21 @@ Network ready to use. Local network node endpoints: +-------+----------+------------------------------------------------------------------------------------+ | NODE | VM | URL | +-------+----------+------------------------------------------------------------------------------------+ -| node2 | mySubnet | http://127.0.0.1:9652/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node2 | myblockchain | http://127.0.0.1:9652/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node3 | mySubnet | http://127.0.0.1:9654/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node3 | myblockchain | http://127.0.0.1:9654/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node4 | mySubnet | http://127.0.0.1:9656/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node4 | myblockchain | http://127.0.0.1:9656/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node5 | mySubnet | http://127.0.0.1:9658/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node5 | myblockchain | http://127.0.0.1:9658/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ -| node1 | mySubnet | http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +| node1 | myblockchain | http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc | +-------+----------+------------------------------------------------------------------------------------+ Browser Extension connection details (any node URL from above works): RPC URL: http://127.0.0.1:9650/ext/bc/SPqou41AALqxDquEycNYuTJmRvZYbfoV9DYApDJVXKXuwVFPz/rpc Funded address: 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC with 1000000 (10^18) - private key: 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027 -Network name: mySubnet +Network name: myblockchain Chain ID: 54325 Currency Symbol: TUTORIAL ``` diff --git a/content/docs/tooling/cross-chain/teleporter-devnet.mdx b/content/docs/tooling/cross-chain/teleporter-devnet.mdx index fb51ecccea3..d072893219c 100644 --- a/content/docs/tooling/cross-chain/teleporter-devnet.mdx +++ b/content/docs/tooling/cross-chain/teleporter-devnet.mdx @@ -22,17 +22,17 @@ Note: the tutorial uses AWS hosts, but Devnets can also be created and operated Create Subnets Configurations[​](#create-subnets-configurations "Direct link to heading") ----------------------------------------------------------------------------------------- -For this section we will follow this [steps](/tooling/cross-chain/teleporter-local-network#create-subnets-configurations), to create two Teleporter-enabled Subnets, `` and ``. +For this section we will follow this [steps](/tooling/cross-chain/teleporter-local-network#create-subnets-configurations), to create two Teleporter-enabled Subnets, `` and ``. Create a Devnet and Deploy a Subnet in It[​](#create-a-devnet-and-deploy-a-subnet-in-it "Direct link to heading") ----------------------------------------------------------------------------------------------------------------- -Let's use the `devnet wiz` command to create a devnet `` and deploy `` in it. +Let's use the `devnet wiz` command to create a devnet `` and deploy `` in it. The devnet will be created in the `us-east-1` region of AWS, and will consist of 5 validators only. ```bash -avalanche node devnet wiz --aws --node-type default --region us-east-1 --num-validators 5 --num-apis 0 --enable-monitoring=false --default-validator-params +avalanche node devnet wiz --aws --node-type default --region us-east-1 --num-validators 5 --num-apis 0 --enable-monitoring=false --default-validator-params Creating the devnet... @@ -61,7 +61,7 @@ updating configuration file ~/.avalanche-cli/nodes/i-0f1815c016b555fcc/services/ Devnet is successfully created and is now validating subnet subnet1! -Subnet RPC URL: http://67.202.23.231:9650/ext/bc/fqcM24LNb3kTV7KD1mAvUJXYy5XunwP8mrE44YuNwPjgZHY6p/rpc +Subnet RPC URL: http://67.202.23.231:9650/ext/bc/fqcM24LNb3kTV7KD1mAvUJXYy5XunwP8mrE44YuNwPjgZHY6p/rpc ✓ Cluster information YAML file can be found at ~/.avalanche-cli/nodes/inventories//clusterInfo.yaml at local host ``` @@ -127,12 +127,12 @@ Apr 05 14:15:08 ip-172-31-47-187 awm-relayer[6886]: {"level":"info","timestamp": Deploying the Second Subnet[​](#deploying-the-second-subnet "Direct link to heading") ------------------------------------------------------------------------------------- -Let's use the `devnet wiz` command again to deploy ``. +Let's use the `devnet wiz` command again to deploy ``. -When deploying Subnet ``, the two Teleporter contracts will not be deployed to C-Chain in Local Network as they have already been deployed when we deployed the first Subnet. +When deploying Subnet ``, the two Teleporter contracts will not be deployed to C-Chain in Local Network as they have already been deployed when we deployed the first Subnet. ```bash -avalanche node devnet wiz --default-validator-params +avalanche node devnet wiz --default-validator-params Adding subnet into existing devnet ... ... @@ -158,7 +158,7 @@ updating configuration file ~/.avalanche-cli/nodes/i-0f1815c016b555fcc/services/ Devnet is now validating subnet subnet2 -Subnet RPC URL: http://67.202.23.231:9650/ext/bc/7gKt6evRnkA2uVHRfmk9WrH3dYZH9gEVVxDAknwtjvtaV3XuQ/rpc +Subnet RPC URL: http://67.202.23.231:9650/ext/bc/7gKt6evRnkA2uVHRfmk9WrH3dYZH9gEVVxDAknwtjvtaV3XuQ/rpc ✓ Cluster information YAML file can be found at ~/.avalanche-cli/nodes/inventories//clusterInfo.yaml at local host ``` @@ -199,10 +199,10 @@ By executing `subnet describe` on a Teleporter enabled Subnet, the following rel - Teleporter Messenger address - Teleporter Registry address -Let's get the information for ``: +Let's get the information for ``: ```bash -avalanche blockchain describe +avalanche blockchain describe _____ _ _ _ | __ \ | | (_) | diff --git a/content/docs/tooling/cross-chain/teleporter-local-network.mdx b/content/docs/tooling/cross-chain/teleporter-local-network.mdx index 2aaba5b2639..22bcb0ae678 100644 --- a/content/docs/tooling/cross-chain/teleporter-local-network.mdx +++ b/content/docs/tooling/cross-chain/teleporter-local-network.mdx @@ -18,14 +18,14 @@ Note that currently only [Subnet-EVM](https://github.com/ava-labs/subnet-evm) an Create Subnet Configurations[​](#create-subnet-configurations "Direct link to heading") --------------------------------------------------------------------------------------- -Let's create a Subnet called `` with the latest Subnet-EVM version, a chain ID of 1, TOKEN1 as the token name, and with default Subnet-EVM parameters (more information regarding Subnet creation can be found [here](/subnets/build-first-subnet#create-your-subnet-configuration)): +Let's create a Subnet called `` with the latest Subnet-EVM version, a chain ID of 1, TOKEN1 as the token name, and with default Subnet-EVM parameters (more information regarding Subnet creation can be found [here](/subnets/build-first-subnet#create-your-subnet-configuration)): ```bash -avalanche blockchain create --evm --latest\ +avalanche blockchain create --evm --latest\ --evm-chain-id 1 --evm-token TOKEN1 --evm-defaults creating genesis for -configuring airdrop to stored key "subnet__airdrop" with address 0x0EF8151A3e6ad1d4e17C8ED4128b20EB5edc58B1 +configuring airdrop to stored key "subnet__airdrop" with address 0x0EF8151A3e6ad1d4e17C8ED4128b20EB5edc58B1 loading stored key "cli-teleporter-deployer" for teleporter deploys (evm address, genesis balance) = (0xE932784f56774879e03F3624fbeC6261154ec711, 600000000000000000000) using latest teleporter version (v1.0.0) @@ -38,14 +38,14 @@ To disable Teleporter in your Subnet, use the flag `--teleporter=false` when cre To disable Relayer in your Subnet, use the flag `--relayer=false` when creating the Subnet. -Now let's create a second Subnet called ``, with similar settings: +Now let's create a second Subnet called ``, with similar settings: ```bash -avalanche blockchain create --evm --latest\ +avalanche blockchain create --evm --latest\ --evm-chain-id 2 --evm-token TOKEN2 --evm-defaults creating genesis for -configuring airdrop to stored key "subnet__airdrop" with address 0x0EF815FFFF6ad1d4e17C8ED4128b20EB5edAABBB +configuring airdrop to stored key "subnet__airdrop" with address 0x0EF815FFFF6ad1d4e17C8ED4128b20EB5edAABBB loading stored key "cli-teleporter-deployer" for teleporter deploys (evm address, genesis balance) = (0xE932784f56774879e03F3624fbeC6261154ec711, 600000000000000000000) using latest teleporter version (v1.0.0) @@ -55,12 +55,12 @@ using latest teleporter version (v1.0.0) Deploy the Subnets to Local Network[​](#deploy-the-subnets-to-local-network "Direct link to heading") ----------------------------------------------------------------------------------------------------- -Let's deploy ``: +Let's deploy ``: ```bash -avalanche blockchain deploy --local +avalanche blockchain deploy --local -Deploying [] to Local Network +Deploying [] to Local Network Backend controller started, pid: 149427, output at: ~/.avalanche-cli/runs/server_20240229_165923/avalanche-cli-backend.log Booting Network. Wait until healthy... @@ -72,8 +72,8 @@ Deploying Blockchain. Wait until network acknowledges... Teleporter Messenger successfully deployed to c-chain (0x253b2784c75e510dD0fF1da844684a1aC0aa5fcf) Teleporter Registry successfully deployed to c-chain (0x17aB05351fC94a1a67Bf3f56DdbB941aE6c63E25) -Teleporter Messenger successfully deployed to (0x253b2784c75e510dD0fF1da844684a1aC0aa5fcf) -Teleporter Registry successfully deployed to (0x9EDc4cB4E781413b1b82CC3A92a60131FC111F58) +Teleporter Messenger successfully deployed to (0x253b2784c75e510dD0fF1da844684a1aC0aa5fcf) +Teleporter Registry successfully deployed to (0x9EDc4cB4E781413b1b82CC3A92a60131FC111F58) Using latest awm-relayer version (v1.1.0) Executing AWM-Relayer... @@ -82,21 +82,21 @@ Blockchain ready to use. Local network node endpoints: +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ | NODE | VM | URL | ALIAS URL | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ -| node1 | | http://127.0.0.1:9650/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9650/ext/bc//rpc | +| node1 | | http://127.0.0.1:9650/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9650/ext/bc//rpc | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ -| node2 | | http://127.0.0.1:9652/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9652/ext/bc//rpc | +| node2 | | http://127.0.0.1:9652/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9652/ext/bc//rpc | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ -| node3 | | http://127.0.0.1:9654/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9654/ext/bc//rpc | +| node3 | | http://127.0.0.1:9654/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9654/ext/bc//rpc | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ -| node4 | | http://127.0.0.1:9656/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9656/ext/bc//rpc | +| node4 | | http://127.0.0.1:9656/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9656/ext/bc//rpc | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ -| node5 | | http://127.0.0.1:9658/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9658/ext/bc//rpc | +| node5 | | http://127.0.0.1:9658/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9658/ext/bc//rpc | +-------+-----------+------------------------------------------------------------------------------------+--------------------------------------------+ Browser Extension connection details (any node URL from above works): RPC URL: http://127.0.0.1:9650/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc Funded address: 0x0EF8151A3e6ad1d4e17C8ED4128b20EB5edc58B1 with 1000000 (10^18) - private key: 16289399c9466912ffffffdc093c9b51124f0dc54ac7a766b2bc5ccf558d8eee -Network name: +Network name: Chain ID: 1 Currency Symbol: TOKEN1 ``` @@ -109,19 +109,19 @@ Notice some details here: CLI configures the Relayer to enable every Subnet to send messages to all other Subnets. If you add more Subnets, the Relayer will be automatically reconfigured. -When deploying Subnet ``, the two Teleporter contracts will not be deployed to C-Chain in Local Network as they have already been deployed when we deployed the first Subnet. +When deploying Subnet ``, the two Teleporter contracts will not be deployed to C-Chain in Local Network as they have already been deployed when we deployed the first Subnet. ```bash -avalanche blockchain deploy --local +avalanche blockchain deploy --local -Deploying [] to Local Network +Deploying [] to Local Network Deploying Blockchain. Wait until network acknowledges... Teleporter Messenger has already been deployed to c-chain -Teleporter Messenger successfully deployed to (0x253b2784c75e510dD0fF1da844684a1aC0aa5fcf) -Teleporter Registry successfully deployed to (0x9EDc4cB4E781413b1b82CC3A92a60131FC111F58) +Teleporter Messenger successfully deployed to (0x253b2784c75e510dD0fF1da844684a1aC0aa5fcf) +Teleporter Registry successfully deployed to (0x9EDc4cB4E781413b1b82CC3A92a60131FC111F58) Using latest awm-relayer version (v1.1.0) Executing AWM-Relayer... @@ -130,31 +130,31 @@ Blockchain ready to use. Local network node endpoints: +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ | NODE | VM | URL | ALIAS URL | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node1 | | http://127.0.0.1:9650/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9650/ext/bc//rpc | +| node1 | | http://127.0.0.1:9650/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9650/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node1 | | http://127.0.0.1:9650/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9650/ext/bc//rpc | +| node1 | | http://127.0.0.1:9650/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9650/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node2 | | http://127.0.0.1:9652/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9652/ext/bc//rpc | +| node2 | | http://127.0.0.1:9652/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9652/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node2 | | http://127.0.0.1:9652/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9652/ext/bc//rpc | +| node2 | | http://127.0.0.1:9652/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9652/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node3 | | http://127.0.0.1:9654/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9654/ext/bc//rpc | +| node3 | | http://127.0.0.1:9654/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9654/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node3 | | http://127.0.0.1:9654/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9654/ext/bc//rpc | +| node3 | | http://127.0.0.1:9654/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9654/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node4 | | http://127.0.0.1:9656/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9656/ext/bc//rpc | +| node4 | | http://127.0.0.1:9656/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9656/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node4 | | http://127.0.0.1:9656/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9656/ext/bc//rpc | +| node4 | | http://127.0.0.1:9656/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9656/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node5 | | http://127.0.0.1:9658/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9658/ext/bc//rpc | +| node5 | | http://127.0.0.1:9658/ext/bc/MzN4AbtFzQ3eKqPhFaDpwCMJmagciWSCgghkZx6YeC6jRdvb6/rpc | http://127.0.0.1:9658/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ -| node5 | | http://127.0.0.1:9658/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9658/ext/bc//rpc | +| node5 | | http://127.0.0.1:9658/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc | http://127.0.0.1:9658/ext/bc//rpc | +-------+-----------+-------------------------------------------------------------------------------------+--------------------------------------------+ Browser Extension connection details (any node URL from above works): RPC URL: http://127.0.0.1:9650/ext/bc/2tVGwEQmeXtdnFURW1YSq5Yf4jbJPfTBfVcu68KWHdHe5e5gX5/rpc Funded address: 0x0EF815FFFF6ad1d4e17C8ED4128b20EB5edAABBB with 1000000 (10^18) - private key: 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027 -Network name: +Network name: Chain ID: 2 Currency Symbol: TOKEN2 ``` @@ -197,10 +197,10 @@ By executing `subnet describe` on a Teleporter enabled Subnet, the following rel - Teleporter Messenger address - Teleporter Registry address -Let's get the information for ``: +Let's get the information for ``: ```bash -avalanche blockchain describe +avalanche blockchain describe _____ _ _ _ | __ \ | | (_) | From 273820edfdc499f4de6788a21da6a47125e994bf Mon Sep 17 00:00:00 2001 From: owenwahlgren Date: Fri, 23 Aug 2024 16:58:29 -0400 Subject: [PATCH 05/10] replace: more commands --- .../teleporter/teleporter-on-devnet.mdx | 2 +- .../teleporter-on-local-network.mdx | 2 +- .../docs/subnets/avalanche-cli-subnets.mdx | 44 +++++++++---------- .../subnets/deploy-a-subnet/fuji-testnet.mdx | 2 +- .../subnets/deploy-a-subnet/local-network.mdx | 8 ++-- .../make-subnet-permissionless.mdx | 10 ++--- .../docs/subnets/maintain/delete-subnet.mdx | 2 +- content/docs/subnets/troubleshooting.mdx | 2 +- .../upgrade/subnet-virtual-machine.mdx | 4 +- content/docs/tooling/avalanche-cli.mdx | 44 +++++++++---------- .../deploy-custom-vm.mdx | 10 ++--- .../create-avalanche-nodes/run-loadtest.mdx | 2 +- .../create-avalanche-nodes/setup-devnet.mdx | 28 ++++++------ .../validate-subnet.mdx | 10 ++--- .../create-deploy-subnets/deploy-locally.mdx | 8 ++-- .../deploy-on-fuji-testnet.mdx | 2 +- .../create-deploy-subnets/view-subnets.mdx | 4 +- .../tooling/cross-chain/teleporter-devnet.mdx | 2 +- .../cross-chain/teleporter-local-network.mdx | 2 +- 19 files changed, 94 insertions(+), 94 deletions(-) diff --git a/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx b/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx index 887a0b3f2b2..3b4fc5e6b27 100644 --- a/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx +++ b/content/docs/cross-chain/teleporter/teleporter-on-devnet.mdx @@ -191,7 +191,7 @@ Obtaining Information on Teleporter Deploys[​](#obtaining-information-on-telep ### Obtaining Subnet Information[​](#obtaining-subnet-information "Direct link to heading") -By executing `subnet describe` on a Teleporter enabled Subnet, the following relevant information can be found: +By executing `blockchain describe` on a Teleporter enabled Subnet, the following relevant information can be found: - Blockchain RPC URL - Blockchain ID in cb58 format diff --git a/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx b/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx index 4faded9a03d..20ac42ef676 100644 --- a/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx +++ b/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx @@ -186,7 +186,7 @@ Obtaining Information on Teleporter Deploys[​](#obtaining-information-on-telep ### Obtaining Subnet Information[​](#obtaining-subnet-information "Direct link to heading") -By executing `subnet describe` on a Teleporter enabled Subnet, the following relevant information can be found: +By executing `blockchain describe` on a Teleporter enabled Subnet, the following relevant information can be found: - Blockchain RPC URL - Blockchain ID in cb58 format diff --git a/content/docs/subnets/avalanche-cli-subnets.mdx b/content/docs/subnets/avalanche-cli-subnets.mdx index 0e357d2e52f..48216648a9b 100644 --- a/content/docs/subnets/avalanche-cli-subnets.mdx +++ b/content/docs/subnets/avalanche-cli-subnets.mdx @@ -51,11 +51,11 @@ Subnet[​](#subnet "Direct link to heading") The `subnet` command suite provides a collection of tools for developing and deploying Subnets. -To get started, use the `subnet create` command wizard to walk through the configuration of your very first Subnet. Then, go ahead and deploy it with the `subnet deploy` command. You can use the rest of the commands to manage your Subnet configurations and live deployments. +To get started, use the `blockchain create` command wizard to walk through the configuration of your very first Subnet. Then, go ahead and deploy it with the `blockchain deploy` command. You can use the rest of the commands to manage your Subnet configurations and live deployments. ### Subnet AddValidator[​](#subnet-addvalidator "Direct link to heading") -The `subnet addValidator` command whitelists a primary network validator to validate the provided deployed Subnet. +The `blockchain addValidator` command whitelists a primary network validator to validate the provided deployed Subnet. To add the validator to the Subnet's allow list, you first need to provide the subnetName and the validator's unique NodeID. The command then prompts for the validation start time, duration, and stake weight. You can bypass these prompts by providing the values with flags. @@ -117,7 +117,7 @@ avalanche blockchain removeValidator [subnetName] [flags] ### Subnet Change Owner[​](#subnet-change-owner "Direct link to heading") -The `subnet changeOwner` changes the owner of the deployed Subnet. This command currently only works on Subnets deployed to Devnet, Fuji or Mainnet. +The `blockchain changeOwner` changes the owner of the deployed Subnet. This command currently only works on Subnets deployed to Devnet, Fuji or Mainnet. **Usage**: @@ -167,7 +167,7 @@ avalanche blockchain configure [subnetName] [flags] ### Subnet Create[​](#subnet-create "Direct link to heading") -The `subnet create` command builds a new genesis file to configure your Subnet. By default, the command runs an interactive wizard. It walks you through all the steps you need to create your first Subnet. +The `blockchain create` command builds a new genesis file to configure your Subnet. By default, the command runs an interactive wizard. It walks you through all the steps you need to create your first Subnet. The tool supports deploying Subnet-EVM and custom VMs. You can create a custom, user-generated genesis with a custom VM by providing the path to your genesis and VM binaries with the `--genesis` and `--vm` flags. @@ -204,7 +204,7 @@ avalanche blockchain create [subnetName] [flags] ### Subnet Delete[​](#subnet-delete "Direct link to heading") -The `subnet delete` command deletes an existing Subnet configuration. +The `blockchain delete` command deletes an existing Subnet configuration. **Usage**: @@ -220,7 +220,7 @@ avalanche blockchain delete [flags] ### Subnet Deploy[​](#subnet-deploy "Direct link to heading") -The `subnet deploy` command deploys your Subnet configuration locally, to Fuji Testnet, or to Mainnet. +The `blockchain deploy` command deploys your Subnet configuration locally, to Fuji Testnet, or to Mainnet. At the end of the call, the command prints the RPC URL you can use to interact with the Subnet. @@ -259,7 +259,7 @@ avalanche blockchain deploy [subnetName] [flags] ### Subnet Describe[​](#subnet-describe "Direct link to heading") -The `subnet describe` command prints the details of a Subnet configuration to the console. By default, the command prints a summary of the configuration. By providing the `--genesis` flag, the command instead prints out the raw genesis file. +The `blockchain describe` command prints the details of a Subnet configuration to the console. By default, the command prints a summary of the configuration. By providing the `--genesis` flag, the command instead prints out the raw genesis file. **Usage**: @@ -276,7 +276,7 @@ avalanche blockchain describe [subnetName] [flags] ### Subnet Export[​](#subnet-export "Direct link to heading") -The `subnet export` command write the details of an existing Subnet deploy to a file. The command prompts for an output path. You can also provide one with the `--output` flag. +The `blockchain export` command write the details of an existing Subnet deploy to a file. The command prompts for an output path. You can also provide one with the `--output` flag. **Usage**: @@ -293,7 +293,7 @@ avalanche blockchain export [subnetName] [flags] ### Subnet Import[​](#subnet-import "Direct link to heading") -The `subnet import` command imports configurations into Avalanche-CLI. +The `blockchain import` command imports configurations into Avalanche-CLI. This command supports importing from a file created on another computer, or importing from Subnets running public networks (for example, created manually or with the deprecated Subnet-CLI) @@ -319,7 +319,7 @@ avalanche blockchain import file [subnetPath] [flags] #### Import from a Public Network[​](#import-from-a-public-network "Direct link to heading") -The `subnet import public` command imports a Subnet configuration from a running network. +The `blockchain import public` command imports a Subnet configuration from a running network. The genesis file should be available from the disk for this to work. By default, an imported Subnet doesn't overwrite an existing Subnet with the same name. To allow overwrites, provide the `--force` flag. @@ -347,7 +347,7 @@ avalanche blockchain import public [subnetPath] [flags] ### Subnet Join[​](#subnet-join "Direct link to heading") -The `subnet join` command configures your validator node to begin validating a new Subnet. +The `blockchain join` command configures your validator node to begin validating a new Subnet. To complete this process, you must have access to the machine running your validator. If the CLI is running on the same machine as your validator, it can generate or update your node's config file automatically. Alternatively, the command can print the necessary instructions to update your node manually. To complete the validation process, the Subnet's admins must add the NodeID of your validator to the Subnet's allow list by calling `addValidator` with your NodeID. @@ -380,7 +380,7 @@ avalanche blockchain join [subnetName] [flags] ### Subnet List[​](#subnet-list "Direct link to heading") -The `subnet list` command prints the names of all created Subnet configurations. Without any flags, it prints some general, static information about the Subnet. With the `--deployed` flag, the command shows additional information including the VMID, BlockchainID and SubnetID. +The `blockchain list` command prints the names of all created Subnet configurations. Without any flags, it prints some general, static information about the Subnet. With the `--deployed` flag, the command shows additional information including the VMID, BlockchainID and SubnetID. **Usage**: @@ -397,7 +397,7 @@ avalanche blockchain list [flags] ### Subnet Publish[​](#subnet-publish "Direct link to heading") -The `subnet publish` command publishes the Subnet's VM to a repository. +The `blockchain publish` command publishes the Subnet's VM to a repository. **Usage**: @@ -419,7 +419,7 @@ avalanche blockchain publish [subnetName] [flags] ### Subnet Stats[​](#subnet-stats "Direct link to heading") -The `subnet stats` command prints validator statistics for the given Subnet. +The `blockchain stats` command prints validator statistics for the given Subnet. **Usage**: @@ -438,7 +438,7 @@ avalanche blockchain stats [subnetName] [flags] ### Subnet VMID[​](#subnet-vmid "Direct link to heading") -The `subnet vmid` command prints the virtual machine ID (VMID) for the given Subnet. +The `blockchain vmid` command prints the virtual machine ID (VMID) for the given Subnet. **Usage**: @@ -537,7 +537,7 @@ avalanche blockchain addPermissionlessDelegator [subnetName] [flags] Subnet Upgrade[​](#subnet-upgrade "Direct link to heading") ----------------------------------------------------------- -The `subnet upgrade` command suite provides a collection of tools for updating your developmental and deployed Subnets. +The `blockchain upgrade` command suite provides a collection of tools for updating your developmental and deployed Subnets. ### Subnet Upgrade Apply[​](#subnet-upgrade-apply "Direct link to heading") @@ -587,7 +587,7 @@ avalanche blockchain upgrade export [subnetName] [flags] ### Subnet Upgrade Generate[​](#subnet-upgrade-generate "Direct link to heading") -The `subnet upgrade generate` command builds a new upgrade.json file to customize your Subnet. It guides the user through the process using an interactive wizard. +The `blockchain upgrade generate` command builds a new upgrade.json file to customize your Subnet. It guides the user through the process using an interactive wizard. **Usage**: @@ -636,7 +636,7 @@ avalanche blockchain upgrade print [subnetName] [flags] ### Subnet Upgrade VM[​](#subnet-upgrade-vm "Direct link to heading") -The `subnet upgrade vm` command enables the user to upgrade their Subnet's VM binary. The command can upgrade both local Subnets and publicly deployed Subnets on Fuji and Mainnet. +The `blockchain upgrade vm` command enables the user to upgrade their Subnet's VM binary. The command can upgrade both local Subnets and publicly deployed Subnets on Fuji and Mainnet. The command walks the user through an interactive wizard. The user can skip the wizard by providing command line flags. @@ -874,7 +874,7 @@ avalanche node stop [clusterName] [flags] (ALPHA Warning) This command is currently in experimental mode. -The `node sync` command enables all nodes in a cluster to be bootstrapped to a Subnet. You can check the Subnet bootstrap status by calling avalanche `node status --subnet ` +The `node sync` command enables all nodes in a cluster to be bootstrapped to a Subnet. You can check the Subnet bootstrap status by calling avalanche `node status --subnet ` **Usage**: @@ -902,7 +902,7 @@ The `node update` command suite provides a collection of commands for nodes to u (ALPHA Warning) This command is currently in experimental mode. -The `node update subnet` command updates all nodes in a cluster with latest Subnet configuration and You can check the updated Subnet bootstrap status by calling avalanche `node status --subnet ` +The `node update subnet` command updates all nodes in a cluster with latest Subnet configuration and You can check the updated Subnet bootstrap status by calling avalanche `node status --subnet ` **Usage**: @@ -958,7 +958,7 @@ avalanche node validate primary [clusterName] [flags] (ALPHA Warning) This command is currently in experimental mode. -The `node validate subnet` command enables all nodes in a cluster to be validators of a Subnet. If the command is run before the nodes are Primary Network validators, the command will first make the nodes Primary Network validators before making them Subnet validators. If The command is run before the nodes are bootstrapped on the Primary Network, the command will fail. You can check the bootstrap status by calling `avalanche node status `. If The command is run before the nodes are synced to the Subnet, the command will fail. You can check the Subnet sync status by calling `avalanche node status --subnet `. +The `node validate subnet` command enables all nodes in a cluster to be validators of a Subnet. If the command is run before the nodes are Primary Network validators, the command will first make the nodes Primary Network validators before making them Subnet validators. If The command is run before the nodes are bootstrapped on the Primary Network, the command will fail. You can check the bootstrap status by calling `avalanche node status `. If The command is run before the nodes are synced to the Subnet, the command will fail. You can check the Subnet sync status by calling `avalanche node status --subnet `. **Usage**: @@ -1084,7 +1084,7 @@ Network[​](#network "Direct link to heading") The `network` command suite provides a collection of tools for managing local Subnet deployments. -When you deploy a Subnet locally, it runs on a local, multi-node Avalanche network. The `subnet deploy` command starts this network in the background. This command suite allows you to shutdown, restart, and clear that network. +When you deploy a Subnet locally, it runs on a local, multi-node Avalanche network. The `blockchain deploy` command starts this network in the background. This command suite allows you to shutdown, restart, and clear that network. This network currently supports multiple, concurrently deployed Subnets. diff --git a/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx b/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx index c9be159dc1f..b49a90466e4 100644 --- a/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx +++ b/content/docs/subnets/deploy-a-subnet/fuji-testnet.mdx @@ -178,7 +178,7 @@ Create an EVM Subnet[​](#create-an-evm-subnet "Direct link to heading") Creating a Subnet with `Avalanche-CLI` for `Fuji` works the same way as with a local network. In fact, the `create` commands only creates a specification of your Subnet on the local file system. Afterwards the Subnet needs to be _deployed_. This allows to reuse configs, by creating the config with the `create` command, then first deploying to a local network and successively to `Fuji` - and eventually to `Mainnet`. -To create an EVM Subnet, run the `subnet create` command with a name of your choice: +To create an EVM Subnet, run the `blockchain create` command with a name of your choice: ```bash avalanche blockchain create testsubnet diff --git a/content/docs/subnets/deploy-a-subnet/local-network.mdx b/content/docs/subnets/deploy-a-subnet/local-network.mdx index 258a69885d2..88733d2cb3c 100644 --- a/content/docs/subnets/deploy-a-subnet/local-network.mdx +++ b/content/docs/subnets/deploy-a-subnet/local-network.mdx @@ -10,18 +10,18 @@ description: This guide focuses on taking an already created Subnet configuratio ## Deploying Subnets Locally -In the following commands, make sure to substitute the name of your Subnet configuration for ``. +In the following commands, make sure to substitute the name of your Subnet configuration for ``. To deploy your Subnet, run ```bash -avalanche blockchain deploy +avalanche blockchain deploy ``` and, select `Local Network` to deploy on. Alternatively, you can bypass this prompt by providing the `--local` flag. For example: ```bash -avalanche blockchain deploy --local +avalanche blockchain deploy --local ``` The command may take a couple minutes to run. @@ -86,5 +86,5 @@ To redeploy the Subnet, you first need to wipe the Subnet state. This permanentl You are now free to redeploy your Subnet with: ```bash -avalanche blockchain deploy --local +avalanche blockchain deploy --local ``` diff --git a/content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx b/content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx index 75c9ffd7aea..8117d476098 100644 --- a/content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx +++ b/content/docs/subnets/elastic-subnets/make-subnet-permissionless.mdx @@ -15,12 +15,12 @@ This how-to guide focuses on taking an already created permissioned Subnet and t Getting Started[​](#getting-started "Direct link to heading") ------------------------------------------------------------- -In the following commands, make sure to substitute the name of your Subnet configuration for ``. +In the following commands, make sure to substitute the name of your Subnet configuration for ``. To transform your permissioned Subnet into an Elastic Subnet (NOTE: this action is irreversible), run: ```bash -avalanche subnet elastic +avalanche subnet elastic ``` and, select the network that you want to transform the Subnet on. Alternatively, you can bypass this prompt by providing the `--local`, `--fuji`, or `--mainnet` flag. @@ -50,12 +50,12 @@ You can use the output details such as the Asset ID and Elastic Subnet ID to con Adding Permissionless Validators to Elastic Subnet[​](#adding-permissionless-validators-to-elastic-subnet "Direct link to heading") ----------------------------------------------------------------------------------------------------------------------------------- -If you are running this command on local network, you will need to first remove permissioned validators (by running `avalanche subnet removeValidator `) so that you can have a list of local nodes to choose from to be added as a permissionless validator in the Elastic Subnet. +If you are running this command on local network, you will need to first remove permissioned validators (by running `avalanche subnet removeValidator `) so that you can have a list of local nodes to choose from to be added as a permissionless validator in the Elastic Subnet. To add permissionless validators to an Elastic Subnet, run: ```bash -avalanche subnet join --elastic +avalanche subnet join --elastic ``` You will be prompted with which node you would like to add as a permissionless validator. You can skip this prompt by using `--nodeID` flag. @@ -70,7 +70,7 @@ Adding Permissionless Delegator to a Permissionless Validator in Elastic Subnet[ To add permissionless delegators, run: ```bash -avalanche subnet addPermissionlessDelegator +avalanche subnet addPermissionlessDelegator ``` You will be prompted with which Subnet validator you would like to delegate to. You can skip this prompt by using `--nodeID` flag. diff --git a/content/docs/subnets/maintain/delete-subnet.mdx b/content/docs/subnets/maintain/delete-subnet.mdx index 016114382c1..39a01841564 100644 --- a/content/docs/subnets/maintain/delete-subnet.mdx +++ b/content/docs/subnets/maintain/delete-subnet.mdx @@ -9,7 +9,7 @@ Deleting a Subnet Configuration[​](#deleting-a-subnet-configuration "Direct li To delete a created Subnet configuration, run: ```bash -avalanche blockchain delete +avalanche blockchain delete ``` Deleting a Deployed Subnet[​](#deleting-a-deployed-subnet "Direct link to heading") diff --git a/content/docs/subnets/troubleshooting.mdx b/content/docs/subnets/troubleshooting.mdx index a2217b86630..c111b863866 100644 --- a/content/docs/subnets/troubleshooting.mdx +++ b/content/docs/subnets/troubleshooting.mdx @@ -82,7 +82,7 @@ This error occurs when the RPCChainVM protocol version used by VMs like Subnet-E If your VM has an RPC version mismatch, you have two options: 1. Update the version of AvalancheGo you use in your VM. This is the correct long-term approach. -2. Use Avalanche-CLI to deploy an older version of AvalancheGo by using the `--avalanchego-version` flag. Both the [`subnet deploy`](/tooling/avalanche-cli#subnet-deploy) and [`network start`](/tooling/avalanche-cli#network-start) commands support setting the AvalancheGo version explicitly. +2. Use Avalanche-CLI to deploy an older version of AvalancheGo by using the `--avalanchego-version` flag. Both the [`blockchain deploy`](/tooling/avalanche-cli#subnet-deploy) and [`network start`](/tooling/avalanche-cli#network-start) commands support setting the AvalancheGo version explicitly. Although it's very important to keep your version of AvalancheGo up-to-date, this workaround helps you avoid broken builds in the short term. diff --git a/content/docs/subnets/upgrade/subnet-virtual-machine.mdx b/content/docs/subnets/upgrade/subnet-virtual-machine.mdx index 1c0742d578c..58f1066cb0d 100644 --- a/content/docs/subnets/upgrade/subnet-virtual-machine.mdx +++ b/content/docs/subnets/upgrade/subnet-virtual-machine.mdx @@ -17,10 +17,10 @@ Next, you need to select the new VM to run your Subnet on. If you're running a S Start the upgrade wizard with: ```bash -avalanche blockchain upgrade vm +avalanche blockchain upgrade vm ``` -where you replace `` with the name of the Subnet you would like to upgrade. +where you replace `` with the name of the Subnet you would like to upgrade. ### Selecting a VM Deployment to Upgrade[​](#selecting-a-vm-deployment-to-upgrade "Direct link to heading") diff --git a/content/docs/tooling/avalanche-cli.mdx b/content/docs/tooling/avalanche-cli.mdx index 04eb16c592b..7ab8edfd155 100644 --- a/content/docs/tooling/avalanche-cli.mdx +++ b/content/docs/tooling/avalanche-cli.mdx @@ -49,11 +49,11 @@ Subnet[​](#subnet "Direct link to heading") The `subnet` command suite provides a collection of tools for developing and deploying Subnets. -To get started, use the `subnet create` command wizard to walk through the configuration of your very first Subnet. Then, go ahead and deploy it with the `subnet deploy` command. You can use the rest of the commands to manage your Subnet configurations and live deployments. +To get started, use the `blockchain create` command wizard to walk through the configuration of your very first Subnet. Then, go ahead and deploy it with the `blockchain deploy` command. You can use the rest of the commands to manage your Subnet configurations and live deployments. ### Subnet AddValidator -The `subnet addValidator` command whitelists a primary network validator to validate the provided deployed Subnet. +The `blockchain addValidator` command whitelists a primary network validator to validate the provided deployed Subnet. To add the validator to the Subnet's allow list, you first need to provide the subnetName and the validator's unique NodeID. The command then prompts for the validation start time, duration, and stake weight. You can bypass these prompts by providing the values with flags. @@ -115,7 +115,7 @@ avalanche blockchain removeValidator [subnetName] [flags] ### Subnet Change Owner -The `subnet changeOwner` changes the owner of the deployed Subnet. +The `blockchain changeOwner` changes the owner of the deployed Subnet. This command currently only works on Subnets deployed to Devnet, Fuji or Mainnet. @@ -167,7 +167,7 @@ avalanche blockchain configure [subnetName] [flags] ### Subnet Create -The `subnet create` command builds a new genesis file to configure your Subnet. By default, the command runs an interactive wizard. It walks you through all the steps you need to create your first Subnet. +The `blockchain create` command builds a new genesis file to configure your Subnet. By default, the command runs an interactive wizard. It walks you through all the steps you need to create your first Subnet. The tool supports deploying Subnet-EVM and custom VMs. You can create a custom, user-generated genesis with a custom VM by providing the path to your genesis and VM binaries with the `--genesis` and `--vm` flags. @@ -206,7 +206,7 @@ avalanche blockchain create [subnetName] [flags] ### Subnet Delete -The `subnet delete` command deletes an existing Subnet configuration. +The `blockchain delete` command deletes an existing Subnet configuration. **Usage**: @@ -222,7 +222,7 @@ avalanche blockchain delete [flags] ### Subnet Deploy -The `subnet deploy` command deploys your Subnet configuration locally, to Fuji Testnet, or to Mainnet. +The `blockchain deploy` command deploys your Subnet configuration locally, to Fuji Testnet, or to Mainnet. At the end of the call, the command prints the RPC URL you can use to interact with the Subnet. @@ -261,7 +261,7 @@ avalanche blockchain deploy [subnetName] [flags] ### Subnet Describe -The `subnet describe` command prints the details of a Subnet configuration to the console. By default, the command prints a summary of the configuration. By providing the `--genesis` flag, the command instead prints out the raw genesis file. +The `blockchain describe` command prints the details of a Subnet configuration to the console. By default, the command prints a summary of the configuration. By providing the `--genesis` flag, the command instead prints out the raw genesis file. **Usage**: @@ -278,7 +278,7 @@ avalanche blockchain describe [subnetName] [flags] ### Subnet Export -The `subnet export` command write the details of an existing Subnet deploy to a file. +The `blockchain export` command write the details of an existing Subnet deploy to a file. The command prompts for an output path. You can also provide one with the `--output` flag. @@ -297,7 +297,7 @@ avalanche blockchain export [subnetName] [flags] ### Subnet Import -The `subnet import` command imports configurations into Avalanche-CLI. +The `blockchain import` command imports configurations into Avalanche-CLI. This command supports importing from a file created on another computer, or importing from Subnets running public networks (for example, created manually or with the deprecated Subnet-CLI) @@ -323,7 +323,7 @@ avalanche blockchain import file [subnetPath] [flags] #### Import from a Public Network -The `subnet import public` command imports a Subnet configuration from a running network. +The `blockchain import public` command imports a Subnet configuration from a running network. The genesis file should be available from the disk for this to work. By default, an imported Subnet doesn't overwrite an existing Subnet with the same name. To allow overwrites, provide the `--force` flag. @@ -351,7 +351,7 @@ avalanche blockchain import public [subnetPath] [flags] ### Subnet Join -The `subnet join` command configures your validator node to begin validating a new Subnet. +The `blockchain join` command configures your validator node to begin validating a new Subnet. To complete this process, you must have access to the machine running your validator. If the CLI is running on the same machine as your validator, it can generate or update your node's config file automatically. Alternatively, the command can print the necessary instructions to update your node manually. To complete the validation process, the Subnet's admins must add the NodeID of your validator to the Subnet's allow list by calling `addValidator` with your NodeID. @@ -384,7 +384,7 @@ avalanche blockchain join [subnetName] [flags] ### Subnet List -The `subnet list` command prints the names of all created Subnet configurations. Without any flags, it prints some general, static information about the Subnet. With the `--deployed` flag, the command shows additional information including the VMID, BlockchainID and SubnetID. +The `blockchain list` command prints the names of all created Subnet configurations. Without any flags, it prints some general, static information about the Subnet. With the `--deployed` flag, the command shows additional information including the VMID, BlockchainID and SubnetID. **Usage**: @@ -401,7 +401,7 @@ avalanche blockchain list [flags] ### Subnet Publish -The `subnet publish` command publishes the Subnet's VM to a repository. +The `blockchain publish` command publishes the Subnet's VM to a repository. **Usage**: @@ -423,7 +423,7 @@ avalanche blockchain publish [subnetName] [flags] ### Subnet Stats -The `subnet stats` command prints validator statistics for the given Subnet. +The `blockchain stats` command prints validator statistics for the given Subnet. **Usage**: @@ -442,7 +442,7 @@ avalanche blockchain stats [subnetName] [flags] ### Subnet VMID -The `subnet vmid` command prints the virtual machine ID (VMID) for the given Subnet. +The `blockchain vmid` command prints the virtual machine ID (VMID) for the given Subnet. **Usage**: @@ -541,7 +541,7 @@ avalanche blockchain addPermissionlessDelegator [subnetName] [flags] Subnet Upgrade[​](#subnet-upgrade "Direct link to heading") ----------------------------------------------------------- -The `subnet upgrade` command suite provides a collection of tools for updating your developmental and deployed Subnets. +The `blockchain upgrade` command suite provides a collection of tools for updating your developmental and deployed Subnets. ### Subnet Upgrade Apply @@ -591,7 +591,7 @@ avalanche blockchain upgrade export [subnetName] [flags] ### Subnet Upgrade Generate -The `subnet upgrade generate` command builds a new upgrade.json file to customize your Subnet. It guides the user through the process using an interactive wizard. +The `blockchain upgrade generate` command builds a new upgrade.json file to customize your Subnet. It guides the user through the process using an interactive wizard. **Usage**: @@ -636,7 +636,7 @@ avalanche blockchain upgrade print [subnetName] [flags] ### Subnet Upgrade VM -The `subnet upgrade vm` command enables the user to upgrade their Subnet's VM binary. The command can upgrade both local Subnets and publicly deployed Subnets on Fuji and Mainnet. +The `blockchain upgrade vm` command enables the user to upgrade their Subnet's VM binary. The command can upgrade both local Subnets and publicly deployed Subnets on Fuji and Mainnet. The command walks the user through an interactive wizard. The user can skip the wizard by providing command line flags. @@ -864,7 +864,7 @@ avalanche node stop [clusterName] [flags] (ALPHA Warning) This command is currently in experimental mode. -The `node sync` command enables all nodes in a cluster to be bootstrapped to a Subnet. You can check the Subnet bootstrap status by calling avalanche `node status --subnet ` +The `node sync` command enables all nodes in a cluster to be bootstrapped to a Subnet. You can check the Subnet bootstrap status by calling avalanche `node status --subnet ` **Usage**: @@ -886,7 +886,7 @@ The `node update` command suite provides a collection of commands for nodes to u (ALPHA Warning) This command is currently in experimental mode. -The `node update subnet` command updates all nodes in a cluster with latest Subnet configuration and You can check the updated Subnet bootstrap status by calling avalanche `node status --subnet ` +The `node update subnet` command updates all nodes in a cluster with latest Subnet configuration and You can check the updated Subnet bootstrap status by calling avalanche `node status --subnet ` **Usage**: @@ -944,7 +944,7 @@ avalanche node validate primary [clusterName] [flags] (ALPHA Warning) This command is currently in experimental mode. -The `node validate subnet` command enables all nodes in a cluster to be validators of a Subnet. If the command is run before the nodes are Primary Network validators, the command will first make the nodes Primary Network validators before making them Subnet validators. If The command is run before the nodes are bootstrapped on the Primary Network, the command will fail. You can check the bootstrap status by calling `avalanche node status `. If The command is run before the nodes are synced to the Subnet, the command will fail. You can check the Subnet sync status by calling `avalanche node status --subnet `. +The `node validate subnet` command enables all nodes in a cluster to be validators of a Subnet. If the command is run before the nodes are Primary Network validators, the command will first make the nodes Primary Network validators before making them Subnet validators. If The command is run before the nodes are bootstrapped on the Primary Network, the command will fail. You can check the bootstrap status by calling `avalanche node status `. If The command is run before the nodes are synced to the Subnet, the command will fail. You can check the Subnet sync status by calling `avalanche node status --subnet `. **Usage**: @@ -1075,7 +1075,7 @@ Network[​](#network "Direct link to heading") The `network` command suite provides a collection of tools for managing local Subnet deployments. -When you deploy a Subnet locally, it runs on a local, multi-node Avalanche network. The `subnet deploy` command starts this network in the background. This command suite allows you to shutdown, restart, and clear that network. +When you deploy a Subnet locally, it runs on a local, multi-node Avalanche network. The `blockchain deploy` command starts this network in the background. This command suite allows you to shutdown, restart, and clear that network. This network currently supports multiple, concurrently deployed Subnets. diff --git a/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx b/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx index d2be564a3b3..07201714fd7 100644 --- a/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx +++ b/content/docs/tooling/create-avalanche-nodes/deploy-custom-vm.mdx @@ -85,10 +85,10 @@ Save it into a file with path `` (for example `~/morpheusvm_genesis Create the Subnet[​](#create-the-subnet "Direct link to heading") ----------------------------------------------------------------- -Let's create a Subnet called ``, with custom VM binary and genesis. +Let's create a Subnet called ``, with custom VM binary and genesis. ```bash -avalanche blockchain create +avalanche blockchain create ``` Choose custom @@ -131,7 +131,7 @@ Successfully created subnet configuration For this example, we will deploy the Subnet and blockchain on Fuji. Run: ```bash -avalanche blockchain deploy +avalanche blockchain deploy ``` Choose Fuji: @@ -404,7 +404,7 @@ Deploy Our Custom VM[​](#deploy-our-custom-vm "Direct link to heading") To deploy our Custom VM, run: ```bash -avalanche node sync +avalanche node sync ``` ```bash @@ -413,4 +413,4 @@ Node(s) successfully started syncing with Subnet! Your custom VM is successfully deployed! -You can also use `avalanche node update subnet ` to reinstall the binary when the branch is updated, or update the config files. \ No newline at end of file +You can also use `avalanche node update subnet ` to reinstall the binary when the branch is updated, or update the config files. \ No newline at end of file diff --git a/content/docs/tooling/create-avalanche-nodes/run-loadtest.mdx b/content/docs/tooling/create-avalanche-nodes/run-loadtest.mdx index 1ab073104d5..a3cef1edcb7 100644 --- a/content/docs/tooling/create-avalanche-nodes/run-loadtest.mdx +++ b/content/docs/tooling/create-avalanche-nodes/run-loadtest.mdx @@ -25,7 +25,7 @@ choice. To start load test, run: ```bash -avalanche node loadtest start +avalanche node loadtest start ``` Next, you will need to provide the load test Git repository URL, load test Git Branch, the command diff --git a/content/docs/tooling/create-avalanche-nodes/setup-devnet.mdx b/content/docs/tooling/create-avalanche-nodes/setup-devnet.mdx index d67c6c3d157..1888b8b8964 100644 --- a/content/docs/tooling/create-avalanche-nodes/setup-devnet.mdx +++ b/content/docs/tooling/create-avalanche-nodes/setup-devnet.mdx @@ -40,11 +40,11 @@ Let's go through several examples with the full command (with flags) provided. For example, to spin up a Devnet with 5 validator nodes and 1 API node in 5 regions each (us-west-2,us-east-1,ap-south-1,ap-northeast-1,eu-west-1) in AWS with each node having spec of -c7g.8xlarge AWS EC2 instance type and io2 volume type, with Subnet `` deployed +c7g.8xlarge AWS EC2 instance type and io2 volume type, with Subnet `` deployed into the Devnet, we will run : ```bash -avalanche node devnet wiz --authorize-access +avalanche node devnet wiz --authorize-access --aws --num-apis 1,1,1,1,1 --num-validators 5,5,5,5,5 --region us-west-2,us-east-1,ap-south-1,ap-northeast-1,eu-west-1 --default-validator-params --node-type c7g.8xlarge --aws-volume-type=io2 @@ -62,15 +62,15 @@ Setting the nodes as subnet trackers Waiting for node(s) in cluster to be healthy... Nodes healthy after 33 seconds ... -Waiting for node(s) in cluster to be syncing subnet ... -Nodes Syncing after 5 seconds +Waiting for node(s) in cluster to be syncing subnet ... +Nodes Syncing after 5 seconds Adding nodes as subnet validators ... -Waiting for node(s) in cluster to be validating subnet ... -Nodes Validating after 23 seconds +Waiting for node(s) in cluster to be validating subnet ... +Nodes Validating after 23 seconds -Devnet has been created and is validating subnet ! +Devnet has been created and is validating subnet ! ``` ### Create a Devnet and Deploy a Custom VM based Subnet into the Devnet @@ -91,10 +91,10 @@ The following settings will be used: To spin up a Devnet with 5 validator nodes and 1 API node in 5 regions each (us-west-2,us-east-1,ap-south-1,ap-northeast-1,eu-west-1) in AWS with each node having spec of c7g.8xlarge AWS EC2 instance type and io2 volume type, with the Custom VM based Subnet -`` deployed into the Devnet, we will run : +`` deployed into the Devnet, we will run : ```bash -avalanche node devnet wiz --custom-subnet \ +avalanche node devnet wiz --custom-subnet \ --subnet-genesis --custom-vm-repo-url \ --custom-vm-branch --custom-vm-build-script \ --chain-config --subnet-config \ @@ -117,13 +117,13 @@ Setting the nodes as subnet trackers Waiting for node(s) in cluster to be healthy... Nodes healthy after 33 seconds ... -Waiting for node(s) in cluster to be syncing subnet ... -Nodes Syncing after 5 seconds +Waiting for node(s) in cluster to be syncing subnet ... +Nodes Syncing after 5 seconds Adding nodes as subnet validators ... -Waiting for node(s) in cluster to be validating subnet ... -Nodes Validating after 23 seconds +Waiting for node(s) in cluster to be validating subnet ... +Nodes Validating after 23 seconds -Devnet has been created and is validating subnet ! +Devnet has been created and is validating subnet ! ``` \ No newline at end of file diff --git a/content/docs/tooling/create-avalanche-nodes/validate-subnet.mdx b/content/docs/tooling/create-avalanche-nodes/validate-subnet.mdx index 6f2a732bb8b..3321c603e7a 100644 --- a/content/docs/tooling/create-avalanche-nodes/validate-subnet.mdx +++ b/content/docs/tooling/create-avalanche-nodes/validate-subnet.mdx @@ -26,14 +26,14 @@ Before the nodes can be Subnet Validators, the nodes need to first sync with the To have all nodes in cluster `clusterName` sync with Subnet `subnetName`, run: ```bash -avalanche node sync +avalanche node sync ``` All the nodes in cluster `clusterName` will now be syncing to Subnet `subnetName`. Wait until nodes are successfully `Syncing` with the Subnet before running the next commands. -To check sync status, run `avalanche node status --subnet `. Once the node is finished syncing, the response will be: +To check sync status, run `avalanche node status --subnet `. Once the node is finished syncing, the response will be: ```bash All nodes in cluster `clusterName` are synced to Subnet `subnetName` @@ -47,7 +47,7 @@ Once the nodes have synced, we can now have the nodes be Subnet Validators. To have the nodes be Subnet Validators, run: ```bash -avalanche node validate subnet +avalanche node validate subnet ``` **For Fuji Only**: If any of the nodes is not yet a Primary Network Validator, we will first add it as a Primary Network Validator. @@ -78,7 +78,7 @@ Next, choose how long the node will be validating for: Once all the inputs are completed you will see a transaction ID indicating that the node is now a Primary Network Validator. -Note: if you see an error indicating that the transaction is not committed, run `avalanche node validate subnet ` again as it could be due to the validator start time having elapsed. +Note: if you see an error indicating that the transaction is not committed, run `avalanche node validate subnet ` again as it could be due to the validator start time having elapsed. We will then proceed with adding the node as a Subnet Validator. Similar to adding the node as a Primary Network Validator, the wizard will ask you for how you would like to pay for the transaction fee. @@ -94,7 +94,7 @@ Note that for this part, you are not staking actual AVAX in the validator. This Once all input is completed, you will another transaction ID indicating that the node is now scheduled to be a Subnet Validator. -Once the start time that you chose for the node to be a Subnet Validator has elapsed, verify that the node is a Subnet validator by running `avalanche node status --subnet `. +Once the start time that you chose for the node to be a Subnet Validator has elapsed, verify that the node is a Subnet validator by running `avalanche node status --subnet `. You should see: diff --git a/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx b/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx index 8cd88822472..1e6f37d0ff4 100644 --- a/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx +++ b/content/docs/tooling/create-deploy-subnets/deploy-locally.mdx @@ -13,18 +13,18 @@ This how-to guide focuses on taking an already created Subnet configuration and Deploying Subnets Locally[​](#deploying-subnets-locally "Direct link to heading") --------------------------------------------------------------------------------- -In the following commands, make sure to substitute the name of your Subnet configuration for ``. +In the following commands, make sure to substitute the name of your Subnet configuration for ``. To deploy your Subnet, run: ```bash -avalanche blockchain deploy +avalanche blockchain deploy ``` and select `Local Network` to deploy on. Alternatively, you can bypass this prompt by providing the `--local` flag. For example: ```bash -avalanche blockchain deploy --local +avalanche blockchain deploy --local ``` The command may take a couple minutes to run. @@ -88,5 +88,5 @@ To redeploy the Subnet, you first need to wipe the Subnet state. This permanentl You are now free to redeploy your Subnet with ```bash -avalanche blockchain deploy --local +avalanche blockchain deploy --local ``` diff --git a/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx b/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx index 4603681fcf1..197ba401ff4 100644 --- a/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx +++ b/content/docs/tooling/create-deploy-subnets/deploy-on-fuji-testnet.mdx @@ -178,7 +178,7 @@ Create an EVM Subnet[​](#create-an-evm-subnet "Direct link to heading") Creating a Subnet with `Avalanche-CLI` for `Fuji` works the same way as with a local network. In fact, the `create` commands only creates a specification of your Subnet on the local file system. Afterwards the Subnet needs to be _deployed_. This allows to reuse configs, by creating the config with the `create` command, then first deploying to a local network and successively to `Fuji` - and eventually to `Mainnet`. -To create an EVM Subnet, run the `subnet create` command with a name of your choice: +To create an EVM Subnet, run the `blockchain create` command with a name of your choice: ```bash avalanche blockchain create testsubnet diff --git a/content/docs/tooling/create-deploy-subnets/view-subnets.mdx b/content/docs/tooling/create-deploy-subnets/view-subnets.mdx index f787ae5e0e1..b402c49b4fd 100644 --- a/content/docs/tooling/create-deploy-subnets/view-subnets.mdx +++ b/content/docs/tooling/create-deploy-subnets/view-subnets.mdx @@ -34,7 +34,7 @@ To see detailed information about your deployed Subnets, add the `--deployed` fl ## Describe Subnet Configurations -To see the details of a specific configuration, run: `avalanche blockchain describe ` +To see the details of a specific configuration, run: `avalanche blockchain describe ` Example: @@ -123,7 +123,7 @@ No precompiles set ## Viewing a Genesis File -If you'd like to see the raw genesis file, supply the `--genesis` flag to the describe command: `avalanche blockchain describe --genesis` +If you'd like to see the raw genesis file, supply the `--genesis` flag to the describe command: `avalanche blockchain describe --genesis` Example: diff --git a/content/docs/tooling/cross-chain/teleporter-devnet.mdx b/content/docs/tooling/cross-chain/teleporter-devnet.mdx index d072893219c..95a25ff9778 100644 --- a/content/docs/tooling/cross-chain/teleporter-devnet.mdx +++ b/content/docs/tooling/cross-chain/teleporter-devnet.mdx @@ -191,7 +191,7 @@ Obtaining Information on Teleporter Deploys[​](#obtaining-information-on-telep ### Obtaining Subnet Information[​](#obtaining-subnet-information "Direct link to heading") -By executing `subnet describe` on a Teleporter enabled Subnet, the following relevant information can be found: +By executing `blockchain describe` on a Teleporter enabled Subnet, the following relevant information can be found: - Blockchain RPC URL - Blockchain ID in cb58 format diff --git a/content/docs/tooling/cross-chain/teleporter-local-network.mdx b/content/docs/tooling/cross-chain/teleporter-local-network.mdx index 22bcb0ae678..3da999f0077 100644 --- a/content/docs/tooling/cross-chain/teleporter-local-network.mdx +++ b/content/docs/tooling/cross-chain/teleporter-local-network.mdx @@ -189,7 +189,7 @@ Obtaining Information on Teleporter Deploys[​](#obtaining-information-on-telep ### Obtaining Subnet Information[​](#obtaining-subnet-information "Direct link to heading") -By executing `subnet describe` on a Teleporter enabled Subnet, the following relevant information can be found: +By executing `blockchain describe` on a Teleporter enabled Subnet, the following relevant information can be found: - Blockchain RPC URL - Blockchain ID in cb58 format From e02b110897d4e59c0dc3218edf94908a505fcfb9 Mon Sep 17 00:00:00 2001 From: owenwahlgren Date: Fri, 23 Aug 2024 17:02:00 -0400 Subject: [PATCH 06/10] replace: -> --- .../cross-chain/teleporter/teleporter-on-local-network.mdx | 4 ++-- content/docs/tooling/cross-chain/teleporter-local-network.mdx | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx b/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx index 20ac42ef676..deabb8ac00d 100644 --- a/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx +++ b/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx @@ -21,7 +21,7 @@ Let's create a Subnet called `` with the latest Subnet-EVM version, a ch avalanche blockchain create --evm --latest\ --evm-chain-id 1 --evm-token TOKEN1 --evm-defaults -creating genesis for +creating genesis for configuring airdrop to stored key "subnet__airdrop" with address 0x0EF8151A3e6ad1d4e17C8ED4128b20EB5edc58B1 loading stored key "cli-teleporter-deployer" for teleporter deploys (evm address, genesis balance) = (0xE932784f56774879e03F3624fbeC6261154ec711, 600000000000000000000) @@ -41,7 +41,7 @@ Now let's create a second Subnet called ``, with similar settings: avalanche blockchain create --evm --latest\ --evm-chain-id 2 --evm-token TOKEN2 --evm-defaults -creating genesis for +creating genesis for configuring airdrop to stored key "subnet__airdrop" with address 0x0EF815FFFF6ad1d4e17C8ED4128b20EB5edAABBB loading stored key "cli-teleporter-deployer" for teleporter deploys (evm address, genesis balance) = (0xE932784f56774879e03F3624fbeC6261154ec711, 600000000000000000000) diff --git a/content/docs/tooling/cross-chain/teleporter-local-network.mdx b/content/docs/tooling/cross-chain/teleporter-local-network.mdx index 3da999f0077..ed5e5a8ae88 100644 --- a/content/docs/tooling/cross-chain/teleporter-local-network.mdx +++ b/content/docs/tooling/cross-chain/teleporter-local-network.mdx @@ -24,7 +24,7 @@ Let's create a Subnet called `` with the latest Subnet-EVM version, a ch avalanche blockchain create --evm --latest\ --evm-chain-id 1 --evm-token TOKEN1 --evm-defaults -creating genesis for +creating genesis for configuring airdrop to stored key "subnet__airdrop" with address 0x0EF8151A3e6ad1d4e17C8ED4128b20EB5edc58B1 loading stored key "cli-teleporter-deployer" for teleporter deploys (evm address, genesis balance) = (0xE932784f56774879e03F3624fbeC6261154ec711, 600000000000000000000) @@ -44,7 +44,7 @@ Now let's create a second Subnet called ``, with similar settings: avalanche blockchain create --evm --latest\ --evm-chain-id 2 --evm-token TOKEN2 --evm-defaults -creating genesis for +creating genesis for configuring airdrop to stored key "subnet__airdrop" with address 0x0EF815FFFF6ad1d4e17C8ED4128b20EB5edAABBB loading stored key "cli-teleporter-deployer" for teleporter deploys (evm address, genesis balance) = (0xE932784f56774879e03F3624fbeC6261154ec711, 600000000000000000000) From 141d1c22171043165d5358d5765add8da21a003f Mon Sep 17 00:00:00 2001 From: owenwahlgren Date: Fri, 23 Aug 2024 17:07:52 -0400 Subject: [PATCH 07/10] replace: firstsubnet -> firstblockchain --- content/docs/subnets/maintain/view-subnets.mdx | 6 +++--- content/docs/tooling/create-deploy-subnets/view-subnets.mdx | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/docs/subnets/maintain/view-subnets.mdx b/content/docs/subnets/maintain/view-subnets.mdx index f42bcb2fade..63890c4e5ca 100644 --- a/content/docs/subnets/maintain/view-subnets.mdx +++ b/content/docs/subnets/maintain/view-subnets.mdx @@ -30,7 +30,7 @@ avalanche blockchain list --deployed ``` ```bash -avalanche blockchain describe firstsubnet +avalanche blockchain describe firstblockchain #output _____ _ _ _ @@ -42,7 +42,7 @@ avalanche blockchain describe firstsubnet +----------------------------+----------------------------------------------------+ | PARAMETER | VALUE | +----------------------------+----------------------------------------------------+ -| Subnet Name | firstsubnet | +| Subnet Name | firstblockchain | +----------------------------+----------------------------------------------------+ | ChainID | 12345 | +----------------------------+----------------------------------------------------+ @@ -117,7 +117,7 @@ No precompiles set If you'd like to see the raw genesis file, supply the `--genesis` flag to the describe command: ```bash -avalanche blockchain describe firstsubnet --genesis +avalanche blockchain describe firstblockchain --genesis # output { diff --git a/content/docs/tooling/create-deploy-subnets/view-subnets.mdx b/content/docs/tooling/create-deploy-subnets/view-subnets.mdx index b402c49b4fd..275bfc12db1 100644 --- a/content/docs/tooling/create-deploy-subnets/view-subnets.mdx +++ b/content/docs/tooling/create-deploy-subnets/view-subnets.mdx @@ -39,7 +39,7 @@ To see the details of a specific configuration, run: `avalanche blockchain descr Example: ```bash -> avalanche blockchain describe firstsubnet +> avalanche blockchain describe firstblockchain _____ _ _ _ | __ \ | | (_) | @@ -50,7 +50,7 @@ Example: +----------------------------+----------------------------------------------------+ | PARAMETER | VALUE | +----------------------------+----------------------------------------------------+ -| Subnet Name | firstsubnet | +| Subnet Name | firstblockchain | +----------------------------+----------------------------------------------------+ | ChainID | 12345 | +----------------------------+----------------------------------------------------+ @@ -128,7 +128,7 @@ If you'd like to see the raw genesis file, supply the `--genesis` flag to the de Example: ```bash -> avalanche blockchain describe firstsubnet --genesis +> avalanche blockchain describe firstblockchain --genesis { "config": { "chainId": 12345, From e2622efb4c37fc916f845c41a1f61ead5818d904 Mon Sep 17 00:00:00 2001 From: owenwahlgren Date: Mon, 26 Aug 2024 09:47:25 -0400 Subject: [PATCH 08/10] replace: myCustomSubnet -> myCustomBlockchain --- .../custom-virtual-machine.mdx | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx b/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx index e46f15ca48e..e32041a1043 100644 --- a/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx +++ b/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx @@ -104,10 +104,10 @@ timestamp when you create your genesis file. Create the Subnet Configuration[​](#create-the-subnet-configuration "Direct link to heading") --------------------------------------------------------------------------------------------- -Now that you have your binary, it's time to create the Subnet configuration. This tutorial uses `myCustomSubnet` as it Subnet name. Invoke the Subnet Creation Wizard with this command: +Now that you have your binary, it's time to create the Subnet configuration. This tutorial uses `myCustomBlockchain` as it Subnet name. Invoke the Subnet Creation Wizard with this command: ```bash -avalanche blockchain create myCustomSubnet +avalanche blockchain create myCustomBlockchain ``` ### Choose Your VM[​](#choose-your-vm "Direct link to heading") @@ -146,9 +146,9 @@ Now it's time to deploy it. Deploy the Subnet Locally[​](#deploy-the-subnet-locally "Direct link to heading") --------------------------------------------------------------------------------- -To deploy your Subnet, run: `avalanche blockchain deploy myCustomSubnet` +To deploy your Subnet, run: `avalanche blockchain deploy myCustomBlockchain` -Make sure to substitute the name of your Subnet if you used a different one than `myCustomSubnet`. +Make sure to substitute the name of your Subnet if you used a different one than `myCustomBlockchain`. Next, select `Local Network`: @@ -165,9 +165,9 @@ This command boots a five node Avalanche network on your machine. It needs to do If all works as expected, the command output should look something like this: ```bash -> avalanche blockchain deploy myCustomSubnet +> avalanche blockchain deploy myCustomBlockchain ✔ Local Network -Deploying [myCustomSubnet] to Local Network +Deploying [myCustomBlockchain] to Local Network Backend controller started, pid: 26110, output at: /home/fm/.avalanche-cli/runs/server_20230816_131014/avalanche-cli-backend.log Installing avalanchego-v1.10.8... avalanchego-v1.10.8 installation successful @@ -181,15 +181,15 @@ Network ready to use. Local network node endpoints: +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ | NODE | VM | URL | ALIAS URL | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ -| node1 | myCustomSubnet | http://127.0.0.1:9650/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9650/ext/bc/myCustomSubnet/rpc | +| node1 | myCustomBlockchain | http://127.0.0.1:9650/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9650/ext/bc/myCustomBlockchain/rpc | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ -| node2 | myCustomSubnet | http://127.0.0.1:9652/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9652/ext/bc/myCustomSubnet/rpc | +| node2 | myCustomBlockchain | http://127.0.0.1:9652/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9652/ext/bc/myCustomBlockchain/rpc | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ -| node3 | myCustomSubnet | http://127.0.0.1:9654/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9654/ext/bc/myCustomSubnet/rpc | +| node3 | myCustomBlockchain | http://127.0.0.1:9654/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9654/ext/bc/myCustomBlockchain/rpc | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ -| node4 | myCustomSubnet | http://127.0.0.1:9656/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9656/ext/bc/myCustomSubnet/rpc | +| node4 | myCustomBlockchain | http://127.0.0.1:9656/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9656/ext/bc/myCustomBlockchain/rpc | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ -| node5 | myCustomSubnet | http://127.0.0.1:9658/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9658/ext/bc/myCustomSubnet/rpc | +| node5 | myCustomBlockchain | http://127.0.0.1:9658/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9658/ext/bc/myCustomBlockchain/rpc | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ Browser Extension connection details (any node URL from above works): @@ -245,7 +245,7 @@ Your results may be slightly different, but you can see that in addition to the If you used the default genesis, your custom VM has a prefunded address. You can verify its balance with a curl command. Make sure to substitute the command's URL with the `RPC URL` from your deployment output. ```bash -curl --location --request POST 'http://127.0.0.1:9650/ext/bc/myCustomSubnet/rpc' \ +curl --location --request POST 'http://127.0.0.1:9650/ext/bc/myCustomBlockchain/rpc' \ --header 'Content-Type: application/json' \ --data-raw '{ "jsonrpc": "2.0", From 82e6cf2eae5c12279e43127d731db062889ea809 Mon Sep 17 00:00:00 2001 From: owenwahlgren Date: Mon, 26 Aug 2024 10:31:24 -0400 Subject: [PATCH 09/10] replace any command w/ subnet naming convention -> myblockchain --- .../custom-virtual-machine.mdx | 24 +++++++++---------- .../docs/subnets/maintain/view-subnets.mdx | 6 ++--- .../create-deploy-subnets/view-subnets.mdx | 6 ++--- 3 files changed, 18 insertions(+), 18 deletions(-) diff --git a/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx b/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx index e32041a1043..70a73bee05a 100644 --- a/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx +++ b/content/docs/subnets/deploy-a-subnet/custom-virtual-machine.mdx @@ -104,10 +104,10 @@ timestamp when you create your genesis file. Create the Subnet Configuration[​](#create-the-subnet-configuration "Direct link to heading") --------------------------------------------------------------------------------------------- -Now that you have your binary, it's time to create the Subnet configuration. This tutorial uses `myCustomBlockchain` as it Subnet name. Invoke the Subnet Creation Wizard with this command: +Now that you have your binary, it's time to create the Subnet configuration. This tutorial uses `myblockchain` as it Subnet name. Invoke the Subnet Creation Wizard with this command: ```bash -avalanche blockchain create myCustomBlockchain +avalanche blockchain create myblockchain ``` ### Choose Your VM[​](#choose-your-vm "Direct link to heading") @@ -146,9 +146,9 @@ Now it's time to deploy it. Deploy the Subnet Locally[​](#deploy-the-subnet-locally "Direct link to heading") --------------------------------------------------------------------------------- -To deploy your Subnet, run: `avalanche blockchain deploy myCustomBlockchain` +To deploy your Subnet, run: `avalanche blockchain deploy myblockchain` -Make sure to substitute the name of your Subnet if you used a different one than `myCustomBlockchain`. +Make sure to substitute the name of your Subnet if you used a different one than `myblockchain`. Next, select `Local Network`: @@ -165,9 +165,9 @@ This command boots a five node Avalanche network on your machine. It needs to do If all works as expected, the command output should look something like this: ```bash -> avalanche blockchain deploy myCustomBlockchain +> avalanche blockchain deploy myblockchain ✔ Local Network -Deploying [myCustomBlockchain] to Local Network +Deploying [myblockchain] to Local Network Backend controller started, pid: 26110, output at: /home/fm/.avalanche-cli/runs/server_20230816_131014/avalanche-cli-backend.log Installing avalanchego-v1.10.8... avalanchego-v1.10.8 installation successful @@ -181,15 +181,15 @@ Network ready to use. Local network node endpoints: +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ | NODE | VM | URL | ALIAS URL | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ -| node1 | myCustomBlockchain | http://127.0.0.1:9650/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9650/ext/bc/myCustomBlockchain/rpc | +| node1 | myblockchain | http://127.0.0.1:9650/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9650/ext/bc/myblockchain/rpc | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ -| node2 | myCustomBlockchain | http://127.0.0.1:9652/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9652/ext/bc/myCustomBlockchain/rpc | +| node2 | myblockchain | http://127.0.0.1:9652/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9652/ext/bc/myblockchain/rpc | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ -| node3 | myCustomBlockchain | http://127.0.0.1:9654/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9654/ext/bc/myCustomBlockchain/rpc | +| node3 | myblockchain | http://127.0.0.1:9654/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9654/ext/bc/myblockchain/rpc | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ -| node4 | myCustomBlockchain | http://127.0.0.1:9656/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9656/ext/bc/myCustomBlockchain/rpc | +| node4 | myblockchain | http://127.0.0.1:9656/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9656/ext/bc/myblockchain/rpc | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ -| node5 | myCustomBlockchain | http://127.0.0.1:9658/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9658/ext/bc/myCustomBlockchain/rpc | +| node5 | myblockchain | http://127.0.0.1:9658/ext/bc/z9a7L6XmFYskbaHuuLFCxThByKg4xqsYYbaqT5ke6xVutDQTp/rpc | http://127.0.0.1:9658/ext/bc/myblockchain/rpc | +-------+----------------+------------------------------------------------------------------------------------+-------------------------------------------------+ Browser Extension connection details (any node URL from above works): @@ -245,7 +245,7 @@ Your results may be slightly different, but you can see that in addition to the If you used the default genesis, your custom VM has a prefunded address. You can verify its balance with a curl command. Make sure to substitute the command's URL with the `RPC URL` from your deployment output. ```bash -curl --location --request POST 'http://127.0.0.1:9650/ext/bc/myCustomBlockchain/rpc' \ +curl --location --request POST 'http://127.0.0.1:9650/ext/bc/myblockchain/rpc' \ --header 'Content-Type: application/json' \ --data-raw '{ "jsonrpc": "2.0", diff --git a/content/docs/subnets/maintain/view-subnets.mdx b/content/docs/subnets/maintain/view-subnets.mdx index 63890c4e5ca..3a95b206f99 100644 --- a/content/docs/subnets/maintain/view-subnets.mdx +++ b/content/docs/subnets/maintain/view-subnets.mdx @@ -30,7 +30,7 @@ avalanche blockchain list --deployed ``` ```bash -avalanche blockchain describe firstblockchain +avalanche blockchain describe myblockchain #output _____ _ _ _ @@ -42,7 +42,7 @@ avalanche blockchain describe firstblockchain +----------------------------+----------------------------------------------------+ | PARAMETER | VALUE | +----------------------------+----------------------------------------------------+ -| Subnet Name | firstblockchain | +| Subnet Name | myblockchain | +----------------------------+----------------------------------------------------+ | ChainID | 12345 | +----------------------------+----------------------------------------------------+ @@ -117,7 +117,7 @@ No precompiles set If you'd like to see the raw genesis file, supply the `--genesis` flag to the describe command: ```bash -avalanche blockchain describe firstblockchain --genesis +avalanche blockchain describe myblockchain --genesis # output { diff --git a/content/docs/tooling/create-deploy-subnets/view-subnets.mdx b/content/docs/tooling/create-deploy-subnets/view-subnets.mdx index 275bfc12db1..0c2c317f8ad 100644 --- a/content/docs/tooling/create-deploy-subnets/view-subnets.mdx +++ b/content/docs/tooling/create-deploy-subnets/view-subnets.mdx @@ -39,7 +39,7 @@ To see the details of a specific configuration, run: `avalanche blockchain descr Example: ```bash -> avalanche blockchain describe firstblockchain +> avalanche blockchain describe myblockchain _____ _ _ _ | __ \ | | (_) | @@ -50,7 +50,7 @@ Example: +----------------------------+----------------------------------------------------+ | PARAMETER | VALUE | +----------------------------+----------------------------------------------------+ -| Subnet Name | firstblockchain | +| Subnet Name | myblockchain | +----------------------------+----------------------------------------------------+ | ChainID | 12345 | +----------------------------+----------------------------------------------------+ @@ -128,7 +128,7 @@ If you'd like to see the raw genesis file, supply the `--genesis` flag to the de Example: ```bash -> avalanche blockchain describe firstblockchain --genesis +> avalanche blockchain describe myblockchain --genesis { "config": { "chainId": 12345, From c9ba37525724b0b9bde5a9ff0cda70feaf65e520 Mon Sep 17 00:00:00 2001 From: Owen Date: Mon, 26 Aug 2024 11:57:46 -0400 Subject: [PATCH 10/10] fix: missing chainid config in teleporter-on-local-network.mdx Signed-off-by: Owen --- .../docs/cross-chain/teleporter/teleporter-on-local-network.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx b/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx index bd0aa70b96d..3ff5e49fb27 100644 --- a/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx +++ b/content/docs/cross-chain/teleporter/teleporter-on-local-network.mdx @@ -39,6 +39,7 @@ Now let's create a second Subnet called ``, with similar settings: ``` avalanche blockchain create --evm --latest\ + --evm-chain-id 2 --evm-token TOKEN1 --evm-defaults creating genesis for configuring airdrop to stored key "subnet__airdrop" with address 0x0EF815FFFF6ad1d4e17C8ED4128b20EB5edAABBB