With Polymesh Governance, POLYX holders have the opportunity to influence the direction of the Polymesh blockchain. They can do this by submitting a Polymesh Improvement Proposal (PIP) through Polymesh Governance. Other POLYX holders vote on the proposal, with approved proposals voted on by the Polymesh Governing Council for implementation.
The quality of the proposal can be one of the best predictors of it passing — it will be more easily understood by the POLYX community and Governing Council, and more explicit in implementation. Although a form is provided to proposers with information to include in a proposal, the format is meant to be flexible and therefore, does allow room for error.
Here are a few best practices to consider when creating a proposal:
Questions to ask: Am I providing enough information for POLYX holders and the Governance Council to make a decision?
All proposals must include a title and supporting documentation for consideration by the community. The aim of your proposal title should be that a community member can read the title and understand the changes you’re proposing.
The Proposal details field is available for you to include additional details and supporting documentation through an external link. A few examples:
- If your proposal requires a network upgrade, the URL should point to the code changes in some format. We suggest you submit them as a Github PR.
- If you’re submitting a proposal to add a new Customer Due Diligence (CDD) provider or become a network operator, include links to due diligence or any other supporting documentation relevant to the new provider or operator.
- For other proposals, you can include a URL to the corresponding discussion on a discussion board or Github issue.
The descriptive title and the link to the proposal’s details are stored on-chain to be referenced by POLYX holders and Governing Council members to evaluate the proposal easily and understandably.
Questions to ask: Have I appropriately categorized the proposal? Is the correct function to call selected and the parameters are filled in accurately?
Proposals are categorized by what component of the chain they impact. To help you choose the appropriate category for your proposal, below we’ve outlined the available options and what they mean:
- User Balances: relates to requesting a change to a Polymesh user’s balance by proposing a force transfer of POLYX from one account to another
- User Identity: relates to whether a CDD provider needs to provide authorization for a user to rotate their master key
- Proposal Rules: relates to changing the rules for creating a Polymesh Improvement Proposal, such as the minimum amount of POLYX required to bond, proposal duration, and quorum requirements
- Polymesh Voting: relates to changing the voting thresholds required for a proposal to be considered by the Governing Council
- Staking Parameters: relates to changing aspects of the operation of the chain such as, adding or removing operators and minimum staking requirements
- System Preferences: relates to whether your proposal requires changes to the code which would require a network upgrade to be implemented. These proposals may require more review of the code before being eligible for consideration by the Governing Council
Once you select the component of the chain that you want to propose a change for, the function to call field will update with the appropriate options and you can proceed to fill in the requested details.
Polymesh Governance is available to test through the Polymesh Aldebaran Testnet. Learn more about how to test here. To stay up to speed on new developments and testing opportunities, join the Polymath Beta Testing Community.
Want to join the security token revolution? We’re always looking for high-quality talent. Apply now!