Crown Platforms Agents subsystem
Motivation
In order to build a decentralized registry system where agents are empowered to accept or reject new registrants, the CDGP must be extended. Currently, it only supports proposals for budget distribution. The goal is to create a governance system where different types of proposals about the future of the Crown Platform and its ecosystem can be posted. One of the most important mechanisms which should be a part of the CDGP is assigning roles to different entities (agents empowering).
Requirements
- To apply for an agent the entity has to have an Identity on the network registered and verified.
- The eligible voters can vote for or against agents applications
- The eligible voters are Masternode Operators (and Systemnode Operators?)
- The minimum number of agents on the Crown network at any time is 2
- There is no maximum limit for a number of agents
Acceptance
- Crown users applying to be an agent without being verified will trigger an error
- The Opt In process for Crown users applyling to be an agent once they're verified has to be a clear process
- The Crown users applying to become Agent Candidates must be able to Opt Out of being an Agent Candidate
- Only Crown users that are verified and have Opted In can be eligible to receive votes
- Any Crown wallet owner can acheive Agent status
- Any Crown wallet owner can see the Agent voting pages
- The Crown wallet Agent voting page must be consistent with wallet UI
- The Crown Agent Candidates can only be voted on by Crown users with a masternode or systemnode
- Crown Candidates become Crown Agents when the total amount of Yes votes reaches 20% of the total amount of MN + SNs on the network
- Crown Agents lose their Agent status if the amount of Yes Votes drops below 20% of the total amount of MN + SNs on the network
Links/references
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information