Checklist for Subnet to L1 Migration

AvaCloud Portal provides a flow to guide customers through migration of their Subnet to an L1 (see technical details in ACP-77) 

Before starting the process though, there are several things to check and prepare so the process run smoothly:

• All validators of the Subnet must be active and validating this Subnet. Otherwise, migrated L1 network will start with the wrong number of validators, which may impact network stability.
• Ensure you have access to subnet control keys
• Ensure you have at least 1 AVAX per validator in the wallet that will do the migration, plus a small amount for the gas (typically below 0.01 AVAX)
• Check that Avalanche app on Ledger device (if used to store subnet control keys) is v1.2.5 and upgrade through Ledger Live if not
• Add address 0xC05A41523fd54Fd1056AA4ABeCdF59A318623A64 to Contract Deployer and Transaction AllowList precompiles if enabled on the network
• Review this document to determine the location of Validator Manager deployment 
• Make sure to switch (and fund) to internal Core wallet (not Ledger-backed) for deployment of the Validator Manager contract (transaction is too large to sign with the Ledger, you can transfer ownership to a Ledger-backed address after the migration is done)
• If your network has been turned private, AvaCloud will need to do an additional step to update the infrastructure configuration, which needs to be done before posting the actual conversation transaction, so please coordinate with AvaCloud support team on the exact timing.