You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Zoom link shared on RIP coordination in the RollCall channel in the EthR&D Discord which is bridged to the RollCall telegram channel shortly before the call.
RIP 7212 finalised! - rollups that choose to do so can now deploy the secp256r1 precompile knowing that the specs won't change and there won't be an address conflict at 0x100
Discussion of EIP-7587 - This EIP reserves the address range 0x100 - 0x1ff for use by RIPs, so we can deploy further precompiles in the future
Ansgar announced Rollcall working groups over the next few Wednesdays:
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
RIP coordination
in the RollCall channel in the EthR&D Discord which is bridged to the RollCall telegram channel shortly before the call.Agenda
Further discussion
Feel free to add comments to this issue with further items of discussion
The text was updated successfully, but these errors were encountered: