Avalanche Network Unveils New Proposal Framework for Community-Driven Enhancements

In a significant development for the blockchain ecosystem, the Avalanche Network has introduced a groundbreaking framework known as Avalanche Community Proposals (ACPs). These ACPs are set to revolutionize how changes and improvements are proposed, discussed, and implemented within the Avalanche Network, promoting community involvement and consensus building.

The Avalanche Network, a leading blockchain platform, has been at the forefront of innovation in the decentralized finance (DeFi) and blockchain space. To further enhance its capabilities and ensure the active involvement of its vibrant community, it has launched the ACP framework, offering a structured process for proposing and implementing changes.

What is an Avalanche Community Proposal (ACP)?

An Avalanche Community Proposal is a concise document designed to introduce a change or best practice for adoption on the Avalanche Network. Each ACP is expected to provide clear technical specifications for any proposed changes, along with a compelling rationale for their adoption. This framework aims to foster transparency, open discussion, and consensus building among the network’s community members.

Importantly, ACPs are open to anyone within the community who wishes to contribute to the network’s development. They can create ACPs and initiate discussions on these proposals through the official Avalanche GitHub repository, promoting a culture of open-source collaboration and innovation.

Three Distinct ACP Tracks

The ACP framework encompasses three primary tracks, ensuring that a wide range of proposals and improvements can be considered:

  1. Standards Track ACPs: These proposals describe changes to the design or functionality of the Avalanche Network. They may include modifications to the P2P networking protocol, adjustments to the P-Chain design, Subnet architecture, or any other changes that impact the interoperability of Avalanche Network Clients (ANCs).
  2. Best Practices Track ACPs: These proposals define design patterns or common interfaces that should be adopted across the Avalanche Network. Such proposals can facilitate easier integration with Avalanche or enhance the interoperability of subnets with one another. Examples may include suggestions for smart contract interfaces or improvements to existing practices without changing how smart contracts are executed.
  3. Meta Track ACPs: In this category, proposals focus on changes to the ACP process itself or suggest new ways for the Avalanche community to collaborate more effectively.

Four ACP Statuses

The ACP framework also maintains a set of statuses to track the progress of each proposal:

  1. Proposed ACP: A proposal at this stage has been merged into the main branch of the ACP repository and is actively under discussion within the Avalanche Community. Modifications may be made based on feedback.
  2. Implementable ACP: Proposals that have reached this status are considered “ready for implementation” by the author(s). They are unlikely to undergo significant changes from their current form. Implementable ACPs may receive recommendations from the Avalanche Foundation, indicating potential benefits to the network, but such recommendations are non-binding.
  3. Recommended ACP: A proposal that has received a recommendation from the Avalanche Foundation. However, it’s essential to note that this recommendation does not create any obligation or liability for individuals or the foundation. It represents the opinion of the foundation and is made without guarantees.
  4. Stale ACP: Proposals in this category have been abandoned by their author(s) due to lack of community support or replacement by another ACP. They may also become stale if no progress is made on them for an extended period.

The ACP Workflow

The ACP process commences with the birth of a new idea for the Avalanche Network. Potential ACPs must have an author(s) responsible for crafting the proposal, initiating discussions on GitHub, and working to build consensus within the community. The entire process, from the initial idea to the ACP submission, is open and transparent.

Authors are encouraged to gauge support for their ideas by posting them in the “Ideas” category on GitHub Discussions before formally drafting an ACP. This public vetting process helps save time for both the author(s) and the wider Avalanche Community, ensuring that ideas align with community needs and priorities.

Once confidence in the proposal’s potential acceptance is established, an ACP is drafted and submitted as a pull request. It is crucial that each ACP is focused on a single key proposal or new idea. The more focused the proposal, the higher the chances of its success. After merging, an official GitHub Discussion is opened for the ACP, allowing for community discussion and support.

Importantly, the Avalanche Community has the opportunity to voice its support or objection to an ACP at any time through a “Straw Poll,” further emphasizing the democratic nature of the framework.

The process concludes with the ACP being marked as “Implementable” and addressing all open questions. An associated reference implementation is provided if applicable, and the proposal is available for adoption by members of the Avalanche Network.

In Conclusion

The introduction of Avalanche Community Proposals (ACPs) is a significant step toward community-driven blockchain development and improvement. The framework not only empowers community members to propose changes and enhancements but also emphasizes transparency, open discussion, and consensus building. As the Avalanche Network continues to evolve, ACPs are poised to play a crucial role in shaping its future. It will be interesting to see how this innovative approach enhances the functionality and adoption of the Avalanche Network in the coming months.

Read more:

Join us on Telegram

Follow us on Twitter

Follow us on Facebook

Follow us on Reddit

You might also like