Blue Paper Community Feedback Initiative

Author

EOS Network Foundation

Date

Feb 25, 2022

EOS bounties offered for qualifying feedback on Blue Papers

In the wake of the ENF working group Blue Papers being published and demonstrating the fruits of collaboration produced by multiple teams within the EOSIO ecosystem, we now enter the next phase in our deliberation on the proposals put forward as we solicit the community for feedback.

The Blue Papers have been crafted by some of the most experienced and knowledgeable teams developing on EOS. The collaborative nature of the working groups allowed them to hone in on many of the most salient issues EOS faces and articulate many novel solutions.

The EOS community is composed of many talented and perceptive individuals, and the power of our community shows up in many ways, including a rich diversity of experience and perspective on the tools and strategies available to us. As thorough as the working groups have been, it’s likely that members of the community will see other valuable approaches to any particular problem that are worth considering.

The ENF and the sponsored working groups are now actively seeking out community feedback on such considerations. Additionally, we would like to hear the community’s thoughts and opinions on the funding proposals put forth by each of the sponsored working groups.

Introducing: Blue Paper Community Feedback Initiative

We would now like to invite the broader EOS community to weigh-in on these formative Blue Paper documents.

Here are the categories of longform written contributions that we’re seeking:

Funding Proposal Feedback: Identify work proposals outlined in a Blue Paper and communicate why or why not you believe that work should be funded and whether or not you agree with its budget. Please include as much detail as possible behind your reasoning and offer an alternative solution, if possible.
Alternative Solution: An alternative to the solution should explain why this solution would be preferred vs the original solution in the Blue Paper. It should highlight why the originally proposed solution is not deemed optimal and potential ramifications of implementation. It should contain reference materials and links if available.
Enhanced Solution: An Enhanced Solution would build upon the original author’s proposal by adding more features or functionality. It would not be an alternative as in the previous section, but an extension of the originally proposed solution.
Additional Section & Solution: This section would include an additional solution to the Blue Paper that was not in the original. It is not replacing any current section or debating it, but adding in a new feature or enhancement to that working group that the author feels was omitted. It should indicate whether the author of the post would be willing to help implement the solution and any timeline estimates / information.

Feedback Submission Deadlines

Audit+: March 12, 2022
Core+: March 12, 2022
API+: March 19, 2022
Wallet+: April 2, 2022

Criteria for Contributions

Read, understand, and abide by these criteria before you finalize your feedback and submit it for consideration.

Reference the Blue Paper name, section header, and page when proposing an alternative or enhanced solution.
Reference whether the post is an Alternative, Enhanced, or Additional Solution.
Contributions should be in the form of a blog post or post on a publishing platform such as medium.com or hive.blog.
Posts should be written as articles no shorter than 500 words and no longer than 3000 words.
If you have multiple submissions for multiple Blue Papers or have both alternate solutions and additional solutions, it is fine to create a separate blog post for each.
Post should contain constructive additional or alternative information and not be simply agreeing with or confirming the original author’s information.
Do use the Google Doc versions of the Blue Papers to make small changes such as grammar, spelling, or requests for clarification.
Do NOT use the Google Docs to provide long feedback or debate sections, instead, make a blog post and earn some EOS!

All submissions must be made using the Google web form with your information to be considered as a qualified entry.

EOS Bounties for Qualifying Entries

Qualify and earn from 100–2000 EOS for your contribution!

Participants whose response article adheres to the “Criteria for Contributions” expressed above which meet the minimum criteria for contributions will receive 100 EOS for their efforts.
Participants whose feedback fits into the Alternative Solution category AND whose feedback is approved & integrated by authors will be awarded up to 2,000 EOS.
Participants whose feedback fits into the Additional Section & Solution category AND whose feedback is approved & integrated by authors will be awarded up to 2,000 EOS.
Participants whose feedback fits into the Enhanced Solution category AND whose feedback is approved & integrated by authors will be awarded up to 1,000 EOS.

*Entries that are incomplete or do not comply with the Criteria as ‘Qualifying Entries’ may be disqualified at the sole discretion of the ENF and working group participants. The reward amount totals for Alternative, Additional, and Enhanced Solutions that get approved for integration into the community edition of the Blue Papers is at the sole discretion of the ENF and working group participants.

Short Form Community Feedback

Community members who do not wish to write an entire blog article providing detailed feedback on a proposal are also invited to leave short comments directly on a Google Doc version of each Blue Paper. Community feedback is also being accepted in the working group channels in EOS Discord, but organizing that feedback directly onto the Google Doc is preferable. Comments and suggestions to the Google Docs are not eligible for the incentives outlined above, but are still highly encouraged for gathering valuable community feedback.

Blue Papers

Audit+ Google Doc — English | Chinese | Korean
Audit+ PDF — English | Chinese | Korean
Core+ Google Doc — English | Chinese | Korean
Core+ PDF — English | Chinese | Korean
API+ PDF — English | Chinese | Korean
API+ Google Doc — English | Chinese | Korean
Wallet+ PDF — English | Chinese | Korean
Wallet+ Google Doc — English | Chinese | Korean
Wallet+ Blue Paper

Let’s Hear Your Voice!

The response from this initiative will mature the Blue Papers into a “community enhanced” version that will enable us to confidently take action on the recommendations they contain with an even greater degree of certainty that nothing has been overlooked in the process.

We encourage you to promote your article on social media, and be sure to tag the ENF and relevant authors where appropriate. Above all, be sure to submit the link to your post using the Google Form or it may not be counted

We look forward to hearing from you!

EOS Network

The EOS Network is a 3rd generation blockchain platform powered by the EOS VM, a low-latency, highly performant, and extensible WebAssembly engine for deterministic execution of near feeless transactions; purpose-built for enabling optimal web3 user and developer experiences. EOS is the flagship blockchain and financial center of the EOSIO protocol, serving as the driving force behind multi-chain collaboration and public goods funding for tools and infrastructure through the EOS Network Foundation (ENF).

EOS Network Foundation

The EOS Network Foundation (ENF) is a not-for-profit organization that coordinates financial and non-financial support to encourage the growth and development of the EOS Network. The ENF is the hub of the EOS Network, harnessing the power of decentralization as a force for positive global change to chart a coordinated future for EOS.