The Permissionless Subnet and Elastic Validation Standards, primarily defined by ACP-77 and implemented in the Etna upgrade, represent a foundational shift in how Subnets on Avalanche secure themselves. Previously, Subnets relied on a permissioned set of validators manually curated by the Subnet creator, creating a closed security model. These new standards introduce a mechanism where anyone can become a validator for a Subnet by staking a specified asset, making the validator set dynamic and economically weighted. This directly impacts the P-Chain, which now manages the staking, delegation, and reward distribution for these elastic Subnets.
Protocols
Permissionless Subnet and Elastic Validation Standards
Impact analysis of the ACPs that define permissionless validator sets for Subnets, including staking, delegation, and slashing mechanics. A core component of the Etna upgrade, requiring validators and stakers to assess new economic security models.
introduction
PERMISSIONLESS VALIDATION AND ECONOMIC SECURITY
Introduction
The ACP-driven standards that transition Avalanche Subnets from permissioned validator sets to elastic, stake-weighted validation, fundamentally altering security models and operator requirements.
Operationally, this change decouples Subnet validation from the Primary Network's validator set. Under ACP-77, Subnet validators are no longer required to be validators of the Primary Network, lowering the barrier to entry but introducing a new, Subnet-specific staking token and its associated economic security model. The standards define the mechanics for continuous staking, churn limits, delegation, and crucially, the potential for slashing. Validators and stakers must now assess the security of a Subnet not by the reputation of a fixed list of operators, but by the market cap and staking dynamics of its native token, a model that requires new risk assessment frameworks.
For builders, exchanges, and wallet providers, this transition mandates a thorough review of integration points. Custody solutions must adapt to support staking and delegation operations on the P-Chain for potentially hundreds of Subnet tokens. Subnet architects must design and communicate their slashing conditions, reward curves, and unbonding periods clearly, as these parameters are now programmable and directly influence validator participation. Chainscore Labs can assist teams in auditing these new economic security parameters, reviewing validator client implementations for compliance with ACP-77, and stress-testing the operational readiness of staking infrastructure before a Subnet transitions to a permissionless model.
PERMISSIONLESS SUBNET AND ELASTIC VALIDATION STANDARDS
Quick Facts
Operational impact of ACPs enabling permissionless validator sets, staking, delegation, and slashing for elastic Subnets under the Etna upgrade.
| Area | What changes | Who is affected | Action |
|---|---|---|---|
Validator Set Management | Subnets can transition from a permissioned allowlist to a permissionless, stake-weighted validator set. | Subnet operators, validators, stakers | Review ACP-20 and ACP-77 for activation criteria and migration paths. |
Staking Mechanism | Validators and delegators stake the Subnet's native token or a designated asset to secure the network. | Validators, wallet providers, exchanges | Integrate new staking and delegation transactions into wallet and custody flows. |
Delegation Model | Token holders can delegate stake to validators, sharing rewards and slashing risk. | Token holders, staking UI providers | Update staking interfaces to support delegation and reward claiming logic. |
Slashing Conditions | Validators and delegators face slashing for defined misbehavior, such as downtime or equivocation. | Validators, delegators, risk teams | Audit slashing rules and ensure operational practices meet uptime requirements. |
Economic Security | Security shifts from social trust to cryptoeconomic incentives based on staked value. | Protocol architects, investors | Model cost-of-corruption scenarios and verify stake distribution assumptions. |
Validator Client Requirements | AvalancheGo and custom VM binaries must support new staking, delegation, and slashing logic. | Node operators, infrastructure providers | Upgrade to Etna-compatible client versions and test in a staging environment. |
Cross-Subnet Implications | Permissionless Subnets may alter assumptions for bridges and cross-chain protocols relying on validator honesty. | Bridge operators, DeFi protocols | Reassess trust models and verify validator set proofs for cross-chain messages. |
Governance Control | Subnet governance retains authority over parameters like minimum stake, delegation rates, and slashing severity. | Subnet governance participants | Define and ratify initial economic parameters before enabling permissionless validation. |
technical-context
FROM DELEGATED TO NATIVE STAKING
Technical Mechanism
How ACP-77 and ACP-103 transform Subnet validation from a P-Chain delegation model to a native, elastic staking system.
The Permissionless Subnet and Elastic Validation standards, primarily defined by ACP-77 and refined by ACP-103, fundamentally re-architect how Subnets on Avalanche secure themselves. Before the Etna upgrade, a Subnet's validators were a subset of the Primary Network's validators, requiring them to stake a minimum of 2,000 AVAX on the P-Chain. This model created a high economic barrier and a rigid, binary security posture: a Subnet was either validated by the entire Primary Network validator set or a manually curated subset. The new standards decouple Subnet validation from Primary Network staking entirely, introducing a model where a Subnet's validators stake the Subnet's own native token directly on the P-Chain, creating an independent, economically secured validator set.
This mechanism is enabled by converting a Subnet into an Elastic Subnet. The conversion process, initiated by the Subnet's governance, activates a continuous ConvertSubnetTx that registers the Subnet's native gas token as its staking asset. Once converted, any holder of that token can permissionlessly become a validator by posting a stake, which is locked on the P-Chain. The Subnet's economic security becomes elastic, scaling up and down with the market value of its token and the willingness of holders to stake. ACP-103 introduces a critical refinement: a ValidatorManager smart contract on the P-Chain that standardizes the lifecycle of these elastic validators, including registration, staking, delegation, and the calculation of staking rewards and slashing penalties, making the system programmable and consistent across Subnets.
For operators and builders, this shift changes the trust and security model. A Subnet's liveness and safety are no longer anchored to the AVAX stake but to the economic value and distribution of its own token. This introduces new risks, such as a low-float token enabling a cheap validation takeover, or a volatile token price causing mass validator churn. The operational impact is significant: validators must now manage a new staking workflow for each Subnet's token, and Subnet architects must carefully design their ValidatorManager parameters—including delegation rules, unbonding periods, and slashing conditions—to ensure long-term security. Chainscore Labs can review these economic security parameters and the ValidatorManager implementation to identify risks before the Subnet's conversion to an elastic model.
WHO MUST RESPOND TO ELASTIC VALIDATION
Affected Actors
Subnet Architects and Operators
Elastic validation fundamentally changes the security model from a permissioned set of known validators to a permissionless, stake-weighted set. Subnet builders must decide whether to convert existing Subnets to elastic validation or launch new ones under this model.
Key actions:
- Audit the Subnet's VM for compatibility with dynamic validator churn and potential reorganization depth.
- Design and parameterize the staking token economics, including minimum stake, delegation ratios, and slashing conditions.
- Implement a validator uptime monitoring system; elastic Subnets require active performance tracking to detect non-responsive nodes.
- Plan a governance process for adjusting parameters like the delegation fee and minimum stake without disrupting active validators.
Chainscore Labs can review your Subnet's transition plan, assess economic security parameters, and audit the VM's interaction with the P-Chain's validator manager.
implementation-impact
VALIDATOR AND SUBNET OPERATOR ACTIONS
Implementation Impact
The shift to permissionless validation and elastic staking fundamentally alters the security model for Subnets. Operators, stakers, and builders must assess new economic incentives, validator lifecycle management, and integration points.
01
Validator Onboarding and Lifecycle
Operators must adapt infrastructure to support permissionless validator registration, continuous staking, and dynamic weight changes. Unlike the fixed-duration model, elastic validation requires monitoring of active stake weight, delegation fluctuations, and automated reward compounding. Teams should review the P-Chain APIs for validator registration and ensure their node management tooling can handle non-deterministic validator set churn without manual intervention.
02
Economic Security Re-evaluation
Elastic Subnets allow the staking token to be the Subnet's native gas token, decoupling security from AVAX. Subnet architects must design a sustainable token-economic model where the value at stake exceeds the profit from corruption. This requires modeling staking yields, slashing conditions, and the liquidity profile of the native token. A flawed design can lead to a death spiral where a token price drop directly weakens network security.
03
Delegation and Staking Provider Integration
Wallets, exchanges, and liquid staking protocols must integrate with the new delegation mechanics on the P-Chain. This includes supporting partial delegation, reward claiming, and unstaking periods specific to elastic Subnets. Custody providers need to build workflows for non-custodial delegation that differ significantly from the legacy AddDelegator transaction, requiring updates to transaction parsing, signing, and balance tracking systems.
04
Slashing Mechanism and Uptime Enforcement
Permissionless Subnets can enforce uptime requirements and slashing for validators that fail to produce blocks or sign Warp messages. Node operators must harden their infrastructure against downtime to avoid economic penalties. Monitoring and alerting systems must be configured to track validator health against the specific Subnet's SLA parameters, as a simple Primary Network health check is insufficient to prevent slashing on an active elastic Subnet.
05
Bridge and Warp Messaging Trust Model
The security of Warp Messaging for a permissionless Subnet is now directly tied to the economic weight of its dynamic validator set. Bridge operators and cross-chain application developers must stop assuming a static, trusted validator set. They need to implement client-side validation of the BLS multi-signature aggregate and verify that the signing weight meets a configurable threshold before accepting cross-chain messages, especially for high-value asset transfers.
06
Chainscore Labs Upgrade Readiness Review
A successful transition to permissionless validation requires a comprehensive review of your Subnet's tokenomics, validator onboarding flow, and slashing parameters. Chainscore Labs provides an end-to-end protocol impact assessment, including smart contract review for staking modules, integration testing for Warp Messaging signature verification, and operational runbooks for node operators to manage dynamic validator sets securely.
ELASTIC VALIDATION AND PERMISSIONLESS SUBNET RISKS
Risk Matrix
Evaluates the economic security, operational, and integration risks introduced by permissionless validator sets and elastic staking for Subnets under the Etna upgrade.
| Risk Area | Failure Mode | Severity | Affected Actors | Mitigation and Action |
|---|---|---|---|---|
Economic Security Dilution | A Subnet's total stake becomes insufficient to deter a Byzantine attack because validators can freely join and leave, lowering the cost of corruption. | High | Subnet architects, DeFi protocols, bridge operators | Subnet architects must design and monitor staking incentive programs. Protocols should verify the economic security threshold against the Subnet's TVL before deployment. |
Staking Derivative Liquidity Crunch | Elastic staking ties up the native gas token, creating a liquidity shortage that prevents users from paying for transaction fees or interacting with core dApps. | Medium | Subnet users, dApp developers, DeFi protocols | Subnet architects should model the liquid supply impact of staking participation targets. Wallets and dApps must ensure fee estimation logic does not fail under low-liquid-supply conditions. |
Validator Set Instability | Rapid churn in the permissionless validator set causes frequent missed blocks or consensus instability if new validators are poorly provisioned or misconfigured. | Medium | RPC providers, exchanges, Subnet operators | Node operators must monitor validator uptime and network health metrics. Exchanges should adjust confirmation depth policies based on observed validator set stability. |
Delegation Centralization | A small number of large delegators control the majority of stake weight, effectively centralizing the permissionless validator set and undermining the security model. | High | Stakers, governance delegates, Subnet architects | Governance should monitor stake distribution and consider delegation caps or incentive adjustments. Risk teams must assess the Nakamoto coefficient of the validator set. |
Slashing Logic Vulnerabilities | Bugs in the new slashing mechanism for elastic Subnets lead to wrongful slashing of honest validators or failure to slash malicious ones. | Critical | Validators, stakers, custodians | Validators and custodians must review the slashing contract logic before depositing stake. Chainscore Labs can perform a dedicated smart contract and integration review. |
Cross-Subnet Bridge Security | A bridge relies on the validator set of a permissionless Subnet for message verification, but the economic security of that set is too low to secure bridged assets. | Critical | Bridge operators, Warp Messaging integrators, DeFi protocols | Bridge operators must independently verify the stake weight and slashing conditions of the source Subnet's validator set. Do not assume all permissionless Subnets meet a minimum security bar. |
P-Chain Congestion | A surge in staking and delegation transactions from many elastic Subnets congests the P-Chain, delaying validator set updates and cross-chain transfers. | Medium | All Subnet validators, exchange custody teams | Infrastructure teams should monitor P-Chain mempool pressure during high-activity periods. Custodians must build graceful retry and timeout logic for staking operations. |
Incentive Misalignment | Validators join a Subnet solely for short-term incentive farming and exit immediately after rewards dry up, causing a sudden security collapse. | High | Subnet architects, DeFi protocols, users | Subnet governance must design vesting or lock-up incentives for validators. Protocols should implement circuit breakers that pause critical functions if the active validator set drops below a threshold. |
PERMISSIONLESS SUBNET AND ELASTIC VALIDATION
Operator Readiness Checklist
A practical checklist for validators, stakers, and Subnet operators preparing for the transition to permissionless and elastic validation models introduced by the Etna upgrade. Each item identifies a critical operational change, explains the risk of inaction, and defines the signal that confirms readiness.
What to check: Review the new staking and delegation mechanics introduced by the relevant ACPs, specifically how the minimum stake duration, delegation caps, and reward distribution logic have changed. Confirm that your node's staking transactions will be compatible with the new rules at activation.
Why it matters: The Etna upgrade fundamentally alters how validators join and leave Subnets. Hardcoded staking parameters in your operational scripts or custody workflows will fail if they assume pre-Etna constraints. A misconfigured staking transaction could result in a validator being unable to join the set or a staker being unable to withdraw.
Readiness signal: A successful testnet staking operation using the post-Etna AvalancheGo client, where the validator is accepted into the active set and rewards accrue according to the new formula.
resource-links
AVALANCHE STANDARDS
Source Resources
Primary resources for tracking permissionless Subnet and elastic validation standards, including ACP text, AvalancheGo implementation work, validator operations, and ecosystem readiness signals.
Chains We Build On
Looking to build on a specific blockchain?
We build smart contracts, DeFi applications, wallets, tokenization platforms, and blockchain infrastructure across the major ecosystems teams choose today. That includes Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Solana, Sui, Aptos, Hedera, Stellar, and NEAR, with support for additional EVM and non-EVM networks based on your product requirements.
EVM ecosystems
- Ethereum
- Arbitrum
- Optimism
- Polygon
- Avalanche
- Cronos
Non-EVM ecosystems
- Solana
- Sui
- Aptos
- Hedera
- Stellar
- NEAR
Additional ecosystems
- Polkadot
- Cosmos
- TON
- Cardano
- Algorand
- Tempo
Also available for Base, appchains, custom EVM networks, and cross-chain product architecture.
OPERATIONAL AND SECURITY FAQ
Frequently Asked Questions
Answers to common questions from validators, stakers, and Subnet architects evaluating the shift to permissionless validation and elastic Subnet security models.
A permissioned Subnet relies on a fixed, pre-approved validator set controlled by the Subnet creator. An Elastic Subnet replaces this with an economic security model where the validator set is permissionless and determined by stake weight.
Key implications:
- Validator entry/exit: Anyone can become a validator by staking the required token on the P-Chain, and they can exit subject to unbonding periods.
- Sybil resistance: Security is no longer based on identity or legal agreements but on the economic cost of acquiring a majority of the staked token.
- Slashing risk: The ACP introduces the possibility of slashing for validators who violate Subnet-specific rules, creating a direct economic penalty for misbehavior.
- Delegation: Token holders who do not run a node can delegate their stake to a validator, increasing the total economic security of the Subnet.
Teams must assess whether the token's market depth and distribution are sufficient to make a 51% attack economically irrational before transitioning to Elastic validation.
Trusted by Industry Leaders
Delivering blockchain solutions for 5+ years.
We have partnered with 50+ leading DeFi protocols, NFT ecosystems, and fintech innovators to build secure, scalable, and capital-efficient blockchain products.
Selected Partners & Clients
“I've been working with Chainscore Labs for last 3+ years, they've consistently delivered with strong ownership across multiple projects. The team is reliable and detail-oriented.”
L
Lee Erswell
CEO, Telos Foundation
how to get started
How to get started?
If you're looking for blockchain integration, ChainScore Labs has 5+ years of experience helping teams build and integrate exchanges, wallets, smart contracts, tokenization solutions, and protocol-connected products, we can help you choose the right path, integrate securely, and get to production faster. Our team consists of experienced blockchain developers and architects who can help you with your blockchain integration needs.
01
Exploration & Strategy
Define your product goals and choose the right blockchain architecture for your use case.
02
Architecture & Design
Design the smart contracts, tokenomics, and security parameters of your system.
03
Development & Integration
Build and integrate with wallets, oracles, and front-end dApps for a seamless experience.
04
Security & Launch
Comprehensive audits followed by a risk-managed mainnet deployment to protect your users.
Explore More Solutions
Discover our
blockchain development services.
We build production-grade blockchain solutions for top-tier projects across DeFi and Web3.
Book a Call
Start a build
Need a blockchain engineering team?
Send the project context and we will respond with next steps, scope questions, and a practical path to delivery.