Versions Compared

Key

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

...

  • Keeping track of the discussions.

General context


We are getting various signals

...

  • Pros: 
  • Cons:
  • Risks:
    • Hyperledger 
  • Mitigations:
  • Horizon: 
    • pre-merge ? 
    • post merge?
  • Duration: 
    • 9 months - but we should divide in increment (module per module). 
    • For example, how long to modularize one core component of Besu?




General

Two step approach 

  • Open-minded approach, engineers attempting the modularization to see the real scope

...

  • EVM Engine
  • Consensus Protocols
  • Peer-to-peer communications
  • JSON-RPC Communications
  • Data Storage
  • Block Production



Modularization technical braindump


(brainstorm) Modular Client for the Merge - draft

  1. Approach #1 - “Besu as Debian” - create distribution artifacts from modules
  2. Approach #2 - “Execution Engine Shell” - create an execution engine project leveraging hyperledger/besu modules
  3. ?


Synthesis of the conversation on Discord

Participants: Gary, Danno, Sajida, Tim

https://discord.com/channels/@me/804833347816914944/885936379618545724

(add notes)


Debrief of meeting with Erigon

Meeting #1 - 9/14/21

Participants: Alexey, Madeline, Sajida

...