Notes
thegaram33 here’s a quick summary:
- RIP-7212: adopted by Polygon (live on testnet), zkSync (ready, rollout ETA April), Optimism, Kakarot
- Rollup registry wip: https://github.com/ethereum/RIPs/tree/rips_registry/registry. Chains that support an RIP on mainnet can be added here. Which chains → inclusion by default, we don’t want to define what a rollup is.
- What if a rollup is not fully compliant with a RIP, e.g. changes gas schedule? Generally it would count as not implementing the RIP. Multi-dimensional fees might address this.
- How to check if an RIP is implemented correctly? We could set up something similar to execution-spec-tests and reuse some of the testing setup from L1.
- Devex issues around partial support for precompiles, devs need to ensure support on each L2 they deploy on. We could use progressive precompiles but that proposal is not compatible with the RIP address range. Suggestion by @yoavw: new precompile that would allow checking RIP support on-chain in a standard way
Recording
