WPS Working Group FAQ August update

edited August 2018 in Worker Proposals

Frequently Asked Questions

EOS.IO Core WPS Working Group

I just heard about Worker Proposals, what does that even mean?
The EOS.IO system creates inflation of 5% each year. 1% is dedicated to fund the Block Producers who run the chain, while the remaining 4% is paid into the Worker Proposal Fund (WPF). The WPF is intended to be a source of funding for community driven ideas that help grow the ecosystem. The exact definition of what that entails is an exercise we the community have to solve together.
How will the proposal be presented to the public for ratification?
The proposal will consist of several deliverables including a thorough process model of the initial Emergency category process, a change management plan to empower community to amend the system as the mainnet evolves, and a plan to open a referendum through which the EOS token holders can vote to approve a project. Each of these deliverables will be presented in draft form in English at first, with Chinese and Korean translations coming as quickly as we can. On [Insert Agreed Date], the project team will open the WPS referendum which will trigger an on-chain community wide vote to adopt the first stage.
Why are you in charge?
We are not “in charge”. It is an open call for system proposals. Apparently, we are ahead of the game and have been working through the process design with predefined methods and open calls to the community for input.
How are decisions made?
Decisions are not being made. As a group, we are working together to create a proposal. No decision is implemented until the community as a whole votes for or against our proposal. Within our working group, we discuss at length and involve input we receive from community members to ensure that we’ll end up with a proposal that is for the chain, and not imposed on it. In the end, it will be a referendum that brings this, or any system to life.
What about the whales?
What about the whales? We recognise that whales are a part of the EOS.IO ocean and that many in the community are worried about the dangers of plutocracy. Our approach is designed to start small with a set of emergency projects that you approve. We also believe in the collective power of the community to hold bad actors to account, no matter who they are.
Why aren’t you just proposing a whole system at the start?
Designing a Worker Proposal System from the ground up takes time. In the first instance, there are some urgent resources that need funding as soon as we can get community consensus to fund them. These include security testing, testnet operations, code reviews, ECAF setup, Worker Proposal System, bug bounty programs. The next step will be to facilitate a competition for groups to propose governance design systems for each category of works. This is to promote community involvement and diversity of category management in the future.
What type of projects should be approved initially?
For our approach, we believe that the purpose of the Emergency Category is to enable the approval urgent projects and to begin the competition for building the next stage.
The urgent projects include things like:

  • Github repository management
  • Security testing
  • Bug bounty programs
  • WPS oversight committee
  • EOS Core Arbitration Forum (ECAF)

Who decides what WPS proposals get funded?
The token holders decide on which proposals to fund either directly or by voting for the Emergency Committee.
What is the main role of the Emergency Committee? Isn’t that a bit “centralized”?
The main purpose of the Emergency Committee is to pass on approvals to the community for voting. It is to manage the input of ideas and defer projects that do not fit the emergency criteria.
What do you need from the community?
Involved voting, outspoken voices in social media and also volunteers.
What is your greatest concern about the WPS?
System abuse, voter apathy, spam, community fighting and general discord. All of these concerns are great challenges which we do not claim to have the solution for. Our role is to begin the process of helping the community design a future solution or solutions.
How do we stop the inevitable abuses?

  • We design a system that starts small and doesn’t carry too much risk.
  • There is oversight by an Emergency Committee.
  • The Emergency Committee responds to agreed processes and social signals from the community.
  • We include filtering mechanisms to defer projects that are not “emergency” for the next stage when we have approved category governance.
  • We ensure that there is adequate reporting and information provided to the community.

Why don’t we just copy another chain’s system (Bitshares, Dash, etc.) instead of designing a WPS from scratch?
We’ve examined other systems and have tried to pick the best features of each. Each system is a learning experience that improves on the last. With the launch of EOS, it is an opportunity to build on existing knowledge and to create a system that is fit for purpose. We are not proposing to have a fully featured system from the start. Our role is to propose a pathway for the community to take ownership and build the system over time.
How does the WPS system that is being built account for the different communities in EOS and the issues with communication (Chinese, Korean, English)? Are there Chinese or Korean speakers in your group?
We are conscious that the EOS community is comprised of a diverse token holder group, with English, Chinese and Korean being the most common languages used. We plan to design multi-language systems, but for the first version of the minimum viable product we are utilising English. In the meantime we believe that translation will be adequate for submissions and we are already building communication channels for the major language groups. And yes, we have Chinese and Korean native speakers amongst the working group.
How can I make a proposal?
At this stage, the easiest way to start is to sign up to the EOSGO forum. Write up a detailed description of your proposal or idea and share it with the Telegram group. Consider your budget and milestones. When the system is up and ready to receive proposals there will be a form to fill out. The Emergency Committee and volunteers will assist you in making a complete application and then the proposal will be listed for voting.
How do you allow for a free market of ideas?
Anyone can make a proposal. In fact, later this year we will be hosting a competition for category governance design to take your future proposals!
How will it be possible to usefully spend so much money that keeps generating?
The goal is to spend wisely in ways that benefit and enrich the whole community. We don’t see a need to spend it all. In fact, our first proposal for referendum is to move a small fixed amount from the eos.saving account to a worker proposal account. In any case, someone may even suggest a proposal for burning surplus funds in the eos.saving account. We are proposing to start the WPS system with a very contained and reduced risk environment.
Are you proposing that block producers, a committee, or the token holders vote directly on specific projects?
In the first iteration, the Emergency Committee will help to oversee funds being awarded to the projects that were initially approved in the referendum. Also, community members can submit new proposals, but these will be judged by Emergency criteria. The idea is to only fund urgent projects initially, until governance designs can be approved for individual categories.
How can I get involved?
The best way to get involved is to begin by reading through the EOSGO forum and then joining us over at the public Telegram group channel to continue the discussion. We are always looking for volunteers, so make yourself known.

Sign In or Register to comment.