Gloas devnet planning

[michaelsproul]

What do we need?

Local devnet

• Gossip of envelopes (@eserilev, @jimmygchen): to be separated from range sync.
  • Gloas gossip boilerplate #8700
• DA checker (@eserilev, @pawanjay176)
  • Gloas data availability checker #8716
• Consensus changes including containers (@michaelsproul and @jimmygchen):
  • Gloas consensus v1.7.0-alpha.1 #8677
  • Implement Gloas withdrawals and refactor #8692
  • Move KZG commitments from payload envelope to payload bid and spec alpha.2 #8725
• Beacon chain changes @jimmygchen
  • Envelope processing
  • import block & envelopes into the database
• Block production support (@michaelsproul, @eserilev, @shane-moore when avail):
  • Gloas local block building MVP #8754
  • Once this is done, we shoud be able to enable test-beacon-chain-gloas
• Bare minimum fork choice (import payload and building on top of payload) (@hopinheimer)
• Database changes
  • Payload envelope db operations #8717

Devnet-0

• Gossip verification changes for attestations and blocks (@jimmygchen).
  • Gloas attestation verification  #8705
• (Optional) RPC by range/root responses for envelopes (@eserilev, @jimmygchen): to be separated from range sync.

Future work:

• Gossip of payload attestations
• Gossip verification changes for DataColumns (@jimmygchen)
• RPC by range/root responses for envelopes (@eserilev, @jimmygchen): to be separated from range sync.
• Multi BN changes for VC
  • gloas VC block production #8313
• RPC by range/root requests for envelopes (@eserilev, @jimmygchen): to be separated from range sync.
• Sync (@eserilev, @pawanjay176, @dapplion)
• PTC support in BN/VC:
  • Gloas vc ptc duty #8338, Gloas ptc duties beacon node response #8415.
• Gossip of builder bids/proposer prefs Gloas gossip boilerplate #8700
• Fork choice (@hopinheimer, @michaelsproul, @eserilev):
  • Gloas fork choice #8562

[michaelsproul]

We've bumped RPC and sync support out of scope for devnet 0 so we are more likely to meet the goal of interop on Feb 18 (as discussed offline with @jimmygchen and @eserilev). If we have time we can consider RPC responses for envelopes (a stretch goal).

[eserilev]

Potuz wrote:

ah yeah the entire forkchoice is irrelevant IMO for devnet-0, it's not enforceable, As long as you can follow empty/full chains and build on full if you have the payload I think we're fine
My moto for devnet-0 is "the minimum possible to separate the block from the payload"

So it sounds like we can punt most fork choice complexities to devnet 1.

[eserilev]

It seems some clients may be relying on rpc payload by root requests in order to prevent themselves from stalling out. I think introducing the rpc boilerplate and serving payloads over rpc is a relatively small lift. I'll aim to get that done by the devnet deadline

[eserilev]

I've moved PTC BN/VC support to the future work section. It's not needed for devnet 0. All we need is to be able to gossip payload attestations (so peers dont downscore us).

We also wont be including any payload attestations in blocks that LH proposes.

[eserilev]

We wont be propogating any data columns during devnet 0, so I'm moving data column gossip verification to the futures work section