Apillon recently released the first version of the Apillon platform governance model, defining key objectives, participants, and staged roll-out.
Here are the key takeaways to understanding Apillon governance and how everyone can co-shape the Web3 development with the Apillon platform.
But first…
Governance in Web3
With the emergence of Ethereum smart contracts, transparent, democratic, and decentralized decision-making was introduced to online communities, giving power to their voices.
DAOs, decentralized autonomous organizations, have helped shape products and given rise to novel social and economic schemes, business models, social DAOs, network states, and other platforms where previously passive users became active participants.
Token-weighted voting further enabled the decision-making power to be distributed based on voters’ role and investment in a DAO, favoring long-time contributors over mere spectators.
Decentralized technologies offer a powerful opportunity to gather a project’s fam around a Web3 fire, let them speak and be heard. But to avoid anarchy, autocracy, or abuse, the governance mechanisms should be implemented with strong attention to who decides what, how decisive their vote is, and how to minimize unfair outcomes.
Apillon governance model
The Apillon platform was built by developers for developers. As a product that only survives with adoption, it’s essential to deliver the best possible value for its users, Web3 builders.
The Apillon governance model thus touches upon solely the Apillon platform and product-related questions, not broader business decisions.
The constant feedback loop between voters and the Apillon team implementing the voted features should lead to better product-market fit, clearer development priorities, expansion toward users’ needs, and, ultimately, greater adoption of Apillon in the engineering communities.
What can be subject to community vote?
Apillon governance participants will be able to submit proposals and vote on them to improve the Apillon platform offering.
For example, they could propose new parachains or services to be integrated and accessible on the Apillon dashboard or new features to improve its UX.
Maybe, they see great potential for platform growth in partnering with another project. Or, they could weigh the priority of backlog proposals to speed up the implementation of essential upgrades over the nice-to-haves.
Apillon welcomes basically any proposal that deals with the Apillon platform and helps perfect the services offered and the overall Web3 development experience.
Who can participate?
The Apillon community gathers people from all walks of Web3 life, and nobody should be left behind in sharing their views. Various groups are welcome to participate in Apillon governance — NCTR token holders and stakers, project ambassadors, and, of course, Web3 developers.
Apillon developers are the primary target audience, frequent platform users, and holders of NCTR token. Their votes are designed to assume greater value, hopefully steering the governance to the best possible outcome for the engineering community and, ultimately, Apillon’s reception on the market.
Three-phase implementation
The Apillon platform is designed to evolve both following an internal road map and community vote. Product governance will roll out gradually, from testing to fully community-decided upgrades.
Phase 1 — Testing and Chaos
In the initial phase, a simple Discord-based voting system will gather all connected users with a registered Apillon account.
The purpose of Phase 1 is to test the Apillon Governance voting protocols, user participation, and incentivization features, and monitor the open discussions on raised proposals. Testing being a key word, the proposals will be drafted solely by the Apillon team.
Phase 2 — Token-Based Vote
In the following stage, the Apillon governance model will introduce NCTR token-based weighted votes, where users with greater amount of staked NCTR tokens assume more voting power.
Phase 2 should thoroughly change the dynamics of proposal discussions and governance outcomes through blockchain-based voting.
Phase 3 — Fully Fledged Governance
Lastly, the blockchain-based voting mechanics will be upgraded by increasing the voting power of Apillon platform users, that is, Web3 developers.
This is not to say that other NCTR token holders, be it ambassadors or stakers, will get excluded from the voting. Simply, developers will be both rewarded for their activity on the platform and given greater responsibility since their vote affects their work more directly.
Power to the Builders
With a product-oriented governance model, Apillon aims to evolve into an optimal Web3 development solution that incorporates essential features and those the engineering community finds valuable.
Join the Apillon Discord community and add your share to the future of Web3.
⧓ About Apillon
The Apillon platform serves as a unified gateway to the Web3 services provided by linked Polkadot parachains. Following the multi-chain vision, Apillon powers the transition of developers to Web3, simplifying its adoption in the real economy, and expanding its versatility as the ecosystem grows. With Apillon, Web3 services are within reach for every developer, regardless of their background and experience with blockchain technology.
Website | Wiki | GitHub | Twitter | Discord | LinkedIn | Reddit
