Please vote for us, we need your support to continue offering such tools and services!

Voter enforced standby Block Producer rotation

chainri4cvib by chainriftxxx 13-July-2019 11:12:51 UTC referendum-v1

Poll status

7,749,617 EOS voted
Vote

You voted {{(lastVote==1)?'YES':'NO'}}  

{{votingResponse.message}}

Post a public comment (optional)

Select Yes/No to cast your vote and make your comment public on the EOS blockchain. Your comment and vote will be recorded on-chain for ever, if you want to change your comment please vote again and our algorithm will attempt to just show your latest comment.

Account
{{ webdigiWallet.account.account_name}}

  • 25 accounts
  • 34 days since poll started
  • 0.74% participation
  • 100% YES lead over NO

CVIB Terms, Conditions, Agreements

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

For Block Producers:

I understand that commitments that are issued by proxies voting “yes” for this proposal can be revoked.

I request that the proxies fund my development for ‘Voter enforced standby Block Producer rotation’ project for 12 months, starting on 1. April.

Project Link: Google Docs

Brief Overview:

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.

The mechanism allocates one voting slot that randomly selects a standby BP, and puts them into the 21st position. All participating proxies are automatically coordinated to randomly select the same standby BP.

BPs are rotated into the 21st position every 2-4 hours for 4 rounds. If a BP fails to produce, article 8 of the proposed EOS42 regproducer will be specifically catered to this mechanism.

If consensus is eventually reached for soft-forking changes, we can prepare further changes that will empower the already deployed and battle-tested contracts. Specifically the merging of order selection smart-contract in the system contract and allow [claimrewards] only when producing (forcing standby BPs to produce or never able to receive rewards).

In addition, we would develop a solution for a “true” random selection mechanism to determine the random rotation on a chain. This random mechanism can also be leveraged by any dApp that needs a random number selector, such as casinos and games.

Due Date: 1. June for the opt-in solution Due Date: 1. January 2020 for random beacon contract

Deliverables can be tracked and monitored here: github.com/chainrift

I agree to give updates on the project 2x per month for proxy review. Those updates can be reviewed here: t.me/ChainRiftEOS


For proxies:

By casting a yes vote for this proposal, I hereby agree to commit my votes for the time requested in this proposal. If I want to vote yes, but do not agree to the amount of time request, then I will leave a note specifying the amount of time I will vote for the proposal.

If I decide to withdraw my vote before duration of my commitment has come to term, I understand that it is my responsibility to choose whether or not a public statement is needed.





Time Frame:








4 Comments

These comments were made along with their vote

Sort by...
  • Random Beacon sounds excellent, please build it!

  • I support this initiative, but have no yet committed to participating in CVIB. I will continue to vote for BPs according to my proxy philosophy which includes supporting BPs which add value to the network through projects like this.

  • I am voting for this based on the implementation of the soft-fork solution without the opt-in phase.

  • Innovative mechanism to empower proxies and voters to fund the missing infrastructure.