<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by David Margulies on Medium]]></title>
        <description><![CDATA[Stories by David Margulies on Medium]]></description>
        <link>https://medium.com/@davidmargulies_27872?source=rss-ab30033c6ab------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XvIHhkXbueYTD1ibLqkyJQ.jpeg</url>
            <title>Stories by David Margulies on Medium</title>
            <link>https://medium.com/@davidmargulies_27872?source=rss-ab30033c6ab------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:38:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@davidmargulies_27872/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[CDF Referendum: Post Launch Q&A]]></title>
            <link>https://medium.com/wps-working-group-eos/cdf-referendum-post-launch-q-a-d759c9911a5d?source=rss-ab30033c6ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/d759c9911a5d</guid>
            <category><![CDATA[worker-proposal-system]]></category>
            <category><![CDATA[wp]]></category>
            <category><![CDATA[cdf]]></category>
            <category><![CDATA[eos]]></category>
            <dc:creator><![CDATA[David Margulies]]></dc:creator>
            <pubDate>Thu, 14 Feb 2019 15:12:10 GMT</pubDate>
            <atom:updated>2019-02-17T15:02:15.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f3zOIAsw06kzdHeo9z5KwA.jpeg" /><figcaption>Focus on the Rocket.</figcaption></figure><h3>The CDF Proposal launched on January 12th and there has been a high volume of discussion in Telegram about the features outlined.</h3><p>While we cannot make changes to a proposal that is currently up for vote, we can answer the main questions or objections that have been voiced in an effort to ameliorate any fears. These are mainly my answers as a team member and I stand by them.</p><ul><li>The full text of the proposal can be found <a href="https://medium.com/wps-working-group-eos/eos-commons-development-fund-program-78174b76cc44">here.</a></li><li>The on-chain version of the proposal for voting is <a href="https://eostitan.com/proposals?proposal=wps&amp;created_at=2019-01-12T15%3A47%3A52.000Z&amp;tab=0">here</a>.</li><li>If you want to comment or join the discussion please visit the <a href="https://t.me/eosio_wps">Telegram group</a>.</li></ul><ol><li><strong>Why is the Emergency Committee getting 1MM EOS?</strong></li></ol><p>The EmCom is not “getting” 1 million tokens. The EmCom is being tasked with acting as stewards for 1 million tokens. This is an important distinction. The community must vote and so direct how and if the tokens are to be spent. The EmCom has no authority to transfer the tokens to another account without community vote.</p><p>The one million is much larger than the budget posted for the EmCom and the Portal because the fund is not just there to fund EmCom and portal; it is there to fund the first proposals that the community approves. It isn’t up to EmCom to spend the money — it’s up to the community to direct how the EmCom disperses it. 1MM represents the maximum spend that the community can possibly use during the period before the categories are established. The figure is a best guess at the most the community could possibly spend, keeping in mind that we were budgeting for “unknown unknowns”. It’s just a matter of “better to have and not need than need and not have.”</p><p>The entire amount could be needed, but probably won’t. The balance unused is burned or returned. Three different things can trigger the burn or return of unused balance: the Successful establishment of Categories, OR removal by community, OR Six months of operations. (Six months is the life of the EmCom with one caveat: should there be unfinished business, the structure is flexible enough to allow the term to extend slightly. However, this would require community approval. All other triggers stay in place.)</p><p>If the community did spend all of the money and did not want to replenish the the pot for EmCom’s duties that would also mark an end, albeit there would be nothing to dispose of.</p><p><strong>2. Why not split the proposal into separate proposals? (i.e. a burn proposal, a Bootstrap Team proposal, a portal proposal, etc.)</strong></p><p>The legislation that we drafted is intended as a cohesive whole with interlocking parts. If some parts are passed and not others, the end result would not be viable.</p><ul><li>EmCom — this is required to manage the competition and to create the best practices precedents that will guide future CDF efforts, or other attempts to access the .saving account for stakeholder driven development.</li><li>Portal — this is required for voting on chain and communication concerning the proposals, forums, on-chain reports from the various governance structures, tally system for on-chain voting.</li><li>Funding — this should be self evident but without funding for operations and for community approved proposals nothing happens.</li><li>Competition &amp; Categories — this is the ultimate goal: an entirely community designed and driven set of categories, limited in funding and scope, to allow for the greatest variety of governance options so EOS as a whole can figure out what works best, while limiting theft, abuse, or waste.</li><li>Eosio.saving fund management and token retirement — there are 2 main reasons for including a “burn”:<br>* First, there is a large, vocal contingent who fear that the CDF will encourage rampant waste. By taking the funds out of the equation from the start, we hoped to reduce fears; and,<br>* Second, changing inflation is a matter of code and should more properly be handled by a separate referendum, but since we don’t know yet if 5% is truly high or not, shutting the flow off is a very drastic measure. We felt that the entire community is best served if the CDF sets a precedent of taking the minimum needed and safely removing the remainder from play.</li></ul><p><strong>3. Why only 6 months to create the other governance structure?</strong></p><p>Granted, in hindsight 6 months can appear too short. There were a few reasons for picking this range though:</p><ul><li>The EmCom will be putting in a lot of hours for what is essentially unpaid, high consequence, high visibility work. During their tenure they have to forego any business opportunities that would have the appearance of conflict of interest. Asking them to stay at this longer would be unfair;</li><li>If the community wants to build category proposals and vote on them, 6 months should be adequate. If the community doesn’t care or won’t do the work, more time won’t improve the situation;</li><li>This is a prototype body asking for community trust. Limiting the term to the minimum needed to do the job was the best argument that could be made against the more unhinged attacks of “power grab”.</li></ul><p><strong>4. Why have an unelected group of 7 form the EmCom, rather than hold an election?</strong></p><p>First of all, this will not be an unelected team. The community voting for the Referendum elects them. Secondly, this is a bootstrapping enterprise; there are no mechanisms in place for an election. Any such election mechanisms would have to be designed and built, and then configured into wallets and portals. Who should do this work? The truth is anyone who did that work would then be challenged because they, in turn, had not been elected. Such is the nature of bootstrap endeavors. To avoid this tangle of recursive complaint, the slate of nominees have been made public, their EmCom powers are negligible, and if elected will serve only long enough to replace themselves by elected governance structures.</p><p>Overall, a lot of questions have been focused on the EmCom. This is a mistake. The EmCom is only the temporary gantry required to launch the CDF. Focus on the rocket.</p><p><strong>5. What protection will be in place to ensure that the members of EmCom won’t run off with any of the tokens?</strong></p><p>Owner permission is designated to eosio@active and the active permission set up as a 4 of 7 multisig, with keys provided by the 7 members of the EmCom. There will be a 48 hour delay built in to transactions. Since the EmCom only oversees the spend directed by the community, an onchain tally of a successful community vote precedes every 4/7 multisig signature. BPs can confirm the tally and block or delay any suspicious assignment of funds.</p><p>There have been some critics who have responded to this with “yeah but the EmCom could still steal and the BPs might not be motivated to block it.” it is very hard to answer this — anyone on the street could hit people in the head and steal wallets, bank tellers could stuff their pockets and leave for lunch, parking attendants could sell parked cars for parts. The way this is all prevented is by making it hard to steal and moreover making it very hard to get away with.</p><p><strong>6. How much do the EmCom get paid for this?</strong></p><p>The EmCom representatives each receive 1 EOS per meeting for roughly 16hrs of work each, per month. In other words 1 token = between 1 and 16 manhours — very good value to EOS. This is an honorarium and is a placeholder to signify that this is a group of people volunteering their time and effort for the betterment of the entire EOS ecosystem.</p><p><strong>7. Why can’t the BPs just handle the .saving account?</strong></p><p>A stable and healthy government requires checks and balances. Today there are no effective balances to BP power. Giving the BPs access and approval over the entire inflation fund almost guarantees fraud, waste, and abuse — not because every BP would be unethical but because there is nothing to stop all projects that get approved from originating within the BPs themselves. The BPs are for profit businesses but spending a Common Pool resource should benefit everyone. The Incentives just do not align even with offering BPs every benefit of doubt. And given that there are already strong suspicions and indications of an unassailable cartel existing in the BP ranks, how could the community ever regain control?</p><p><strong>8. What happens if this proposal is rejected?</strong></p><p>Nothing happens. The way a proper referendum is supposed to be created, as far as i understand, is that a “no” vote equals the status quo. I suppose those from the original workgroup who were not completely demotivated would create an exit report of learnings. I would like to believe that I would try to help future endeavors by other people.</p><p><strong>9. Given we have the benefit of hindsight here, what would the proposer like to change prior to implementation if approved.</strong></p><p>It would be very good if some of the experts could advise on tightening up the MSIG permissions. However, there is very little leeway to change anything that has already been detailed because it is on-chain and currently being voted on. That said though it should be recognized that the Portal budget and the EmCom budget are very conservative and likely less will be spent than is budgeted for now.</p><p><strong>10. What is the proposed method of “the community” proposing and approving governance structures.</strong></p><p>The honest answer is no one knows the process yet because we haven’t created it. Creating that process is one of the major duties of the EmCom. There can be no definitive answer yet, but the process will likely have a flow along the lines of</p><ol><li>Party A has an Idea, and they bring it to the various fora and the EmCom and other people informally for feedback.</li><li>Party A brings the beta draft of their idea to EmCom and the proposal is jointly reviewed with Party A and EmCom according to the ideas on the third page of the outlined “<a href="http://bit.ly/EmCom_assessment">Proposal Assessment Overview</a>” from the referendum.</li><li>Party A makes adjustments recommended by EmCom, <em>to the extent Party A is willing</em>, and the proposal is posted to the Portal with comments from EmCom and introduction from Party A.</li><li>Voting.</li></ol><p><strong>11. There have been some comments — rather than questions — that are, not statements about the proposal, but statements about the speaker’s beliefs:</strong></p><p><em>A. Inflation should be lowered.</em></p><p>This is an argument that is beyond the remit of the CDF. However, the CDF was created in such a way that the de facto inflation is reduced to 2% at most, unless the community decides it should be higher.</p><p><em>B. Development should be privately funded/voluntarily funded.</em></p><p>Nothing is stopping anyone from running such a system in parallel to the CDF. in fact not even a referendum would be required to launch this. Anyone who wants this should go for it. The CDF is a first pass attempt to build the development program that inflation has been set aside for.</p><p><em>C. Committees or bureaucracies are by default bad.</em></p><p>It is harder for a committee with named public figures to be improperly influenced without being caught than for a whale to run a campaign to manipulate voting. A committee structure is no more intrusive than a proxy; it allows people to focus on the details of individual projects in a way that the community cannot. And, counterintuitively, committees scale better than community votes on every matter because voter fatigue is less likely.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d759c9911a5d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wps-working-group-eos/cdf-referendum-post-launch-q-a-d759c9911a5d">CDF Referendum: Post Launch Q&amp;A</a> was originally published in <a href="https://medium.com/wps-working-group-eos">EOS Worker Proposals</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Suggested CDF EmCom Proposal Approval Flow]]></title>
            <link>https://medium.com/wps-working-group-eos/suggested-cdf-emcom-proposal-approval-flow-59a1fad72153?source=rss-ab30033c6ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/59a1fad72153</guid>
            <category><![CDATA[eos]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[commons]]></category>
            <category><![CDATA[wp]]></category>
            <category><![CDATA[eos-cdf]]></category>
            <dc:creator><![CDATA[David Margulies]]></dc:creator>
            <pubDate>Sat, 12 Jan 2019 07:32:53 GMT</pubDate>
            <atom:updated>2019-01-12T07:32:53.772Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*e4_b03FGy0ZAhf-1" /><figcaption>Canal Lock system employing thresholds</figcaption></figure><p>After a proposal has been vetted and the EmCom is prepared to recommend it, the proposal will be placed before the community for approval. This approval process will not, and should not in most cases, be as difficult as a referendum.</p><p>Key features required for a successful approval process:</p><ul><li>Transparency;</li><li>High cost for manipulation;</li><li>Reflection of community will;</li><li>Speed; and,</li><li>Reduction of voter apathy or burn-out.</li></ul><h3>Approval Thresholds:</h3><p>The best solution found so far is voting by staked tokens. Voting will be on chain but to meet the features listed above, the CDF EmCom will establish voting thresholds based on project size. The goal is to balance practical levels of voter responses with high enough barriers to manipulation — while at the same time reducing voter burnout. This will be an iterative and incremental process. (NB, the exact levels cannot be decided in a vacuum; there is a need to get real data first.)</p><p>The EmCom is considering the following table to grow from:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/981/1*V_-6S2pLzWShXhKYD58rtg.png" /></figure><p>[1] Other proposals by proposing party or related parties should be examined to make certain there is not a case of “structuring”.</p><p>[2] i.e., 50.000001/49.999999</p><p>[3] There is room for possible abuse, obviously. These cases should be used sparingly and for very simple, one-off projects.</p><p>[4] i.e., 55/45</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59a1fad72153" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wps-working-group-eos/suggested-cdf-emcom-proposal-approval-flow-59a1fad72153">Suggested CDF EmCom Proposal Approval Flow</a> was originally published in <a href="https://medium.com/wps-working-group-eos">EOS Worker Proposals</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EOS COMMONS DEVELOPMENT FUND PROGRAM]]></title>
            <link>https://medium.com/wps-working-group-eos/eos-commons-development-fund-program-78174b76cc44?source=rss-ab30033c6ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/78174b76cc44</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[wp]]></category>
            <category><![CDATA[worker-proposal-system]]></category>
            <category><![CDATA[eos]]></category>
            <dc:creator><![CDATA[David Margulies]]></dc:creator>
            <pubDate>Wed, 02 Jan 2019 14:25:09 GMT</pubDate>
            <atom:updated>2019-01-14T07:51:26.877Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*52SoMoKjWDwnti33Sz6soA.jpeg" /></figure><p><em>(AKA PLATFORM DEVELOPMENT FUND, AKA WORKER PROPOSAL SYSTEM, AKA WPS)</em></p><h3>Proposers</h3><p>Anand, Gautam<br> Buck, Justin<br> Espinoza, Branden<br> Karaivanov, Todor<br> Kauffman, Josh<br> Lee Kiho <br> Kim Naeun<br> Ma Larry<br> Mao Yifeng<br> Margulies, David<br> Pahalahti, Samuli<br> Pollard, Chris<br> Seo, Leo<br> Shi, Ricky</p><h3>Describe Initiative / 提案描述 / 제안 요약</h3><p>This proposal is to fund a 6-month bootstrap stage EOS Commons Development Fund System. / 本提案旨在资助为期6个月的启动阶段的EOS公共发展基金系统。/ 이 제안은 6개월간의 EOS 공동 개발 펀드 시스템 부트스트랩 단계를 위한 것입니다.</p><p>Our goal is to create a mechanism to fund a portion of the innovation and advancement of the EOS network, and do so in a transparent manner, utilizing community-directed funds, while addressing and reducing the risks of systemic fraud. / 本提案旨在资助为期6个月的启动阶段的EOS公共发展基金系统。我们的目标是建立一个机制，以透明的方式资助EOS网络的创新和发展，利用社区导向的资金，同时消除系统性欺诈的风险。/ 우리의 목표는 EOS 네트워크의 혁신과 진보를 위한 펀드를 제공하는 메커니즘을 만드는 것입니다. 그리고 이를 위한 투명한 방법과 커뮤니티 규제 하의 펀드 운용을 통해 체계적인 사기를 대처하고 미연에 방지하는 것입니다.</p><p>The Official language of this Referendum will be English: all efforts have been made to translate accurately to other languages for ease of understanding, but English is the prevailing language in case of dispute. / 本次公投的官方语言将是英语:为了方便理解，我们已尽力准确地翻译成其他语言，但在发生争议时，以英语为主。/ 국민 투표의 공식 언어는 영어가 될 것입니다. 물론 쉬운 이해를 돕기 위한 노력으로, 다른 언어로의 명확한 번역이 이루어질 것이지만, 주요 언어는 영어일 예정입니다.</p><ul><li>中文译本: <a href="https://medium.com/wps-working-group-eos/eos%E5%85%AC%E5%85%B1%E5%8F%91%E5%B1%95%E5%9F%BA%E9%87%91-9ffc71d96f9a">https://medium.com/wps-working-group-eos/eos%E5%85%AC%E5%85%B1%E5%8F%91%E5%B1%95%E5%9F%BA%E9%87%91-9ffc71d96f9a</a></li><li>한국어 번역판: <a href="https://medium.com/wps-working-group-eos/be0a50dd9d59">https://medium.com/wps-working-group-eos/be0a50dd9d59</a></li><li>As other language translations become available they will be shared on <a href="https://medium.com/wps-working-group-eos">https://medium.com/wps-working-group-eos</a>.</li></ul><h3>State Question / 官方问题 / 공식 질문</h3><p>Should the EOS mainnet establish the EOS Commons Development Program as outlined in this referendum? / EOS主网是否应该像公投中描述的那样建立EOS公共发展计划? / EOS 메인넷에 이번 국민 투표로 제시한 EOS 공동 개발 펀드 프로그램을 설립해야 할까요?</p><p>· Yes, I vote to establish the EOS Commons Development Program. / 赞成，我投票赞成建立EOS公共发展计划。/ 네. 저는 EOS 공동 개발 펀드 프로그램 설립에 찬성합니다.</p><p>· No, I vote to reject the EOS Commons Development Program. / 反对，我投票反对建立EOS公共发展计划。/ 아니오. 저는 EOS 공동 개발 펀드 프로그램 설립에 반대합니다.</p><h3>Interpretive Statement (What a Yes Vote Will Do)</h3><p>The proposal includes:</p><h4>1. Transfer of Funds.</h4><p>An amount of 1 million EOS tokens is transferred by the top 21 Block Producers from the eosio.saving account to a newly created eosio.wps account. The purpose of this amount is to fund the EOS Commons Development Program activities for six months. [See Section 7 below for more details on eosio.saving.]</p><h4>2. Initial Allocation</h4><p>The first allocation of funding will be immediate and will include funding for</p><ul><li>Emergency Committee Operations</li><li>EOS Commons Development Program portal development and management</li><li>The balance of the initial allocation of 1MM tokens will be held under custody of the Emergency Committee, to be disbursed if, and only if, the community has approved other proposals for funding by the EOS Commons Development Program (as outlined in Article XI of the Constitution).</li></ul><h4>3. Emergency Committee Operation.</h4><p>The Emergency Committee is created and formed with the purpose to filter and oversee proposals that go to community vote, oversee the progress of proposals, oversee the use of funds, report Emergency Committee findings back to the community periodically, and assist in the preparation of governance proposals for EOS Commons Development Program Categories.</p><ul><li>Requested EOS on 20190102: ($68,943.72/$2.72) + 84 = 25,430.9559</li><li>Slate of nominees: <a href="http://bit.ly/slateofnominees">http://bit.ly/slateofnominees</a></li></ul><p>Updated Budget and proposal links:</p><ul><li>(proposal) <a href="http://bit.ly/committee_proposal">http://bit.ly/committee_proposal</a></li><li>(budget) <a href="http://bit.ly/committee_budget">http://bit.ly/committee_budget</a></li></ul><p>Emergency Committee Emergency Proposal Assessment Overview: <a href="http://bit.ly/EmCom_assessment">http://bit.ly/EmCom_assessment</a></p><h4>4. EOS Commons Development Program Portal Development and Management.</h4><p>Portal Development to support the growth of EOS Ecosystem by developing the software and platform for the community to review, discuss, select, fund, and hold accountable projects proposed by community members to benefit EOS; includes the following:</p><ul><li>Smart contracts for registration, submission, proposal review, and voting.</li><li>Web platform for registration, submission, forum and voting.</li><li>Software that incorporates the needs of new categories as they come online.</li><li>Secure infrastructure to deploy the platform.</li></ul><p>Requested EOS on 20190102: ($378,420.00/$2.72)+750 = 139,875</p><p>Updated Budget and proposal links:</p><ul><li>(proposal) <a href="http://bit.ly/portalDev_proposal">http://bit.ly/portalDev_proposal</a></li><li>(budget) <a href="http://bit.ly/portalDev_budget">http://bit.ly/portalDev_budget</a></li></ul><p>Preliminary github <a href="http://bit.ly/github_draft">http://bit.ly/github_draft</a></p><h4>5. Recognition of EOS Commons Development Program Categories</h4><p>The following EOS Commons Development Program categories are established and recognised for future development to allow for the greatest variety of governance options to figure out what works best, while limiting scope for abuse or failure:</p><ul><li><strong>Oversight</strong> — intended for portal maintenance, quality control, and oversight of other categories, as well as supporting any proposals that go through direct referenda instead of one of the EOS Commons Development Program Categories.</li><li><strong>Infrastructure</strong> — for supporting the underlying code base of the blockchain. Examples include security audits, bug patches, and code repository maintenance</li><li><strong>Community</strong> — includes meetups, educational content and platforms, public relations, lawyers, advocates and lobbyists.</li><li><strong>Development</strong> — for supporting developers and ideas.</li><li><strong>Miscellaneous</strong> — for any proposal which may not fit directly into any of the other categories.</li></ul><h4>6. Open Call for Governance Design Proposals for Individual Categories.</h4><p>The Emergency Committee will manage a competition for individual category governance structure designs to allow for experimentation with governance without risk to the whole ecosystem:</p><ul><li>The governance structure for each category is up to worker proposals submitted by the community.</li><li>Winning Designs are those chosen by community vote.</li><li>As each category is approved by the community, the category in question becomes active.</li><li>To become an activated category, the winning submission will be chosen as the one with the highest participation of voting tokens, with no less than 5% of total currency supply, and must maintain no less than 55% Yes votes of the total voting supply, maintained for no less than 15 consecutive days within a period of 60 days.</li><li>Each active category will be limited to its own financial boundaries,(i.e., 10% of eosio.saving) to limit abuse and waste, and to allow room for future growth if and when token holders decide on it. (See Section 7.)</li><li>When a category goes live, the Emergency Committee surrenders control over relevant proposals. Over time, the Emergency Committee ceases to exist as its duties are absorbed.</li></ul><h4>7. Retire the Remaining Balance of eosio.saving.</h4><p>Until such time as there is community confidence in the various government structures, we propose a recurring retirement of all funds in eosio.saving not allocated to eosio.wps:</p><ul><li>On day 1, after the initial 1 million EOS tokens are moved to the eosio.wps account:</li><li>the remainder in eosio.saving will be retired; and,</li><li>eosio.saving will continue being retired monthly, as it accumulates.</li><li>Once the Categories have been properly established:</li><li>10% of the tokens flowing into eosio.saving <em>per approved Category</em> will be distributed into eosio.wps.</li><li>Full description: <a href="http://bit.ly/eosiosaving_burn">http://bit.ly/eosiosaving_burn</a> (NB, external document reflects a previous intention to bundle ECAF and Mainnet Repository Maintenance. This coupling is no longer planned. However for transparency we will not edit already published documents unless required for accuracy.)</li></ul><h3>Block Producer Instructions</h3><ul><li>Create a multisig proposal to create an account named eosio.wps with 10 EOS staked for Network bandwidth and 100 EOS staked for CPU bandwidth and 1500000 bytes of RAM</li><li>The eosio.wps account structure should be crafted with owner permission designated to eosio@active and the active permission set up as a 4 of 7 multisig, with keys provided by the 7 members of the EmCom.</li><li>Create a multisig proposal to transfer 1 million EOS from eosio.saving to eosio.wps</li><li>Create a multisig proposal to retire the remaining balance of eosio.saving after the transfer of 1 million tokens has been executed</li><li>Every 30 days following, a new multisig proposal shall be put forward by the EmCom to retire the unallocated funds within eosio.saving</li></ul><h3>Arguments</h3><p><strong>Summary Arguments In Favor</strong></p><ul><li>EOS requires support and development and funds have been set aside for this purpose.</li><li>CDF is a safe and secure way to bootstrap this support system.</li><li>Public goods should be funded by the commons.</li><li>Decentralization and separation of powers requires an independent CDF.</li></ul><p><strong>Summary Arguments Against</strong></p><ul><li>EOS Inflation is too high at 5%; no development or support is needed so inflation should be reduced to BP rewards.</li><li>A Commons Development Fund to handle development is a central bureaucracy; instead the money and duties should be trusted to the Block Producers.</li><li>DPoS does not work; individuals who hold the most tokens have the greatest voting power. Whales would use a fund like this to just vote themselves money.</li></ul><h4>Arguments In Favor</h4><p>Public Goods must be supported by the community. As explained in the EOSIO whitepaper [<a href="http://bit.ly/eosio_whitepaper">http://bit.ly/eosio_whitepaper</a>], by using a portion of the 4% inflation set aside to fund necessary projects, we can increase and improve the utility of EOS and its overall adoption. This referendum is intended to do the minimum needed to bootstrap the EOS Commons Development Fund. We acknowledge that there is a risk of the CDF getting abused by greedy whales for their own projects. That’s why we start with a small percentage of the available funds and burn the rest. If it turns out that the CDF can’t be used effectively for the benefit of the whole community, only a small amount of money is lost, but we will have learned possible abuse vectors and would be able to account for those in future iterations of the system.</p><p>There are systemic irritations on EOS that we could fix or improve, desired features we could add to EOS, and public dApps that would greatly increase system utility and attract new demand. The problem is that often such things benefit everyone, but not so much that anyone alone would have incentive to create them. In such cases, a collective will must create a common good.</p><p>Block.One wrote about a number of key features in the EOSIO whitepaper: arbitration, account recovery, Inter-Blockchain Communication, distributed storage, referenda tools, to name a few. Due to internal decisions made by Block.One, these tools have fallen to the community to develop. It seems safest to look to Block.One for ideas and to look to ourselves and the CDF for execution.</p><p>We cannot expect block producers or volunteers to take over the role of support, either. We must decentralize the system and decrease reliance on Block Producers. Letting the BPs take more responsibility for the development would consolidate their already very powerful role. Another option, volunteerism, is not a sustainable model for long-term growth. We must enact the provisions for a Commons Development Fund as alluded to in the EOSIO whitepaper. The scope of projects that the community has vocalized a desire for are far-reaching and are too much for single teams to shoulder the cost of. Further, many of these core features are non-monetizable by design. Thus a community-funded approach is the only path forward to see them come to fruition.</p><p>Most importantly, if the EOS community desires to have independent governance and/or journalism, it should look into enabling independent funding for it. Any other known methods of funding expose the system to outside influence. The CDF can provide truly independent funding for these critical pieces of the ecosystem.</p><h4>Rebuttal</h4><p>Block Producers have done a remarkable job working together to roll out dozens of code patches. Anything beyond these changes needs to come from referendum. To put the power of ‘development and new features’ in the hands of a CDF instead of token holders goes against the spirit of DPOS.</p><p>Block producers are paid for their positions and they should be shouldering the cost of these communal goods. They will then be able to advertise that they produced those goods to campaign for increased votes. There will also be free market solutions that arise for many of the problems we face. Someone can come up with a way to monetize the tools we seek, and charge a per-use fee rather than having every token holder’s assets lose value.</p><p>The communal funds of the network should not be used as a slush fund for running experiments. There has not been enough evidence to show that a system like this would work as intended. Any failed attempts, over-funded projects, or tokens that end up being used to build out something that the entire community does not directly benefit from comes at a price to every single token holder. A proper system would need to ensure that every token spent would return more value. The plan for how the group will use the money to facilitate the building of these tools is unclear in the proposal. More details are needed about the expected roadmap for this project.</p><h4>Arguments Against</h4><p>Using the eosio.saving to fund “Worker Proposals designed to benefit the community” [<a href="http://bit.ly/eosio_whitepaper">http://bit.ly/eosio_whitepaper</a>] via an EOS Commons Development Fund Program will devalue all our token holdings through inflation. Inflation on the EOS mainnet is hard capped at 5%. However, only 1% is actually released into circulation as block producer rewards, while the other 4% is held in eosio.saving. Even though this account was created to fund initiatives like a Commons Development Fund / Worker Proposal System, it has really served to lock-down 80% of all inflation, preventing its circulation and therefore preventing EOS token price from decreasing more than it already has. Enabling the community to pull from that pool would decrease token value through inflation.</p><p>What EOS needs right now is more users, so funds can be much better spent creating free accounts for new users and establishing URI. When the number of token holders increases, demand for tokens will rise and outside businesses will be attracted to enter the system and invest privately in development.</p><p>Further, creating a body to handle the development funds and decide where to direct them is tantamount to creating a central bureaucracy. EOS is a decentralized open-source project and The community is full of open-source builders. EOS tools are being built and offered for free to the community. Further, dozens of base code changes have been signed off by BPs; the BPs are handling network maintenance well, as a part of their normal job description. Nobody is getting paid extra for these things, yet they are all happening. To suggest that the community needs some central body to organize and fund efforts to build and maintain a healthy network, is an insult to the EOS community.</p><p>Given the nature of DPoS, individuals who hold or control the greatest number of tokens have the greatest voting power. These whales would use a fund like this to just vote themselves money. Other people will scam the system by not doing the work they promise to do or by creating frivolous boondoggles. The structure of how the funds would be handled, and what they would be used for, need to be more transparent.</p><h4>Rebuttal</h4><p>Currently, the eosio.saving account holds in excess of 20,500,000 tokens and increases at a rate of over 100,000 tokens per day. However, the tokens need not be in actual circulation to depress EOS token value; to individuals concerned about the threat of inflation, the existence of those tokens at all poses an ongoing risk to the EOS token value. However, the EOS Commons Development Fund Program has been set up so that the majority of tokens in eosio.saving will be burned — and this includes new inflation flowing into the account. [see section 7] This action forever removes the threat of those tokens depreciating the token value.</p><p>Tokens only become available when the token holders decide that the benefit to the system is clear. Token holders do this by approving a Category, allowing 10% of the funds held in eosio.saving to be used to grow the EOS ecosystem. And, even when all five categories are up and running, they can access only a total of 50% of eosio.saving. Since that account equals 5% inflation less BP rewards, total inflation would be effectively capped at 3% (1% BPs + 2% CDF) — 2% less than now.</p><p>This is not to say that the 2% potential spending by the CDF would be empty of value. The structure is designed to allow the community to direct spending to improve the overall value of the EOS Ecosystem, which will counteract inflation by increasing utility and demand. Moreover, the category design [See Section 6] is such that it is costly for a whale to hijack a proposal, limits the funds available to steal or waste, and any abuse that is detected is easy to shut down. Importantly, large projects require tranche payments and the achievement of milestones, so even well-intentioned projects that fail to deliver could have their funding stopped if necessary.</p><p>When the technology catches up, URI and similar large scale projects can easily be built out and funded by the architecture put in place by and for the CDF. For now though, the system laid out is a temporary structure intended to bootstrap using the smallest amount of funds. Ultimate oversight duties fall on the community to maintain as is proper for the Blockchain; as it should be in the blockchain world. The major design considerations have been to look to the existing open source and blockchain programs and borrow what works, build modular components for flexibility and fungibility, and support the hundreds of developers already laboring to build EOS. The fact that volunteers have been doing more than is reasonable to expect of them is the very reason that they should be supported in their efforts by a functioning Development Fund.</p><p>It is important to remember that the community can replace any of the Emergency Committee members — or any of the Category Governance Structures — at any time. This is just like the idea behind Block Producer elections; we trust the community can elect good actors through the DPoS consensus method that EOS is built upon. Just as it’s been proven many times in the real world, delegation, when done well, correlates with efficiency.</p><h3>Supporting Documentation</h3><ul><li>GitHub <a href="https://github.com/EOS-BP-Developers/wps-portal">https://github.com/EOS-BP-Developers/wps-portal</a> and <a href="https://github.com/EOS-BP-Developers/wps-backend">https://github.com/EOS-BP-Developers/wps-backend</a></li><li>GitHub — latest commit 5ea8f491efa11fb07acc8d51eff04fbcdef69a69 (portal) and 053fb79b86d9909fa160b84a4ce7f234a4932fed (backend)</li><li>Hash of intent / Ricardians latest commit d120e212bdcd03039037a0a0c76daca5c9c3a350</li><li>Ricardian Contracts: <a href="https://github.com/EOS-BP-Developers/wps-backend/tree/master/contracts/eosio.wps/abi">https://github.com/EOS-BP-Developers/wps-backend/tree/master/contracts/eosio.wps/abi</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78174b76cc44" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wps-working-group-eos/eos-commons-development-fund-program-78174b76cc44">EOS COMMONS DEVELOPMENT FUND PROGRAM</a> was originally published in <a href="https://medium.com/wps-working-group-eos">EOS Worker Proposals</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feedback from EOS Nation talk: WPS Emergency Committee]]></title>
            <link>https://medium.com/wps-working-group-eos/feedback-from-eos-nation-talk-wps-emergency-committee-d0f22df62ff9?source=rss-ab30033c6ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0f22df62ff9</guid>
            <category><![CDATA[worker-proposal-system]]></category>
            <category><![CDATA[eos]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[David Margulies]]></dc:creator>
            <pubDate>Thu, 18 Oct 2018 06:44:53 GMT</pubDate>
            <atom:updated>2018-10-18T12:49:30.406Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*AknE8h3zT26JQAiR_G-nHA.jpeg" /></figure><p>Hello Everyone,</p><p>Based on community feedback received by <a href="https://t.me/YBNorml">Yves La Rose</a> of <a href="http://eosnation.io/">EOS Nation</a> concerning our video interview on <a href="https://youtu.be/rDnnCgevdk4">8 September 2018</a>, I thought I should take some time to assuage and reassure.</p><blockquote><strong>The Emergency Committee budget is poorly defined.</strong></blockquote><p>Yes, it is. In part that was by design and a conscious decision. Lacking real data and experience it seemed best to give reasonable but rough figures to start and to refine as we get real numbers. Please remember we will publish our spending on a monthly basis and return all unused budget at the end of the Committee’s life, for either re-use or burning.</p><blockquote><strong>The Emergency Committee needs clearer roles and responsibilities.</strong></blockquote><p>This one is a head scratcher or me. No one has done this before so we are going to be setting many of the guidelines and best practices as situations arise. There are so many unknown unknowns right now. That said though, we have published fairly extensive documentation. If you click through the links <a href="https://medium.com/wps-working-group-eos/budgets-open-for-review-eos-wps-first-referendum-2d2586c2d89f">HERE</a> for the Emergency Committee <a href="https://drive.google.com/open?id=1PkBw2ckFodBpUIl6dMlp7Ya1k-kvc_I_">Proposal</a>, you will see at the bottom links to both the <a href="https://drive.google.com/file/d/1UEvmUjwSql-AGJ8PHkMp-meENDEieBz8/view?usp=sharing">Emergency Committee Charter</a> and the duties for <a href="https://drive.google.com/file/d/1fRRX3mF96ypCiRS524VdM15TsjtsjEJA/view?usp=sharing">Administrative Assistants</a>. There is probably too much info there!</p><blockquote><strong>It is unclear whether the honorarium is to be paid in EOS or some other coin.</strong></blockquote><p>Really? We are discussing EOS; of course it is to be paid in EOS.</p><blockquote><strong>Some people foresee the Emergency Committee becoming the Oversight Committee (if the Oversight category is eventually run by committee.)</strong></blockquote><p>The Emergency Committee is made up of individuals who will have gained important and beneficial experience and will possess priceless institutional knowledge. Should any of these individuals put themselves forward as future candidates for roles in the governance of any of the Categories I would think that a good thing. Alas, I expect that the experience of holding such a visible and thankless job may drive some of them away from seeking future leadership roles.</p><p>As for the possibility of the emergency committee morphing as a whole into the oversight category governance, that is impossible. The Emergency Committee must continue to function in part until each of the five categories has a governance in place. And I personally would discourage any sitting members of the Emergency Committee from putting themselves forward as candidates for anything that could be perceived as a conflict. Again, please take a look at the <a href="https://drive.google.com/file/d/1UEvmUjwSql-AGJ8PHkMp-meENDEieBz8/view?usp=sharing">charter</a>, as it is fairly explicit on matters of conflict or appearance of conflict.</p><p>Thank you, Yves, EOS Nation, and the greater EOS Community for your engaged support!</p><p>I would like to hear your feedback and comments. Comment below or hit me up on <a href="https://t.me/dmargulies">Telegram</a>. You can also contribute to the ongoing work at <a href="https://t.me/eosio_wps">https://t.me/eosio_wps</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0f22df62ff9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wps-working-group-eos/feedback-from-eos-nation-talk-wps-emergency-committee-d0f22df62ff9">Feedback from EOS Nation talk: WPS Emergency Committee</a> was originally published in <a href="https://medium.com/wps-working-group-eos">EOS Worker Proposals</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WPS Group Announcement: Unbundling First Referendum]]></title>
            <link>https://medium.com/wps-working-group-eos/wps-group-announcement-unbundling-first-referendum-881253732471?source=rss-ab30033c6ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/881253732471</guid>
            <category><![CDATA[wp]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[eos]]></category>
            <category><![CDATA[eos-worker-proposal]]></category>
            <dc:creator><![CDATA[David Margulies]]></dc:creator>
            <pubDate>Wed, 17 Oct 2018 01:37:51 GMT</pubDate>
            <atom:updated>2018-10-17T03:17:47.737Z</atom:updated>
            <content:encoded><![CDATA[<h3>Unbundling First Referendum</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*04sSo5DgaWAgytA3Vs7QzQ.jpeg" /></figure><p><em>What follows is the personal opinion of an opinionated person and not a formal statement from the WPS Group — because that’s what EOS is governed by: a collective of individuals.</em></p><p>For the past few EOS-decades (Earth-weeks), the WPS team has been discussing whether we will continue to propose bundling the core activities in our first referendum. Our first instinct was to include these urgent needs:</p><blockquote>“From this fund, budgets will be set aside to support the EOSIO Core Arbitration Forum (ECAF), EOS Mainnet code repository management, security testing, and Emergency Committee Operations.”</blockquote><p>As discussions have progressed and we have repeatedly revisited this issue, I have come to change my personal stance.</p><p>I was a strong proponent of bundling for numerous reasons. However, as I started looking into the art of designing ballots and language for referendum, I realised that there were too many ingredients in our stew: we, as the team working on WPS, needed to focus on WPS in the referendum.</p><p>Therefore I would like to suggest that we decouple the non-WPS activities from the first WPS Referendum and instead have these activity proposals be presented to the Emergency Committee for separate community votes.</p><p>To be absolutely clear: I, as an EOS Holder, firmly believe that we need a properly funded, trained, operating Core Arbitration System with a central Dispute Resolution Rule Set, <strong>immediately</strong>. Without such, we as a platform, will become irrelevant in a very short time — Ethereum 2.0. As a potential member of the emergency committee, I will work closely with any proposal that plans to get Core Arbitration off the ground and I would hope that the community supports a well-crafted proposal to get approved.</p><p>I also believe that Mainnet code repository management, and security testing support need to be passed as proposals within the first few months. It is a clear indication of how unfinished the EOSIO system was when launched that these activities were not addressed on day one. Again, the only reason for unbundling these urgent and mission critical jobs is to keep the focus of the first WPS referendum on WPS and the creation of a safe management system for the EOS Commons.</p><p>I would like to hear your feedback and comments. Comment below or hit me up on Telegram, @dmargulies. You can also contribute to the ongoing work at <a href="https://t.me/eosio_wps">https://t.me/eosio_wps</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=881253732471" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wps-working-group-eos/wps-group-announcement-unbundling-first-referendum-881253732471">WPS Group Announcement: Unbundling First Referendum</a> was originally published in <a href="https://medium.com/wps-working-group-eos">EOS Worker Proposals</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Why and How of the Worker Proposal System: Bootstrapping from Chaos]]></title>
            <link>https://medium.com/wps-working-group-eos/the-why-and-how-of-the-worker-proposal-system-bootstrapping-from-chaos-e5f6a33e97c7?source=rss-ab30033c6ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5f6a33e97c7</guid>
            <category><![CDATA[worker-proposal]]></category>
            <category><![CDATA[eos]]></category>
            <dc:creator><![CDATA[David Margulies]]></dc:creator>
            <pubDate>Thu, 30 Aug 2018 02:58:54 GMT</pubDate>
            <atom:updated>2018-08-31T18:31:29.061Z</atom:updated>
            <content:encoded><![CDATA[<p>I was asked to speak at the EOS Ignite Conference (2018/8/14&amp;15) and this is the content of my talk. (<a href="https://youtu.be/CyCegEaNrRQ">https://youtu.be/CyCegEaNrRQ</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QNnTO0AcMDf7FouXMZUz1Q.jpeg" /></figure><h3>WORKING FOR EOS</h3><p>EOS is an operating system created for business on the blockchain. No first version of a major software release is without bugs or without a need for patching. So, who will be responsible for providing support for the maintenance of this operating system, as well as the development and addition of new features as required?</p><p>The block producers and volunteers are working away to build this grand venture, but reliance on the Block producers seems to fly in the face of decentralization and volunteerism doesn’t seem sustainable for long-term health.</p><p>Block.one did an admirable beta release, but for EOS to live up to expectations, we cannot rely on Block.one; they promised a number of key features that have not come to fruition and we need to build these soon: these include properly funded core arbitration, key recovery, IBC, storage, referenda tools, clear UX, and a functioning Worker Proposal system, to name a few.</p><p>The WPS group is working to build a set of tools and the workshop needed to build out the rest. By using a portion of the 4% inflation set aside to fund necessary projects, we can increase and improve the utility of EOS and its overall adoption.</p><h3>Bootstrapping A Worker Proposal System</h3><p>Bootstrapping any decentralized process is complicated and a daunting task. There are many things to build and fix. There are ideas to nurture, and many people to organize.</p><p>The first referendum is intended to do the minimum needed to grow the WPS.</p><h3>The First Referendum</h3><p>The first referendum vote will allow the WPS Group to bootstrap the WPS. It will allow you, the EOS token holder, to get a sense of what the WPS could be capable of without risking too many resources. This is what you will be voting for:</p><p><strong>Funding</strong>.</p><p>An initial amount of 1 million EOS tokens will be moved from the eosio.saving account to the eosio.wps account. Only this amount can be used for the purposes initially proposed. This fund is a ceiling for the first six months’ activities and there is little expectation that it will be used in entirety; any remaining funds will be burned at the wrap up of the bootstrapping phase.</p><p><strong>Emergency Committee.</strong></p><p>The Emergency Committee exists to handle urgent needs rather than a specific type of project. This is the only category included in the first referendum but it will be used to help launch other categories through worker proposals.</p><p><strong>Core Activities.</strong></p><p>From this fund, budgets will be set aside to support the EOSIO Core Arbitration Forum (ECAF), EOS Mainnet code repository management, security testing, and Emergency Committee Operations.</p><p><strong>Creation of Category system.</strong></p><p>Establish the existence of the worker proposal categories (see below) and the definition of their boundaries. This structure is intended to allow the greatest variety of governance options to figure out what works best, while limiting any scope for abuse or failure.</p><p><strong>An open call for governance design proposals for individual categories.</strong></p><p>Announcement that the second phase will have a call for Category governance structure worker proposals. The governance structure for each category is up to worker proposals submitted by the community.</p><h3>Governance Design</h3><p>The second round of voting will put forward the selection of proposals for the governance of the different categories. The Emergency Committee will manage a WPS competition for individual category governance structure designs to allow for experimentation with governance without risk to the whole ecosystem. At this stage, each category will be limited to its own financial boundaries with a cap of 10% of the eosio.wps account, to limit abuse and waste, and to allow room for future growth if and when token holders decide on it.</p><p>As each category is approved, the category in question becomes active and gets access to 10% of the eosio.wps account for its projects. When the category goes live, the Emergency Committee surrenders control over relevant proposals. Over time, the Emergency Committee ceases to exist as its duties are absorbed.</p><h3>Burning As A Safeguard</h3><p>Any new system that is rolled out may have problems, and there may be abuse vectors that we have not considered. WPS and the category governance structures are no different; therefore, until such time as there is community confidence in the various government structures, we propose a standing burn on all funds in eosio.saving not allocated to eosio.wps. Because each category is limited to 10%, and there are five categories, half of eosio.saving would be automatically burned on an ongoing basis. We are also proposing that the balance of the eosio.saving that will have accrued is burned when eosio.wps is first funded, so the funding source for WPS starts fresh.</p><h3>The categories</h3><p>Examining each category will give you an idea of the future proposals and indicate what governance structure would be a good fit.</p><p><strong>Oversight</strong></p><p>This category is for WPS portal maintenance, quality control, and oversight of other categories, as well as supporting any proposals that go through direct referenda instead of the WPS.</p><p>While the build is ongoing, these essential duties are handled out of the Emergency Committee. Most likely the best governance for this key category is some form of committee or representative body.</p><p><strong>Infrastructure</strong></p><p>This category is for supporting the underlying code base of the blockchain. This includes security audits, bug patches and code repository maintenance.</p><p><strong>Community</strong></p><p>This category supports the resources and spaces that bring people together. This includes meetups, educational content and platforms, public relations, lawyers, advocates and lobbyists.</p><p><strong>Development</strong></p><p>This category is for supporting developers and ideas. This includes support for decentralized applications and applications that may be necessary for underserved minorities.</p><p>Maybe you will choose to run this district as an Athenian democracy.</p><p><strong>Miscellaneous</strong></p><p>This category is for swag, burning, and projects that may not fit in other categories.</p><p>The potential here is vast and unknowable. How best to govern it?</p><h3>What do we need from You?</h3><p>In the near term, we need Governance proposals for the categories;</p><p>In the medium term, we need Worker Proposals; and,</p><p>We will always need Informed and engaged voting.</p><p>Anyone who has questions or wants to talk further you can find me on telegram @dmargulies.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5f6a33e97c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wps-working-group-eos/the-why-and-how-of-the-worker-proposal-system-bootstrapping-from-chaos-e5f6a33e97c7">The Why and How of the Worker Proposal System: Bootstrapping from Chaos</a> was originally published in <a href="https://medium.com/wps-working-group-eos">EOS Worker Proposals</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Worker Proposal City]]></title>
            <link>https://medium.com/wps-working-group-eos/worker-proposal-city-24dd35527ed8?source=rss-ab30033c6ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/24dd35527ed8</guid>
            <category><![CDATA[eos]]></category>
            <category><![CDATA[gig-economy]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[worker-proposal]]></category>
            <dc:creator><![CDATA[David Margulies]]></dc:creator>
            <pubDate>Thu, 30 Aug 2018 02:21:57 GMT</pubDate>
            <atom:updated>2018-08-31T03:42:12.546Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A graphic metaphor by David Margulies and Chris Pollard. Both are members of the EOS WPS working group.</em></p><p>In the beginning there was the EOS blockchain. There were block producers and token holders. For most, conditions were harsh and life was uncertain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ynaDspjFYfyY98_5" /></figure><p>The Worker Proposal System (WPS) Group formed, with the aim to help transform EOS into a city that the owners would be proud of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7C2VmLBi1wsh_Znu" /></figure><p>The first task was to purchase the land; a small piece of land to start with. These were the EOS tokens that would help to fund the transformation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qsF-soiLB273teeU" /></figure><p>The construction trailer was setup, where the Emergency Committee started work in supporting the urgent works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n3JaIYbeGeNXmKXU" /></figure><p>The underground plumbing and the electricity grids were constructed. This core infrastructure included emergency needs like ECAF funding and code repository management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jgMlRhl7kBprEPhG" /></figure><p>The zoning began. The Emergency Committee went about staking plots of land for each neighbourhood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YWMrxiTWyVEGTlOH" /></figure><p>A global competition was held, where any person or team could submit a design for a neighbourhood. This was an open call to build the best governance design for a new category of works.</p><p>Each time a winning team was voted by the community, the neighbourhood was born, with an ownership of 10% of the city’s land.</p><p><strong>The Neighbourhoods</strong></p><p>The Oversight neighbourhood is like the city hall. This is is where the works in other neighbourhoods are overseen and where the Worker Proposal System is maintained.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qtBwKgkF0VfkeYV5" /></figure><p>The Infrastructure neighbourhood is like the Department of Public Works. This is where the work is dirty and there is no praise. This is where we keep the underlying code base healthy, where security audits and bug patches are done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1RTN_BrT9inRSY9i" /></figure><p>The Community neighbourhood is like the public parks, the schools and the tourist attractions. This neighbourhood supports meetups, education and the resources and spaces that strengthen the community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G9zw-KkY9Ikk35Om" /></figure><p>The Developer neighbourhood is like the light industrial district. It is for supporting developers and ideas that will enrich the community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*14gsKuyV015-BvIr" /></figure><p>The Miscellaneous neighbourhood is like the artist lofts and the repurposed space. This neighbourhood is for swag, burning and projects that may not fit in anywhere else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ScZpCR9YvpShuwwT" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24dd35527ed8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wps-working-group-eos/worker-proposal-city-24dd35527ed8">Worker Proposal City</a> was originally published in <a href="https://medium.com/wps-working-group-eos">EOS Worker Proposals</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Worker Proposal City]]></title>
            <link>https://medium.com/@davidmargulies_27872/worker-proposal-city-48bae9f2a72?source=rss-ab30033c6ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/48bae9f2a72</guid>
            <category><![CDATA[wp]]></category>
            <category><![CDATA[eos]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[David Margulies]]></dc:creator>
            <pubDate>Thu, 30 Aug 2018 02:16:53 GMT</pubDate>
            <atom:updated>2018-08-30T02:19:57.975Z</atom:updated>
            <content:encoded><![CDATA[<p>Worker Proposal City</p><p><em>A graphic metaphor by David Margulies and Chris Pollard. Both are members of the EOS WPS core working group.</em></p><p>In the beginning there was the EOS blockchain. There were block producers and token holders. For most, conditions were harsh and life was uncertain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ynaDspjFYfyY98_5" /></figure><p>The Worker Proposal System (WPS) Group formed, with the aim to help transform EOS into a city that the owners would be proud of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7C2VmLBi1wsh_Znu" /></figure><p>The first task was to purchase the land; a small piece of land to start with. This was the EOS tokens that will helped to fund the transformation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qsF-soiLB273teeU" /></figure><p>The construction trailer was setup, where the Emergency Committee started work in supporting the urgent works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n3JaIYbeGeNXmKXU" /></figure><p>The underground plumbing and the electricity grids were constructed. This core infrastructure included emergency needs like ECAF funding and code repository management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jgMlRhl7kBprEPhG" /></figure><p>The zoning began. The Emergency Committee went about staking plots of land for each neighbourhood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YWMrxiTWyVEGTlOH" /></figure><p>A global competition was held, where any person or team could submit a design for a neighbourhood. This was an open call to build the best governance design for a new category of works.</p><p>Each time a winning team was voted by the community, the neighbourhood was born, with an ownership of 10% of the city’s land.</p><p><strong>The Neighbourhoods</strong></p><p>The Oversight neighbourhood is like the city hall. This is is where the works in other neighbourhoods are overseen and where the Worker Proposal System is maintained.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qtBwKgkF0VfkeYV5" /></figure><p>The Infrastructure neighbourhood is like the Department of Public Works. This is where the work is dirty and there is no praise. This is where we keep the underlying code base healthy, where security audits and bug patches are done. [image: an image of an engineer underground fixing a leaking pipe in a sewer]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1RTN_BrT9inRSY9i" /></figure><p>The Community neighbourhood is like the public parks, the schools and the tourist attractions. This neighbourhood supports meetups, education and the resources and spaces that strengthen the community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G9zw-KkY9Ikk35Om" /></figure><p>The Developer neighbourhood is like the light industrial district. It is for supporting developers and ideas that will enrich the community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*14gsKuyV015-BvIr" /></figure><p>The Miscellaneous neighbourhood is like the artist lofts and the repurposed space. This neighbourhood is for swag, burning and projects that may not fit in anywhere else. [image: not sure, this could be a really cool picture.]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ScZpCR9YvpShuwwT" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48bae9f2a72" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>