ACP Summaries
Avalanche Community Proposals (ACPs) by number and title. For complete details, see the official ACP repository.
Last Updated: October 30, 2025
ACP Index
| ACP | Title | Status | Date |
|---|---|---|---|
| 13 | Subnet-Only Validators (SOVs) | Superseded by ACP-77 | Proposed 2023 |
| 20 | Ed25519 p2p | Activated | Dec 16, 2024 (Etna) |
| 23 | P-Chain Native Transfers | Activated | Mar 6, 2024 (Durango) |
| 24 | Shanghai EIPs on C-Chain | Activated | Mar 6, 2024 (Durango) |
| 25 | Virtual Machine Application Errors | Activated | Mar 6, 2024 (Durango) |
| 30 | Integrate Avalanche Warp Messaging into the EVM | Activated | Mar 6, 2024 (Durango) |
| 31 | Enable Subnet Ownership Transfer | Activated | Mar 6, 2024 (Durango) |
| 41 | Remove Pending Stakers | Activated | Mar 6, 2024 (Durango) |
| 62 | Disable AddValidatorTx and AddDelegatorTx | Activated | Mar 6, 2024 (Durango) |
| 75 | Acceptance Proofs | Proposed | 2024 |
| 77 | Reinventing Subnets | Activated | Dec 16, 2024 (Etna/Avalanche9000) |
| 83 | Dynamic Multidimensional Fees for P-Chain and X-Chain | Superseded by ACP-103 | 2024 |
| 84 | Table Preamble for ACPs | Activated | 2024 |
| 99 | Validator Manager Solidity Standard | Proposed | 2024 |
| 103 | Add Dynamic Fees to the X-Chain and P-Chain | Activated | Dec 16, 2024 (Etna) |
| 108 | EVM Event Importing | Proposed | 2024 |
| 113 | Provable Virtual Machine Randomness | Stale | 2024 |
| 118 | Warp Signature Request Interface Standard | Activated | Dec 16, 2024 (Etna) |
| 125 | Reduce C-Chain minimum base fee from 25 nAVAX to 1 nAVAX | Activated | Dec 16, 2024 (Etna) |
| 131 | Activate Cancun EIPs on C-Chain and Subnet-EVM chains | Activated | Dec 16, 2024 (Etna) |
| 151 | Use current block P-Chain height as context for state verification | Activated | Dec 16, 2024 (Etna) |
| 176 | Dynamic EVM Gas Limits and Price Discovery Updates | Activated | Apr 8, 2025 (Octane) |
| 181 | P-Chain Epoched Views | Proposed | 2025 |
| 191 | Seamless L1 Creation | Proposed | 2025 |
| 194 | Streaming Asynchronous Execution | Proposed | 2025 |
| 204 | Precompile secp256r1 | Proposed | 2025 |
| 209 | EIP7702 Style Account Abstraction | Proposed | 2025 |
| 224 | Dynamic Gas Limit in Subnet EVM | Proposed | 2025 |
| 226 | Dynamic Minimum Block Times | Proposed | 2025 |
This list reflects all ACPs documented in the provided repository. Some have been activated, while others remain in proposed or implementable states. A few have been superseded by newer proposals (e.g., ACP-77 supersedes ACP-13, and ACP-103 supersedes ACP-83).
Major Upgrade Timeline
Durango Upgrade (March 6, 2024)
Activated ACPs: 23, 24, 25, 30, 31, 41, 62
The Durango upgrade brought Avalanche Warp Messaging to the C-Chain and Subnet-EVM, enabling native cross-chain communication. It also introduced P-Chain native transfers, removed pending stakers, and incorporated Ethereum’s Shanghai upgrade features.
Etna Upgrade / Avalanche9000 (December 16, 2024)
Activated ACPs: 20, 77, 103, 118, 125, 131, 151
The largest network upgrade since mainnet launch, Avalanche9000 (also called Etna) fundamentally changed how L1s operate. It eliminated the 2,000 AVAX staking requirement for L1 validators, replacing it with a continuous dynamic fee model. This upgrade also reduced C-Chain base fees by 96% and added dynamic fees to the P-Chain and X-Chain.
Octane Upgrade (April 8, 2025)
Activated ACP: 176
The Octane upgrade introduced dynamic gas limits and enhanced price discovery mechanisms for the C-Chain and Subnet-EVM chains, allowing validators to dynamically adjust target gas consumption without requiring hard forks.
For a systems-level analysis of how these ACPs interact with the Avalanche economic model, see the Avalanche Economic Model: A Systems Engineering Perspective and Subsystem Analysis and MultiGraph documents.
Detailed ACP Descriptions
ACP-13: Subnet-Only Validators (SOVs) | Proposed 2023 | Superseded by ACP-77
This proposal aimed to introduce a new validator type that could validate Avalanche L1s (formerly called Subnets) without validating the Primary Network. It would have required nodes to pay a refundable 500 AVAX fee instead of staking 2000+ AVAX. The goal was to lower the barrier to entry for L1 validation, especially for regulated entities prohibited from validating permissionless chains. SOVs would only need to sync the P-Chain (not X/C-Chain), reducing hardware requirements. This ACP was later superseded by ACP-77 (Reinventing Subnets), which took a more comprehensive approach to the same problem space. For more on the L1 ecosystem dynamics, see the L1 Ecosystem subsystem analysis.
ACP-20: Ed25519 p2p | Activated Dec 16, 2024
This proposal aims to support Ed25519 TLS certificates for p2p communications on the Avalanche network. It would allow the use of Ed25519 public keys for Avalanche Network Client NodeIDs and support Ed25519 signatures in the ProposerVM. The key benefits include smaller key sizes (32-byte public key, 64-byte private key, 64-byte signature) compared to RSA/ECDSA, simplified node maintenance by generating TLS certificates in-memory on startup, and wider crypto industry adoption. This cryptographic improvement affects all subsystems by enhancing network efficiency and security.
ACP-23: P-Chain Native Transfers | Activated Mar 6, 2024
This activated proposal added support for native transfers on the P-chain, enabling users to transfer P-chain assets without leaving the P-chain or abusing other transaction types. It registered the BaseTx transaction type with ID 0x22 in codec version 0x00, providing a cheaper option for both validators and end-users to perform simple transfers as L1 adoption grows. This relates to the Fee Dynamics subsystem by providing more efficient transaction options.
ACP-24: Shanghai EIPs on C-Chain | Activated Mar 6, 2024
This activated proposal adopted several Ethereum Improvement Proposals (EIPs) from Ethereum’s Shanghai upgrade to the Avalanche C-Chain: EIP-3651 (Warm COINBASE), EIP-3855 (PUSH0 instruction), EIP-3860 (Limit and meter initcode), and EIP-6049 (Deprecate SELFDESTRUCT). This maintained compatibility with upstream EVM tooling, infrastructure, and developer experience, supporting the L1 Ecosystem subsystem through EVM standardization.
ACP-25: Virtual Machine Application Errors | Activated Mar 6, 2024
This activated proposal introduced a way for Virtual Machines (VMs) to signal application-defined error conditions to another VM. It added a new AppError message type to the p2p protocol, allowing peers to communicate error conditions instead of relying on timeouts. This enables Avalanche nodes to score peers based on perceived errors and decreases latency in failure scenarios, improving the overall reliability of the L1 Ecosystem subsystem.
ACP-30: Integrate Avalanche Warp Messaging into the EVM | Activated Mar 6, 2024
This activated proposal integrated Avalanche Warp Messaging (AWM) into the C-Chain and Subnet-EVM to enable cross-L1 communication. It introduced a Warp Precompile at address 0x0200000000000000000000000000000000000005 with functions for sending and verifying warp messages, creating a standard implementation of AWM in production on the Avalanche Network. This is fundamental to the L1 Ecosystem subsystem by enabling interoperability between chains.
ACP-31: Enable L1 Ownership Transfer | Activated Mar 6, 2024
This activated proposal allows the current owner of an L1 to transfer ownership to a new owner. It introduced a new transaction type (TransferSubnetOwnershipTx) that takes an L1 ID, verifies the SubnetAuth against the current Owner, and assigns a new Owner to the L1. This enables L1 operators to rotate their control keys periodically or transfer L1 control to new entities, with a fee of 0.001 AVAX. This relates to the Governance subsystem and L1 Ecosystem dynamics.
ACP-41: Remove Pending Stakers | Activated Mar 6, 2024
This activated proposal removed user-specified StartTime for stakers, instead starting the staking period immediately when a staking transaction is accepted. This significantly improved P-chain efficiency by eliminating the need to maintain a pending set of stakers, making MaxValidatorStake verification an O(1) operation, and reducing computational load on validators. This optimization directly affects the Staking Dynamics subsystem.
ACP-62: Disable AddValidatorTx and AddDelegatorTx | Activated Mar 6, 2024
This activated proposal disabled the legacy AddValidatorTx and AddDelegatorTx transaction types, pushing all new stakers to use AddPermissionlessValidatorTx and AddPermissionlessDelegatorTx instead. This ensured all new validators register a BLS key, accelerating the timeline for future P-Chain upgrades and reducing the number of ways to participate in Primary Network validation from two to one. This standardization affects the Staking Dynamics subsystem by simplifying validator onboarding.
ACP-75: Acceptance Proofs | Proposed 2024
This proposed feature introduces support for proving a block’s acceptance in consensus. It allows peers to verify any block accepted by consensus even if they haven’t synced that part of the chain. This enhances fault isolation between the Primary Network and L1s, addressing a potential liveness concern where P-Chain stalling could prevent L1 block verification. This proposal strengthens the L1 Ecosystem subsystem by improving security guarantees.
ACP-77: Reinventing Subnets | Activated Dec 16, 2024
This activated proposal completely overhauled L1 creation and management (renaming “Subnets” to “L1s”). It separated L1 validators from Primary Network validators, moved ownership of L1 validator set management from the P-Chain to L1s themselves, and introduced a continuous P-Chain fee mechanism for L1 validators. This enabled Avalanche Layer 1s with greater flexibility and sovereignty, allowing for ERC-20/ERC-721/arbitrary staking mechanisms. The initial fee is approximately 1.3 AVAX per month per validator. This fundamentally restructured the L1 Ecosystem subsystem and introduced new dynamics in the Staking and Fee Dynamics subsystems.
ACP-83: Dynamic Multidimensional Fees for P-Chain and X-Chain | Superseded by ACP-103 | 2024
This stale proposal aimed to introduce a dynamic and multidimensional fee scheme for the P-chain and X-chain. It would have measured transaction complexity along four dimensions (Bandwidth, Reads, Writes, Compute) and dynamically adjusted fees based on network congestion. This proposal was superseded by ACP-103, which took a simpler approach to dynamic fees. See the Fee Dynamics subsystem analysis for more on how fee mechanisms affect the broader economic system.
ACP-84: Table Preamble for ACPs | Activated 2024
This activated meta-proposal replaced the plain-text code block in ACP preambles with a more readable Markdown table format. This improved readability and user experience by making links clickable and information more clearly organized, similar to the format used in Ethereum EIPs. This enhancement supports the Governance subsystem by improving proposal documentation standards.
ACP-99: Validator Manager Solidity Standard | Proposed 2024
This proposed best practice defines a standard Validator Manager Solidity smart contract interface for Avalanche EVM chains. It provides a specification for contracts that can manage an L1 validator set (as introduced in ACP-77) through standard methods for validator registration, weight updates, and removal. This standardization aims to lower the cost of launching L1s on Avalanche and directly supports the L1 Ecosystem subsystem growth objectives.
ACP-103: Add Dynamic Fees to the X-Chain and P-Chain | Activated Dec 16, 2024
This activated proposal introduced a dynamic fee mechanism to the P-Chain (superseding ACP-83). It defines a single dimension of gas consumption that incorporates bandwidth, reads, writes, and compute costs. The mechanism adjusts fees based on excess gas consumption to maintain a target gas consumption rate, similar to EIP-1559 in Ethereum. This is a core component of the Fee Dynamics subsystem and affects Token Supply through its burn mechanism.
ACP-108: EVM Event Importing | Proposed 2024
This proposed best practice defines a standard smart contract interface for importing EVM events from other blockchains within Avalanche using Avalanche Warp Messaging. It specifies methods for authenticating block hashes and verifying Merkle proofs of events, enabling cross-chain applications without requiring direct interaction on the source chain. This builds on ACP-30 and enhances the L1 Ecosystem subsystem interoperability.
ACP-113: Provable Virtual Machine Randomness | Stale 2024
This stale proposal aimed to introduce a mechanism for generating verifiable, non-cryptographic random number seeds on the Avalanche platform. It would have used a BLS-based VRF implementation where block proposers recursively sign previous signatures. The proposal was marked stale due to documented security concerns, particularly the ability for malicious block producers to bias randomness, requiring complex mitigation strategies that were deemed too costly for the Primary Network. While stale, this proposal highlights important considerations for future protocol enhancements in the Governance subsystem.
ACP-118: Warp Signature Request Interface Standard | Activated Dec 16, 2024
This implementable best practice proposes a standard format for requesting Warp signatures through the AppRequest protocol. It defines SignatureRequest and SignatureResponse message types that VMs can use to request and provide signatures for Warp messages in a VM-agnostic manner. This standardization simplifies signature aggregator implementations and supports cross-VM functionality, complementing ACP-30 and ACP-108 in the L1 Ecosystem subsystem.
ACP-125: Reduce C-Chain minimum base fee from 25 nAVAX to 1 nAVAX | Activated Dec 16, 2024
This activated proposal reduced the minimum base fee on the Avalanche C-Chain from 25 nAVAX to 1 nAVAX, a reduction of 96%. The change was made because the previous minimum was observed to be higher than market demand, artificially reducing network usage. The dynamic fee algorithm had proven capable of responding appropriately during high-use periods, making the higher minimum unnecessary. This optimization affects the Fee Dynamics subsystem by improving price discovery and network utilization. Post-activation, average transaction fees dropped from approximately 0.01.
ACP-131: Activate Cancun EIPs on C-Chain and L1-EVM chains | Activated Dec 16, 2024
This activated proposal enabled new EVM opcodes and changes from Ethereum’s Cancun upgrade on the Avalanche C-Chain and L1-EVM chains. It included EIP-4844 (BLOBHASH opcode), EIP-7516 (BLOBBASEFEE opcode), EIP-1153 (Transient storage), EIP-5656 (MCOPY opcode), and EIP-6780 (SELFDESTRUCT only in same transaction). Notably, it excluded blob transactions from EIP-4844. This maintains compatibility within the L1 Ecosystem subsystem by ensuring EVM standardization.
ACP-151: Use current block P-Chain height as context for state verification | Activated Dec 16, 2024
This activated proposal modified the ProposerVM to pass inner VMs the P-Chain block height of the current block being built rather than the parent block’s height. This allows for more reliable verification of ICM (Interchain Message) aggregated signatures, making operations that modify validator sets verifiable sooner and more reliably. This improvement enhances the security and reliability of the L1 Ecosystem subsystem and Staking Dynamics.
ACP-176: Dynamic EVM Gas Limits and Price Discovery Updates | Activated Apr 8, 2025
This activated standards change modified the C-Chain and L1-EVM chains to adopt a dynamic fee mechanism similar to the one introduced on the P-Chain in ACP-103, but with modifications allowing block proposers (validators) to dynamically adjust the target gas consumption rate. The proposal defines a mechanism where validators can incrementally increase or decrease the target gas consumption rate in blocks they produce, causing the effective rate to converge to a point where 50% of voting stake weight wants it increased and 50% wants it decreased. This removes the need for network upgrades to adjust gas limits as the network’s capacity evolves. Following activation, validators increased the C-Chain’s target gas from 1.6M to 2.1M gas/second (30% increase). This proposal represents an evolution of the Fee Dynamics subsystem with implications for Governance through its distributed parameter adjustment mechanism.
ACP-181: P-Chain Epoched Views | Proposed 2025
This proposed standards track ACP introduces epoched views for the P-Chain, providing a mechanism for organizing validator sets and state transitions into discrete epochs. This architectural change aims to improve the efficiency of validator set management and state verification processes. The proposal would enable more efficient synchronization and verification mechanisms for validators joining the network or catching up after downtime, supporting the scalability of the Staking Dynamics subsystem.
ACP-191: Seamless L1 Creation | Proposed 2025
This proposed standards track ACP introduces the CreateL1Tx transaction type to streamline the process of creating new Avalanche Layer 1 blockchains. Building on the foundation established by ACP-77, this proposal aims to further reduce friction in the L1 creation process by simplifying the required steps and reducing operational overhead. This directly supports the growth objectives of the L1 Ecosystem subsystem by making it easier for developers to launch customized blockchain solutions.
ACP-194: Streaming Asynchronous Execution | Proposed 2025
This proposed standards track ACP introduces Streaming Asynchronous Execution (SAE), a fundamental architectural change that separates block execution from the consensus process. By decoupling these previously synchronous operations, SAE allows for continuous execution threads that operate independently of consensus, enabling gas targets to align with average-case execution times rather than being constrained by worst-case scenarios. This means the network can maintain higher throughput targets without risking consensus delays during computationally intensive blocks. SAE is expected to significantly improve the performance and scalability of the C-Chain and all EVM-based L1s, with potential activation planned for Q3 2025. This represents a major evolution of the L1 Ecosystem subsystem scalability capabilities.
ACP-204: Precompile secp256r1 | Proposed 2025
This proposed standards track ACP implements EIP-7951 for secp256r1 (P-256) signature verification on Avalanche’s C-Chain. The proposal introduces a precompiled contract at address 0x0000000000000000000000000000000000000100 that performs native verification of P-256 signatures at a cost of 6,900 gas. The secp256r1 curve is the standard cryptographic curve used by modern device security systems, including Apple’s Secure Enclave, Android Keystore, WebAuthn, and Passkeys. Currently, developers must use expensive Solidity-based verification costing 200k-330k gas per signature. This precompile would significantly improve gas efficiency for biometric authentication systems and device-based signing mechanisms, making Avalanche more accessible for consumer-facing applications that rely on device-native cryptography.
ACP-209: EIP7702 Style Account Abstraction | Proposed 2025
This proposed standards track ACP introduces EIP-7702-style account abstraction capabilities to Avalanche’s C-Chain and L1-EVM chains. EIP-7702 allows Externally Owned Accounts (EOAs) to temporarily delegate control to smart contract code during a transaction, enabling sophisticated account features like batched operations, sponsored transactions, and custom authorization logic without requiring users to migrate to smart contract wallets. This proposal would bring account abstraction capabilities to Avalanche in a way that’s compatible with existing wallets and user experience patterns, potentially improving accessibility for mainstream users and supporting the growth of the L1 Ecosystem subsystem.
ACP-224: Dynamic Gas Limit in Subnet EVM | Proposed 2025
This proposed standards track ACP extends the dynamic gas limit mechanism introduced in ACP-176 to Subnet-EVM chains, introducing a Fee Manager Precompile that allows L1 operators to configure and manage their own dynamic gas limit parameters. This gives individual L1s the flexibility to set their own gas targets, minimum/maximum bounds, and adjustment rates based on their specific use cases and performance requirements. The proposal enhances the sovereignty and customization capabilities established by ACP-77, supporting diverse application requirements within the L1 Ecosystem subsystem.
ACP-226: Dynamic Minimum Block Times | Proposed 2025
This proposed standards track ACP introduces the ability to dynamically adjust minimum block times on Avalanche chains based on network conditions and validator consensus. Currently, minimum block times are fixed parameters that require network upgrades to modify. This proposal would allow validators to signal their preferences for minimum block time adjustments, similar to the dynamic gas limit mechanism in ACP-176. Dynamic minimum block times would enable the network to optimize for latency when conditions allow while maintaining stability during periods of high load, representing another step toward adaptive, self-tuning network parameters in the Governance subsystem.
Future Enhancements
Several additional improvements are on the horizon for the Avalanche network:
-
Firewood Database Integration: Expected to significantly improve blockchain database operation performance and reduce validator node storage requirements through optimized data layout and state pruning.
-
Additional Network Optimizations: Continued incremental improvements to gas targets and throughput capacity as validator infrastructure evolves.
-
Enhanced Interoperability: Further development of cross-L1 communication standards and capabilities building on AWM and ICM foundations.
References
Document maintained by the Avalanche community. For the most current information, please refer to the official ACP repository.