Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Discussion:

Besu Incentive Program

  • Goals 
    • Teams free to do what they want with validator value and validator tx fees (rewards) 
    • Keys will be divested over 6 month periods (allowing more and more funds to be withdrawn) 
    • Provide long-term incentives to folks that are building Ethereum Mainnet clients 
    • Offered to all mainnet client teams (execution and consensus) 
    • EF will provide validator keys at a later time depending on incentive program milestones
  • Performance metrics
    • Taken over a monthly time frame
    • Over 95% attestation and block proposal inclusions 
    • Avoid slashing for these validators - slashed validators will be removed from the program
    • Consensus client issues - EF will not penalize execution layer client for consensus issues on the other client 
    • Execution layer has to be quick enough (performant) to create the block 
  • Interoperability 
    • Trust in this process by EF - good faith interop (could use canary nodes for combinations that are less tested)
  • Why Now?
    • Prepping for the Merge
    • Helps measure performance and confirms meeting protocol expectations
  • How do we run this program across the Besu community? 
    • This is a big ask for time from community members - Not all should be forced to be node operators
  • Concerns are:
    • All maintainers can't run a release 
    • Data not shared from ConsenSys with the community
    • Lack of transparency from ConsenSys team on roadmap
    • Money will make this open source project more challenging with the community 
    • PRs that need to be reviewed in timely manner
  • Ideas for Incentivizing Besu community
    • Near term idea: Bounty program
    • Near term idea: Clear benchmarks/requirements for operator validator nodes
    • Medium/long term idea: Besu DAO

If we have time...

General Announcements

...