So!
We have a group of people who work on the reference client.
We want to work in such a way in that we are meeting the needs of the majority of stakeholders in CLAM.
There is disagreement on what exactly that work should be - if anything at all.
How do we discover what the majority of stakeholders in CLAM desire?
Proof-Of-Stake has a unique attribute: blocks are found and submitted by the stakeholders of CLAM.
This is different than Proof-Of-Work, where blocks are created by a separate party via computation.
This means that those who find blocks and CLAM stakeholders are the same parties.
Our form of Proof-Of-Working-Stake has a unique attribute: there is no weight.
This results in the chance to stake a block being directly proportional to our stake in the network.
This means that we can verify the share of the network that users possess as blocks are staked.
One block staked == proof of one "unit" of CLAM.
Further, our CLAMspeech system allows users to attach data to their transactions/stakes.
This means that we have a platform for users to communicate their wishes.
Our proof-of-working-stake system, as outlined above, in conjunction with our CLAMspeech system, can allow us to poll the opinion and desires of CLAM stakeholders.
These opinions can be weighted via individual user's stake, utilizing the network stake system itself.
CLAM Petitions
- Shortly, we will release detailed instructions for users to express their opinion on the direction of CLAM development.
- This process will involve attaching designated CLAMspeech messages to staked blocks.
- The protocol/process will allow multiple petitions to occur simultaneously.
- The process will be designed to allow any user to initiate a petition and seek support from other users.
- The development team will initiate and use this process to inform our efforts concerning controversial updates.
We are announcing the topic of the first of these petitions: the process and continuation of "digging" distribution CLAM.
In the coming days, we will announce the timing, choices and assist users in properly submitting "votes" using the process.
The first petition will likely be simplified - but, we see this as an enduring way forward with governance.
This process will allow the entire community to ascertain what petitions have majority support among stakeholders (and is hence likely to succeed given completed code).
The community can then proceed informed and collaborate on getting the code ready to submit to the community.
We invite the community to help us hone the list of choices prior to the start of the voting on this first petition.
Long Live The Great CLAM!