EOS Town Hall - March 25, 2019

Notes Created By: LibertyBlock


Key Takeaways

Introduction to the Cooperative Voting Infrastructure Bounties (1:23)

Instead of having to “guess” what voters want, BPs will have access to known deliverables that will guarantee votes. Similar to the idea of Worker Proposals, voters can “fund” projects that they want by flexing their voting power.

Projects will focus on addressing critical problems in the EOS infrastructure that fall under three categories:

(1) Highly demanding development costs;

(2) No post-development monetary returns; and

(3) Network security

The first bounties are for:

(1) The development of an open source full history solution; or

(2) A mechanism for testing standby production

Requests for Proposals (6:00)

ChainRiftEOS, LibertyBlock, and NodeOne have all submitted proposals with substantial differences. Once submitted, a robust technical assessment of various options should be conducted before moving forward.

ChainRiftEOS’s Proposal (15:16)

The ChainRift solution leverages an “opt-in” approach that requires no system code changes. Proxies and regular users can opt-in by adding permission specifically for the contract developed by ChainRift.

Find out more.

LibertyBlock’s Proposal (36:18)

In order to ensure that backup block producers are always ready to produce blocks, LibertyBlock proposes the following:

Replace the 21st slot in active production with a rotating slot that allows backup producers rank 21–25 to rotate into the production schedule. Each of the five backups will take turns producing blocks. Implementing this solution will require a hard fork.

Find out more.

Gaining Visibility and Next Steps (47:40)

Ryan Bethem from EOS42 is working on a SWOT analysis of the proposed solutions as well as a timeline.

Next Week’s Call

We will discuss CVIB and Ryan’s SWOT analysis of existing proposals.


A special thank you to: