Now that the EOS mainchain is up and running, and we had the first act of governance more or less secured, time to look at another EOS blockchain structure, that has been less talked about, the Worker Proposal Fund!
According to the current setup it will receive an impressive 4% of inflation; at current prices that means a pot of 40M$, not bad, and especially in the first year after the launch this will well be needed for establishing a sound infrastructure for the chain.
So what might EOS national industries look like?
There is now a Worker Proposal Introy by @thomasbcox that gives us a rough idea of how this thing might get rolling:
https://forums.eosgo.io/discussion/1474/worker-proposal-system-wps-charter-released/
Bascially this will follow a two tier structure of Minimal Viable Products (MVP), that will build on the referendum contract (used for the constitution referendeum) and will allow the current group to set up and - more importantly - sufficiently fund, the MVP2 stage, that then will cover the whole project management structure from decision, to planning to testing stages.
The attached charter features a rough timeline:
https://drive.google.com/file/d/1xlRZe9xR3d90f9VcVHaDuZmLU-i5b_33/view
Apparently this will take a while, but with the MVP to be finalised by August 31, we should be able to decide upon the most critical infrastructure after that date.
Of course there are so many things to be decided upon. Just to name a few most important ones:
- Which Projects should be built from the WP Fund, and which should be left to the open market. To me that would be the most critical infrastructure contracts, whatever that could be, maybe official wallets, voting portals, block producer analytics. etc.
- Who can propose projects and what are the criteria?
- How handle proposed projects with overlapping scope?
- Will there be calls for certain projects?
- Who will coordinate projects on the holders side, like financial controlling, progress tracking and quality assurance.
Here is a comprehesive list of questions to be answered:
https://forums.eosgo.io/discussion/1188/what-questions-should-we-be-asking-about-the-worker-proposal-system
I definitely need to look into that after getting comfortable with voting for BPs :) There's a bit of a learning curve involved before getting familiar with the whole EOS ecosystem. Everything should get easier over time when the system matures.
Yes indeed it's so complex and moving so fast, it's incredible, its hard to keep base with just following the news (which are often not officially published but be found in eosgo forums or chats)
BTW, sign yourself (if you haven't yet) for the EOS CryptoWizards :) I have a feeling there will be a lot of fun with the Tournaments!
Good hint, registered, you shoud have given me your referal link, only saw it afterwards, guys in case, here is mine: https://wizards.one/#/?refId=bQUpkr296XukVWYqHTBaRb1Mv4JC2n9nTz5gvSyPRGqxZLi8
And btw.: http://monstereos.io/
That's cool! Just created my first Monster on EOS blockchain! :)))) So happy!
How are you monsters doing? Apparently they are not employee compatible, dying off within 20h, just not managable for me....
Yeah, there's a lot of noise in the background these early days. It will take time for the ones like Scatter (or maybe some other tool) to take the lead offering all functionalities in a safe and user friendly manner. My strategy is not to rush. I did vote for BPs but I may as well now hold for a while and wait for reliable and well verified tools to emerge from this noise.
Not to rush is certainly a good advice, i personally didnt stickt to yet...
You just received a 29.16% upvote from @honestbot, courtesy of @conceptskip!
You got a 30.22% upvote from @cabbage-dealer courtesy of @conceptskip!
Delegate today and earn a 100% share of daily rewards!