Subnet to L1 Migration

Overview

With the AvalancheGo Etna release and the implementation of ACP-77, Avalanche networks are now categorized based on their creation date relative to Etna. Networks established before Etna are known as “Subnets,” while those created post-Etna are referred to as L1s.

  • Separating L1 validators from Primary Network validators (Primary Network Partial Sync, Removal of 2000 $AVAX requirement)
  • Moving ownership of L1 validator set management from P-Chain to L1s (ERC-20/ERC-721/Arbitrary Staking, Staking Reward Management)
  • Introducing a continuous P-Chain fee mechanism for L1 validators (Continuous L1 Staking)

For more details, please refer to ACP-77.

Table of Contents

  1. How do I know my network is a Subnet or L1?
  2. Checklist for Subnet to L1 migration
  3. Steps of Subnet to L1 migration with AvaCloud Portal
  4. How to add an address to precompiles?

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