Avalanche Subnets are application-specific blockchain networks created within Avalanche. Since the Etna upgrade and ACP-77, Avalanche distinguishes legacy Subnets from sovereign Avalanche Layer 1s: the newer L1 model can manage its own validator set and network rules, while older Subnets continue to follow their original design unless they are explicitly converted.
What “Subnet” Means Today
The term Avalanche Subnet refers to a network of one or more blockchains validated by a defined set of nodes. Before ACP-77, Subnet validators also had to validate Avalanche’s Primary Network. The Etna upgrade introduced a different model for new Avalanche L1s: they can use a separate validator set and specify their own membership, token economics, and operating rules.
As a result, “Subnet” and “Avalanche L1” are related but not interchangeable labels. A pre-existing Subnet does not automatically acquire the newer validator model. Its owner can convert it through the specified on-chain process; otherwise, the Subnet continues under its existing configuration. Avalanche documentation still uses “subnetID” in some technical contexts for both converted and unconverted networks.
How Avalanche L1s Work
An Avalanche L1 can run one or more blockchains and can choose its virtual machine, validator-management approach, and gas-token design. An EVM chain is one option, not a requirement. This makes the architecture suitable for an appchain that wants to set rules for a particular application or community.
Under ACP-77, L1 validators do not have to validate every chain on the Primary Network or meet its former 2,000 AVAX stake requirement for Subnet validation. They do need to track the P-Chain, which carries validator-set information and supports interoperability. The new model charges a continuous P-Chain fee rather than relying on the earlier staking arrangement; the fee is parameterized and can change, so older fixed dollar or AVAX estimates should not be treated as current quotes.
Avalanche Warp Messaging can let participating chains exchange authenticated messages. Interoperability still depends on the participating networks’ configurations and validator assumptions. It does not make every L1 equally secure or guarantee that an application can move assets between chains without additional bridge or contract risk.
Why Use a Subnet or L1?
A dedicated network can give an application more control over throughput, fees, access rules, validator selection, and upgrades than deploying only on a shared chain. It can also isolate application-specific activity from other networks. These choices may help a game, financial application, or enterprise deployment set policies that fit its needs.
The tradeoff is responsibility. A network with a small or permissioned validator set may have different censorship, availability, and collusion risks from a large public chain. An L1’s token and fee model can create additional operational dependencies, and its apps may begin with less liquidity, infrastructure, and user activity than established networks. “Sovereign” means the network sets more of its own rules; it does not mean those rules are automatically decentralized or independently secure.
Social Media Sentiment
A December 18, 2025 r/Avax year-end post highlighted Avalanche9000, custom L1 launches, and institutional use as ecosystem progress. The post was positive and had limited discussion, so it is an example of one community narrative, not evidence of broad agreement or proof that adoption, decentralization, or security concerns have been resolved.
Last updated: 2026-10
Related Terms
See Also
- Are Layer 2 Networks Actually Decentralized?
- Does Ethereum TPS Include Layer 2 Transactions?
- Real World Asset Tokenization: What It Actually Is and Why BlackRock Is Doing It
- Swap crypto with ChangeNOW
Sources
- Avalanche Builder Hub: Avalanche L1s — Describes L1 sovereignty, validator requirements, and the Primary Network relationship.
- Avalanche ACP-77: Reinventing Subnets — Specifies the transition from the earlier Subnet model and the separate L1 validator approach.
- Avalanche Builder Hub: Subnet Tools — Documents creating legacy Subnets and the explicit conversion process to an L1.
- r/Avax: Avalanche 2025 Onchain Wrapped — Provides a dated, limited example of positive community discussion around Avalanche9000 and custom L1s.