Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea: Add L2 Configuration Fields #4833

Open
MSilb7 opened this issue Apr 12, 2024 · 0 comments
Open

Idea: Add L2 Configuration Fields #4833

MSilb7 opened this issue Apr 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@MSilb7
Copy link
Contributor

MSilb7 commented Apr 12, 2024

As more L2+s are launching, there are many more interesting and useful fields for analysts and chain consumers. A huge personal painpoint has been trying to track: "How many chains are built using the OP Stack? How many are using L1 DA? etc."

Since these chains will get added to this list in some sort, I thought this would be a great spot to capture some of this information. L2Beat tracks most of this information today, but is not (yet) exhaustive of all chains.

Listing ideas below, but open to discussion about 1) Does this make sense?, 2) If so, what should these fields look like?

  • Rollup Software: OP Stack, Arbitrum, zkSync Stack, Polygon SDK, etc
  • Prover Type: Optimistic, ZK, etc
  • Data Availability Layer: Ethereum, Celestia, EigenDA, BNB, Polygon PoS etc
  • State Output Layer: Ethereum, Base, BNB, etc
  • ?
@ligi ligi added the enhancement New feature or request label Apr 14, 2024
@ethereum-lists ethereum-lists deleted a comment from Goonte May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants