RollCall #0 - Layer 2 protocol & EVM standardization call #0

[CarlBeek]

This is a call to discuss a frameworks to help aid with coordination between the various EVM-like L2s. The idea is to establish optional norms and standards for L2s to be able to extend the EVM and related tooling while limiting conflicts with the L1 EVM and preventing a proliferation of mutually incompatible standards among the L2s.

Meeting Info

• Wed Oct 18, 2023, 14:00-15:30 UTC
• Zoom link shared on RIP coordination telegram channel shortly before the call (DM @CarlBeek on Telegram to be added)
• Recording available on YouTube https://youtu.be/aPvMoVI6rFE

Agenda

• General
  • The RollCall vision
  • RFC on schedule and timing
  • Further discussion at L2 day in Istanbul
• RIP standard
  • General & process
  • secp256r1 precompile

Further discussion

Feel free to add comments to this issue with further items of discussion

[oneski]

Polygon Ecosystem is considering the addition of EIP-3074.
https://github.com/maticnetwork/Polygon-Improvement-Proposals/blob/main/PIPs/PIP-22.md
If time would love to add as a discussion topic after secp256r1 (EIP-7212)

[drinkcoffee]

It would be good to discuss the EIP I have created for standardising profiles of opcodes that L2s could support.
This EIP could be expanded to include additions such as the EIP 3074 support @oneski you are considering.

[Dominik1999]

Nice

[0xverif]

looking fwd

[0xverif]

multi-chain apps need this

[lightclient]

Much less important than the actual technical considerations to discuss, but I really dislike the name "L2ED". In English "ED" usually refers to something other than "EVM devs".

May I pose some alternatives:

• All Core L2 Devs -- ACLD / ACL2D
• EVM Implementers Group -- EIG
• L2 Implementers Group -- LIG
• L2 Core Assembly -- LCA
• Council of EVM Devs -- CED

Also RIP is used frequently to mean rest in peace. I don't exactly love the naming collision. Some possible alternatives:

• EDP -- EVM Developer Proposal
• RFC -- Request for Comment (no need to be fancy)
• E2P -- EVM Layer 2 Proposal
• L2R -- Layer 2 Recommendation

[CarlBeek]

Also not a fan of the "ED" naming. I'm particularly partial to "RollCall" (ht @barnabemonnot).

In terms of "RIP", I don't really have strong feelings in any particular direction. I don't think RFC is nearly specific enough for a set of standards.

[lightclient]

Ooo "RollCall" is nice.

[DRIPDROPS]

Posse Up!

[CarlBeek]

Recording Live at https://youtu.be/aPvMoVI6rFE

[holgerd77]

If possible and not causing too much extra work would be very appreciated to get a 4-7 bullet point summary of these calls. 🙂

[abcoathup]

Brief summary:

• intros
• Rollup Improvement Proposals (RIPs) process, shared numbering with EIPs/ERCs, call for volunteer RIP editors
• EIP7212 (secp256r1 precompile) as first candidate for an RIP
• Devconnect discussion topics
• EIP7530 (EVM profiles)

[d1onys1us]

if you are looking for the RIPs repo check here: https://github.com/ethereum/RIPs

[mratsim]

One agenda item is the EIP 4844 test schedule for goerli, sepolia, holesky.