Skip to content

Idea: Add L2 Configuration Fields #4833

Open
@MSilb7

Description

@MSilb7

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
  • ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions