2021-12-30 Besu Contributor Call (off cycle) - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window) PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2021-12-30 Besu Contributor Call (off cycle) More actions 2021-12-30 Besu Contributor Call (off cycle) Grace Hartley (Deactivated) Ry Jones Owned by Grace Hartley (Deactivated) Last updated: Jan 03, 2022 10 AM ET on December 30th.  Zoom: https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09#success Agenda Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature Discussion: See notes from prior call for additional context.  Agenda for next call (potentially off-cycle): Incentive program (30 mins) Cost of running nodes DAO Proposal Progress DAO Brainstorming Doc: https://hackmd.io/A_iqjtVQRjSL4M9mLa0ncg?view Two open questions from Danno: We still need to figure out who is running the validators Open question is one entity if Hyperledger could be the one holding the keys. Daniela is in discussions to see if this is possible. Of course we need there to be accountability. What does it take to run a node pre-Merge? It's relatively easy. What does it take to run on a node post-Merge? Run XL instance with MVMe and T3.xl Action: Come back with detailed understanding of what it takes to run a validator node. Note: There is a level of experience that is needed to run validator nodes. Group needs to agree on what skillset and expertise is needed by the people running the validator nodes because that is a cost and requirement in addition to the hardware requirements to run nodes. Decision: We would not be interested in an organization running only a node pre-Merge. An organization would need to be able to run pre and most Merge nodes. Antoine has concerns about the DAO being a good use. He would like it to be considered we decline the money and program or Hyperledger has control of the keys. It is the EF's call and their decision how they want to distribute the keys. We need the  We need to address how it works if someone has a super majority of nodes One idea is that we could do quadratic voting to help address super majority of nodes. Gitcoin uses this in their grants so we can explore how they run it. (less important point) We should maybe consider it forward looking it only rather than retroactive. Other Proposals Besu maintainer progress/community concerns (30 mins) There is concerns around ConsenSys owning the project.  Non-ConsenSys employees are having issues getting their PRs reviewed. Ideas for improving Besu community:  Having all contributors join monthly Contributor call Public roadmap on wiki covered in monthly contributor call needs to be up to date Discord chat channel moving forward. Targeting to make a decision in January because that would bring Besu to Ethereum  Regular call to catch up with all Besu contributors not recorded Leverage LFX analytics on Besu to review at top of contributor calls to see time to review on pull request and other metrics. Next Steps: Come back with what it takes to run a validator node (next week or two Review proposed ideas for community practices above with the APAC contributor call on Jan 3rd Danno to share a revised proposal around incentive program View recording:    File Modified Labels No labels Preview View File Besu-Contributor-Call-2021-12-30.transcript.vtt Dec 30, 2021 by Ry Jones Labels No labels Preview View Text File Besu-Contributor-Call-2021-12-30.txt Dec 30, 2021 by Ry Jones Download All , multiple selections available, {"serverDuration": 10, "requestCorrelationId": "79c97590a5f446a18c9dbe77acb10384"}