Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
…into icm_chainlink
  • Loading branch information
Andyvargtz committed Dec 13, 2024
2 parents 0df9cdf + 57f2f64 commit b83f99b
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion content/guide/subnet-vs-l1-validators.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ comments: true

The Etna Upgrade introduced L1s to the Avalanche network, providing an enhanced sovereign network design to the original Subnet model.

**L1 Validators**, introduced with ACP-77, represent a departure from this model, enabling the creation of sovereign L1 networks with minimal dependency on the Primary Network.
**L1 validators**, introduced with ACP-77, represent a departure from this model, enabling the creation of sovereign L1 networks with minimal dependency on the Primary Network.
Unlike Subnet validators, L1 validators do not stake AVAX but instead pay a dynamic monthly fee, initially set at approximately 1.3 AVAX.
They are exempt from validating the Primary Network, reducing their resource requirements and making L1 validation more accessible.
This approach fosters economic inclusivity and sovereignty, allowing developers to define custom validation logic via smart contracts and operate independent networks without staking the Primary Network.
Expand Down Expand Up @@ -45,8 +45,13 @@ L1 validators are required to:
- Sync and validate a specific L1
- Sync the latest P-Chain state

Syncing the P-Chain state is required for basic L1 functionality. It enables the L1 to track its validator weights so that it can perform consensus and validate ICM messages from other L1s, including the P-Chain.

L1 validators do not need to:
- Stake 2,000 AVAX
- Validate or participate in consensus on the Primary Network (X, P, and C-Chains)

Unless removed by the Owner Key, any Subnet validator added to the network before `ConvertSubnetToL1Tx` will continue to validate the network until its "end time" is reached.

Once a Subnet has been converted to an L1, Subnet validators can no longer be added. After a previous Subnet validator is removed or its "end time" is reached, a validator with
the same NodeID can be re-added as an L1 validator to the network with `RegisterL1ValidatorTx`, the same as any other L1 validator who wishes to join the network.

0 comments on commit b83f99b

Please sign in to comment.