Avalanche has successfully activated the Banff upgrade on its mainnet, marking a pivotal evolution in its subnet architecture. This upgrade introduces a transformative feature: subnet validators can now stake using the subnet's own native tokens to earn rewards. It also grants subnet creators the ability to remove validators from their subnet before the staking period concludes.
This enhancement is a cornerstone for Avalanche's vision of a more flexible and accessible network, fundamentally changing how subnet security and participation operate.
What Is the Banff Upgrade?
The Banff upgrade is a significant hard fork to the Avalanche network. It represents a major step forward in the platform's development, focusing on improving the functionality and economic incentives within its growing ecosystem of subnets.
For a validator to continue participating effectively, they must upgrade to the latest client version. Failure to do so will result in the node being marked as offline, leading to a reduction in its staking rewards. This mandatory update ensures network consensus and security.
Key Features of the Banff Upgrade
The activation of Banff unlocks several powerful new capabilities for the Avalanche ecosystem.
Staking with Subnet Tokens: Previously, validators were required to stake the primary Avalanche token (AVAX) to secure a subnet. The Banff upgrade changes this dynamic. Now, a subnet can be configured to allow validators to stake using that subnet's unique native token. This directly rewards those who provide computational resources and security to the specific subnet using its own economy.
Enhanced Control for Subnet Creators: Subnet creators are granted more flexibility. They now have the ability to remove a validator from their subnet before its staking period has officially ended, allowing for more agile network management.
The Concept of Elastic Subnets: It is crucial to understand that these new features are not automatically applied to all existing subnets. To leverage this new staking model, a subnet creator must choose to convert their subnet into an Elastic Subnet. This conversion is a one-way process that permanently locks the subnet's configuration, abandoning the creator's control keys in favor of a decentralized, token-governed model.
The Impact of Elastic Subnets
Patrick O'Grady, Engineering Lead at Ava Labs, emphasized the importance of this development, stating, "Since the network launched in 2020, Elastic Subnets are the biggest feature for Avalanche." This shift is profound because it democratizes subnet validation.
When a creator converts their subnet to an Elastic Subnet, they open up the staking process to anyone who holds the subnet's native token. This allows token holders to directly participate in securing the network they are invested in and be rewarded for it, thereby enhancing the subnet's overall security and decentralization.
👉 Explore more strategies for network participation
However, it's important to note that while a subnet can use its own token for staking rewards and validation, a validator must still stake a base amount of AVAX on the Primary Network. This AVAX stake remains a prerequisite as it is essential for the upcoming native cross-subnet messaging functionality, a feature that will enable seamless communication between different subnets on Avalanche.
The Journey to Mainnet Activation
The path to the mainnet release of Banff began with its activation on the Fuji testnet. This testing phase, which commenced after the upgrade's announcement, allowed developers and validators to familiarize themselves with the new changes in a risk-free environment before the official mainnet deployment.
This careful, phased approach is standard practice in blockchain development, ensuring stability and security for the entire network during a significant protocol upgrade like a hard fork.
Frequently Asked Questions
What is an Avalanche Elastic Subnet?
An Elastic Subnet is a configured Avalanche subnet that allows validators to use its native token for staking instead of solely relying on AVAX. It opens up validation to any holder of the subnet's token, decentralizing security and aligning rewards with the subnet's own economy.
Do validators still need AVAX after the Banff upgrade?
Yes. Even on an Elastic Subnet, a validator must still stake AVAX on the Primary Network. This requirement is fundamental for network-wide security and is a prerequisite for future features like native cross-subnet communication.
Is the Banff upgrade mandatory for all Avalanche validators?
Absolutely. The Banff upgrade is a hard fork. All validators must upgrade their node software to the latest version to remain in consensus with the network. Those who do not upgrade will be marked offline and will see their staking rewards diminished.
What happens when a subnet becomes "elastic"?
Converting a subnet to an Elastic Subnet is a permanent, one-way operation. The creator relinquishes their control keys, and the subnet's staking parameters—like minimum stake amount and reward distribution—are locked in and governed by the code and the token holders.
Can any subnet use its own token for staking now?
Not automatically. Only subnets that have been specifically converted by their creators into Elastic Subnets will support this new staking model. Existing subnets continue to operate under their previous rules unless converted.
How does Banff improve subnet security?
By allowing any holder of a subnet's token to become a validator, Banff incentivizes more participants to help secure the network. A broader and more distributed validator set enhances the censorship-resistance and robustness of the subnet.