Big Goals

• Update avalanchego and subnet-evm as soon as they’re released (without an avalanche-cli update)
• Load and run custom VMs (with custom genesis)
• Eventually, we can download other VMs from APM and store them appropriately
• We can load and use old versions of VMs

Commands

Create Subnet

avalanche subnet create <subnetName>

Edits

• In the subnet-evm creation flow, ask for a subnet-evm version, default to latest
• For the custom-vm flow, we need to prompt for a filepath of the custom vm binary

Flags

• -f, --force: overwrite the existing configuration if one exists
• --genesis: (RENAMED FROM --file) file path of genesis to use instead of the wizard
• --evm: use the Subnet-EVM as the base template
• --custom: use a custom VM template
• --vm: file path to custom vm binary

Technical Details

• We should query github to see what the latest release is (if github isn’t available, we can fall back to the latest installed version)
• We should remove our hardcoded subnet-evm version constants
• We are RENAMING --file to --genesis
• The vm flag should skip the custom vm prompt
• Similar to using a custom genesis, using a custom vm binary should copy the binary into one of our local directories
  • When that subnet is deleted, we should delete the custom binary

Deploy Subnet

avalanche subnet deploy <subnetName>

Edits

• In the deploy flow, ask Github for the latest avago version, download it if not already available. If github is unavailable, use the latest installed version.
• Add a flag --avalanchego-version to manually override the avago version.

Technical Details

• We should query github to see what the latest release is (if github isn’t available, we can fall back to the latest installed version)
• We should remove our hardcoded avago version constants

Tickets

• Add multi subnet-evm versions #112
• Add multi avago versions #111
• Add custom vms #113

from avalanche-cli.