Qortal Project

The future of blockchain platforms

User Tools

Site Tools


voting_system_overview

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
voting_system_overview [03/11/2022 17:57] gfactorvoting_system_overview [07/23/2022 07:38] gfactor
Line 12: Line 12:
 Please note: Qortal is ever evolving, as we build this from scratch. Development does not always have room for the community’s involvement, although when possible, it certainly will be. The DevTeam will always be the final decision maker of what is best, as they understand what is technically possible and what will make the most sense. We realize that some folks might not fully grasp this reality, as ideologically we’d all love to be more involved. This is where we must respect and credit the team’s time and track record of building a fair system for all. One that is built with truly decentralized features that meet the foundational goal of egalitarianism. Please note: Qortal is ever evolving, as we build this from scratch. Development does not always have room for the community’s involvement, although when possible, it certainly will be. The DevTeam will always be the final decision maker of what is best, as they understand what is technically possible and what will make the most sense. We realize that some folks might not fully grasp this reality, as ideologically we’d all love to be more involved. This is where we must respect and credit the team’s time and track record of building a fair system for all. One that is built with truly decentralized features that meet the foundational goal of egalitarianism.
  
-Voting will be used to help steer the project’s direction when possible. Rather than leaving everything up to the DevTeam, the community will be able to vote on certain matters with how the DevTeam should allocate their time with options presented to the community. Such as which coins or features to implement next, or certain modifications needing to take place and which options the community thinks are the best ones to pursue. There will NEVER be any voting for sanctioning or censoring as this will never be a possible action by the Dev Team! In the case of the Voting System itself, there does not seem to be any alternative solutions that could be presented as ‘options’ to vote on. This is a small example of how the DevTeam has to make decisions on behalf of the community, and the track record of building a system with genuine intention, deserves credit and trust.+Voting will be used to help steer the project’s direction when possible. Rather than leaving everything up to the DevTeam, the community will be able to vote on certain matters with how the DevTeam should allocate their time with options presented to the community. Such as which coins or features to implement next, or certain modifications needing to take place and which options the community thinks are the best ones to pursue. There will NEVER be any voting for sanctioning or censoring as this will never be a possible action by the DevTeam! In the case of the Voting System itself, there does not seem to be any alternative solutions that could be presented as ‘options’ to vote on. This is a small example of how the DevTeam has to make decisions on behalf of the community, and the track record of building a system with genuine intention, deserves credit and trust.
  
 Voting will also be used for the community to help approve new developers as an admin of the DevTeam. What this means is that we have two types of DevTeam members: 1) anyone can join the team and help develop the codebase who DO NOT have the ability to vote on the 60% approval to push updates to the chain, and 2) DevTeam admins who DO have the ability to vote on the 60% approval to push updates to the chain. The DevTeam would notify the community of the vetted developers being entered into a community vote, then the community will vote to approve the DevTeam admins to push the update with their 60% approval. This update will then assign the admin permission to the vetted dev(s) and it's official. It is extremely important to have this layer of security with these two types of DevTeam members as the DevTeam admins will be the only ones who can vote for a 60% approval to push updates. This creates a way for the community to have a say in who becomes a DevTeam admin, and the DevTeam admins keep the rest of the DevTeam in check as DevTeam admins are the only devs who can push the 60% approval updates to the chain. Voting will also be used for the community to help approve new developers as an admin of the DevTeam. What this means is that we have two types of DevTeam members: 1) anyone can join the team and help develop the codebase who DO NOT have the ability to vote on the 60% approval to push updates to the chain, and 2) DevTeam admins who DO have the ability to vote on the 60% approval to push updates to the chain. The DevTeam would notify the community of the vetted developers being entered into a community vote, then the community will vote to approve the DevTeam admins to push the update with their 60% approval. This update will then assign the admin permission to the vetted dev(s) and it's official. It is extremely important to have this layer of security with these two types of DevTeam members as the DevTeam admins will be the only ones who can vote for a 60% approval to push updates. This creates a way for the community to have a say in who becomes a DevTeam admin, and the DevTeam admins keep the rest of the DevTeam in check as DevTeam admins are the only devs who can push the 60% approval updates to the chain.
voting_system_overview.txt · Last modified: 04/29/2023 18:35 by gfactor