AvaCloud
      Back to home
      1. AvaCloud Support
      2. AvaCloud

      AvaCloud: How do I upgrade to Mainnet?

      To upgrade from Testnet (Fuji) to Mainnet, users will share specifics on their Subnet, from end goals to any special features.  


      Before beginning, please make sure you have all of the following.

      • Control key owners defined within your organization.  These are the users on the Subnet who can make changes to the Subnet.
      • Ledgers for Control key members.  Ledgers are required to go to Mainnet as they provide the highest level of security.  Make sure members of the team guard and safely store the private keys and seed phrases off of a computer.
      • Understand your precompiles and who in the organization will control them.  You can configure this during setup, or use your own wallet address to add members after your Subnet is stood up.  Users will need to gather the C-Chain wallet address for the users in the organization that will be interacting with the precompiles that were set up during configuration.

      NOTE: This will allow the AvaStudios team to reach out and begin the process of helping transition the Subnet from Testnet (Fuji) to Mainnet


      Users can view all their Subnets from the “My Subnets” tab for an overview of all their Subnets.


      Once Approved

      Within the AvaCloud portal, users can promote their Subnet to the Mainnet once the team has reviewed the submission.

      1. Once this phase is completed, users can proceed to upgrade the Subnet.

      • Enter the Subnet Name
      •  Chain ID
      •  Native Token Symbol.

      NOTE: Make sure the Subnet name and Chain ID are unique for your Mainnet setup.  You can go to chainlist.org to make sure you are choosing a Chain ID that is not in use.



      2. Customize the Subnet with precompile by clicking on Advanced Subnet Setup. To learn more about precompiles, view the following article for more info. This article will also cover how to assign admins and enabled users to each precompile.


      3. Enter the C-Chain addresses to the allowlist to send transactions to the Subnet. Users can select roles for those addresses such as Admin and User.

      Note: One admin must be assigned to each of the precompiles to ensure you can add or remove wallet addresses from being able to interact and use these functionalities.


      4. Enter any addresses that will be receiving airdrops for native tokens.


      5. Set up Control Keys that can make changes to the Subnet. Users can choose which control keys can sign and set the threshold of how many signers are required.

      Note: Subnets will need more than 1 signer for Mainnet.  We suggest a signing threshold of 3 with 5 total potential signers for Mainnet.



      6. Finally a Summary screen will appear to review your Subnet. Once satisfied, click Submit for Review.


      Creating the Blockchain


      1. Connect the wallet admin wallet and make sure that it has a minimum of 7.5 AVAX (for a Mainnet Subnet with 5 nodes) in your spendable P-Chain balance to complete the setup. To obtain more AVAX for the testnet, please use the wallet tools.


      2. Sign for the Subnet Transaction and the Creation of the Blockchain.


      3. When selecting which signers will sign this transaction a unique link will be generated for each signer.  Share the link with people on the list of signers so they can complete the transaction.

      Note:  The user who submits this transaction will need 1 P chain AVAX to submit the transaction.  You can use the wallet tools to add more AVAX to your wallet, or to transfer AVAX from the C-Chain to the P-Chain to sign these transactions.


      4. Updates to the status of each signer will be shown.

      To learn more about how to have team members sign please view the following article.


      Adding Validators

      To finish this process, add validators to the Primary network, and then to the Subnet.


      1. First, add the validator to the P-Chain.


      2. Now add the Validator to the Subnet once all signers have finished signing.

      NOTE: When using multiple signatures, a status will be shown to provide the status of the signatures.

      3. Now the Subnet Setup is complete.



      For any additional questions, please view our other knowledge base articles or contact a support team member via the chat button. Examples are for illustrative purposes only.

      Learn More About AvaCloud | Download Case Studies | Schedule an AvaCloud Demo