DOCSEARCHbyAlgolia
Submit Docs

Optimism Protocol Upgrades

website·Indexed 41 days ago

https://community.optimism.io/

Documentation on protocol upgrades for the OP Stack, detailing how the network stays up to date with the latest innovations and the process for managed upgrades.

Tokens
374
Snippets
0
Records
3
Agent score
22%

What's inside Optimism

  1. Understand the OP Stack protocol upgrade process

    The OP Stack uses a structured upgrade process to mitigate platform risk and ensure changes align with the interests of businesses building on the platform.

    1. Drafting: Upgrades are drafted by OP Labs or core contributors.
    2. Review: The Developer Advisory Board (DAB), an independent group of developers, reviews the proposal to ensure it is well-justified.
    3. Veto Period: After DAB review, there is a 7-day veto period. Tokenholders, chains, apps, and end-users can override the DAB's decision if the upgrade is deemed disadvantageous.
    4. Appeals: If a proposal is vetoed, it enters an appeals and discussion phase before it can be resubmitted.

    This system ensures that no single entity (including OP Labs or the Foundation) can unilaterally dictate the future of the OP Stack.

  2. Influence the OP Stack feature roadmap

    Developers and chain operators can influence the OP Stack roadmap through the following channels:

    • Open Development: All development occurs in public repositories; chains are encouraged to participate and share perspectives in research and development repos.
    • Revenue Contribution: Superchain members who contribute revenue back to the Collective are specifically consulted by OP Labs and core developers regarding the feature roadmap.

  3. Achieve Stage 1 decentralization for OP Chains

    To be classified as Stage 1 in the L2Beat framework, an OP Chain must be a permissionless Fault Proof OP Chain with its upgrade keys managed by the Optimism Security Council. This ensures upgrades are scrutinized and managed by a distributed group.