You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Feedback Requested. This is a draft document. 

Near-Term Set Up :

Note: This is targeted to be a six month resolution. The only funds that the Hyperledger Besu team will receive pre Merge is transaction fees. The Merge is currently tentatively scheduled for Q3 2022.

  1. ConsenSys will run the validator nodes for this 6 month term because the team is set up to do so and timing is critical to begin participating in the Incentive program
  2. All profits received are distributed into a multi-sig. HLF, EF, and ConsenSys are the three parties that will have access to the multi-sig. Funds will be distributed to organization/participants based on the below. A sample breakdown to demonstrate distribution can be found here on the second tab. 
    1. 40% - # of pull requests for mainnet (add in a mainnet tag to PRs to track)
    2. 45% - # of running of validator nodes
    3. 5% of all funds will be put into bounty program
    4. 10% of reserves to be used for community engagement purposes in future.
  3. HLF will be responsible for attributing rewards to contributors other than ConsenSys. At least 2 of the 3 signatories (EF, HLF, EF) will have to be present to distribute the funds, but HLF should attribute/track the addresses of contributors.

PR Repos:

  • hyperledger/besu
  • hyperledger/besu-native
  • hyperledger/besu-docs

Link to the spreadsheet (funds breakdown simulation): Incentive Program Breakdown

At the end of 6 months, we will conduct a reevaluation of the Funds Distribution Program with the EF, HLF, ConsenSys, and Besu Maintainers approving revisions. Throughout the six months, we will be working towards a long-term solution.

Medium/Long Term Set Up: 

Note: The funds received post 6 months will include transaction fees and staking rewards. Staking rewards will not be available until post-Merge.

These are items to be addressed as we build a long-term solution for how to manage Besu's governance and the funds from the Incentive Program.

  1. Other organizations can consider running validator nodes. If they meet requirements as indicated in the requirements documentation provided. Besu maintainers can vote to decide if an organization meets requirements. Details to be agreed upon.
  2. A more complex DAO could be set up to manage voting, tokens, or other aspects.
  3. Determine if pull requests are a good fit and working well given some pull requests might be smaller than others.
  • No labels