[Request for Comment] OP Stack Interactive Specs: opcodes, precompiles etc

Hey guys, Z from LimeChain here.

TLDR: This post is a request for feedback/comments for developing a public good website with interactive specs for the OP Stack (and other rollups) that includes opcodes, precompiles etc.

As blockchain devs, we sometimes find it challenging to assess the differences between developing on L1 versus a given rollup, or between different rollups. Additionally, it is unclear what custom precompiles exist on say the OP Stack, which precompiles are supported, what L1 state is exposed on a rollup, what system-level contracts exist, what the gas costs, latency and interface are for L1 - L2 messaging and how EVM gas pricing has changed etc etc.

In the coming months, there will be a rapid deployment of rollups leveraging the OP Stack. In addition to that, other rollups are gearing up their stack for chains to be built on top of them as well. These new rollups will only add to the confusion around what is available and how it differs from other options.

To address this issue, we are tinkering with the creation of an Interactive Reference Specification for the rollup ecosystems. This website would serve as a valuable resource for developers and provide clarity on the differences between various rollups and their stacks. The website would be extending upon the idea of evm.codes as a base, but would incorporate information on rollups (differences from L1, gas costs, custom precompiles, native precompiles support, system contracts, properties of the native L1 ↔ L2 messaging protocol provided by the given rollup etc).

We think that such a knowledge base will be valuable to dApp/infrastructure/rollup developers and auditors.

Would love to hear feedback on whether you find this valuable, and also what you as a developer community would like to see on it, in order for its value to be maximised.

Thanks!

4 Likes