Cooperative Voting Infra Bounties group

(28 Million votes STRONG!)


Cooperative Voting Infra Bounties group

CVIB Ethos & Intention:

CVIB was started with the vision for proxies to explicitly signal intent to vote for BPs, for a given time frame, on the basis of specific projects being built.

  • Instead of having to “guess” what voters want, BPs will have access to explicit deliverables that will “guarantee” votes.
  • Voters can “fund” projects that they want by pooling their voting power for specific projects to be built.
  • This model explicitly aligns incentives so that important EOS projects are built. BPs can have more certainty about the impact of their efforts on their ranking position, and voters can start to create a more actively engaged culture in which their desires are less abstracted.

CVIB generally prioritizes bounties for critical EOS infrastructure that generally fall under these categories:

  • Unlikely to get developed due highly demanding development costs
  • No post development monetary returns
  • Network Security

Status Update:

Cooperative Voting Infrastructure Bounties (CVIB) began with a vision to pool votes in order to “fund” the development of important EOS infrastructure that lacks post development monetary returns. The EOS community quickly rallied behind the idea. Nineteen proixies totaling 28 million votes signaled intent to commit their voting power to the teams that build an open-source full history solution, or mechanism to test standby performance. Several BPs reached out shortly after the announcement. Five official proposals were submitted.

You can view the current list of participating proxies here

Members (~28 million votes)

  1. The Starkness
  2. Chintai
  3. Investing with a difference
  4. Colin Talks Crypto
  5. EOS Titan
  6. EOS Cannon Proxy
  7. Tokenika
  8. Freedom Proxy
  9. Eos Vibes
  10. Meet one Proxy
  11. Mentormarket
  12. Good Guys 4 EOS
  13. BP Governance Proxy
  14. Mereo
  15. EOS BP Ratings
  16. Ferdous Bhai Proxy
  17. Vote with Detroit
  18. luhaifengeos
  19. itokenpocket

List of Members and Votes



Open Source Full History Solution

  • Conforms to the existing history plugin RPC format that is compatible with existing infrastructure. RPC documented here:
  • OR, if a new API standard is introduced, it should be well documented
  • Why Full History?Full History nodes support the crucial function of allowing dApps to effectively query blockchain data. The current solutions are cost burdensome, inefficient, or closed source. EOS needs to develop a scalable, open source solution that will lead to efficiency and redundancy.


Testing Paid Standby Ability to Produce

  • One Standby BP is randomly rotated every 6 hours
  • BP is rotated into a producing spot that does not contribute to finality, nor affect the top 21
  • Ability to produce must be confirmed objectively
  • Automated enforcement is ideal

Why Test Standby BPs?

EOS42 has been very involved in developing the governing protocol of the `reg_producer` contract. We’re advocates of enforceable standards that hold BPs accountable, and protect the basic elements DPoS.

Given the current game theory involved in EOS, it’s unlikely that BPs would enforce anything that isn’t an objective threat to network security. However, being able to produce blocks is a bare minimum requirement that most everyone can likely agree on. Every paid BP should be able to produce blocks. Testing standby BPs ability to produce blocks protects network security, nourishes network performance, and keeps paid standbys honest.