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 are beacon chain staking rewards. The Merge is currently tentatively scheduled for Q3 2022.
- 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
- 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.
- 40% - # of pull requests for mainnet (add in a mainnet tag to PRs to track)
- 45% - # of running of validator nodes
- Feedback: We should probably map this amount to be cost + margin.
- 5% of all funds will be put into bounty program
- Feedback: We want to make sure the bounty program is fully functioning. We have had various results with bounties in the past.
- 10% of reserves to be used for community engagement purposes in future.
- HLF will be responsible for attributing rewards to contributors other than ConsenSys. At least 2 of the 3 signatories (EF, HLF, ConsenSys) 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 EVM fee rewards (Justin Drake's spreadsheet, more info on rewards).
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.
- 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.
- A more complex DAO could be set up to manage voting, tokens, or other aspects.
- Determine if pull requests are a good fit and working well given some pull requests might be smaller than others.
2 Comments
Antoine Toulme
I don't understand this proposal because it says it's for near-term, but sets up a reserve fund for the future. I have peppered the document with comments asking for explanations and more detail on what you mean.
This doc does not conciliates with any of the proposals I have made.
Danno Ferrin
I have lots of thought about this, and here are some of them: Response to Consensys' First Incentive Proposal.