Skip to content

Commit

Permalink
Update text and remove old diagram
Browse files Browse the repository at this point in the history
  • Loading branch information
jlwllmr committed Aug 14, 2024
1 parent dd91a48 commit 01e3d8f
Show file tree
Hide file tree
Showing 2 changed files with 86 additions and 136 deletions.
120 changes: 86 additions & 34 deletions docs/architecture/overview/decentralization-roadmap/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,17 +4,8 @@ sidebar_position: 9
image: /img/socialCards/decentralization-roadmap.jpg
---

import LineaLaunchRoadmap from "/img/article_images/Decentralization_roadmap/Linea_timeline.svg";

<div className="img-large">
<LineaLaunchRoadmap />
</div>

<br />
<br />

The Linea roadmap is currently scoped in five phases which the team intends to deliver sequentially in collaboration with
the broader Linea ecosystem and community.
The Linea roadmap is currently scoped in five phases which the team intends to deliver sequentially
in collaboration with the broader Linea ecosystem and community.

<div class="center-container">
<div class="img-large">
Expand All @@ -27,44 +18,105 @@ the broader Linea ecosystem and community.

## Phase 0 — Complete

Phase 0 began with the launch of the Linea Mainnet Alpha. From Day 1, Linea's EVM-equivalent zkEVM offered default portability through its implementation of the EVM as specified by the Ethereum Foundation. A developer building on Linea can choose at any time to move their dapp to another EVM-supported chain, such as Ethereum, in the event they are unsatisfied with the Linea network, without re-writing their smart contracts, retooling, or paying for new audits.
Phase 0 began with the launch of the Linea Mainnet Alpha. From day one, Linea's EVM-equivalent zkEVM
offered default portability through its implementation of the EVM as specified by the Ethereum
Foundation. A developer building on Linea can choose at any time to move their dapp to another
EVM-supported chain, such as Ethereum, in the event they are unsatisfied with the Linea network,
without re-writing their smart contracts, retooling, or paying for new audits.

During this phase we will also convene the first iteration of the Linea Security Council, formed to monitor the network, protect users, and mitigate the risks associated with a new production system. The Security Council is managed through a multi-sig Safe (formerly Gnosis Safe) contract that requires certain thresholds of signatures to be submitted to carry out an action. Details can be found in our [risk disclosures](/risk-disclosures).
During this phase we convened the first iteration of the Linea Security Council, formed to
monitor the network, protect users, and mitigate the risks associated with a new production system.
The Security Council is managed through a multi-sig Safe (formerly Gnosis Safe) contract that
requires certain thresholds of signatures to be submitted to carry out an action. Details can be
found in our [risk disclosures](/risk-disclosures).

Finally, the client software used to run a local node on the Linea network was made publicly available, giving any actor the option to verify the Linea state for themselves and minimize trust in the Linea operator.
Finally, the client software used to run a local node on the Linea network was made publicly
available, giving any actor the option to verify the Linea state for themselves and minimize trust
in the Linea operator. View our [node running guides](/developers/guides/run-a-node) to get started.

## Phase 1 — Current

There are two significant components in this phase: the **open-source stack** and ensuring **100% EVM coverage**.
There are two significant components in this phase: the **open-source stack** and ensuring **100%
EVM coverage**.

In the spirit of fostering transparency and maintaining an open platform, the **open-source stack** is an essential element of our roadmap. We plan to license the Linea software stack under AGPL-3.0. This free software license ensures that users have the freedom to view, fork, and modify the code.
Open-sourcing Linea's software stack is an essential element of our roadmap, fostering transparency
and aligning with web3 values. The Linea software stack is publicly available under the
[AGPL-2.0](https://www.apache.org/licenses/LICENSE-2.0) license, which ensures that users have the
freedom to view, fork, and modify the code. An overview of Linea's repositories is available in
our [architecture section](/architecture/stack).

The second cornerstone of this phase is the implementation of **100% EVM coverage** in the zkEVM arithmetization. Linea will generate proofs of computation for all EVM opcodes and precompiles, unlocking trustless execution for all use cases. Further, the specification for the arithmetization will be published, audited, and open to bug bounties to increase the security and reliability of the system.
The second cornerstone of this phase is the implementation of **100% EVM coverage** in the zkEVM
arithmetization. Linea will generate proofs of computation for all EVM opcodes and precompiles,
unlocking trustless execution for all use cases. The specification for the arithmetization
will be published, audited, and open to bug bounties to increase the security and reliability of
the system.

## Phase 2
## Phase 2

There are two significant components in this phase: **diversifying the Security Council**, and enabling **censorship-resistant withdrawals**.
There are two significant components in this phase: **diversifying the Security Council**, and
enabling **censorship-resistant withdrawals**.

**Diversifying the Security Council** forms the first part of this stage. The Security Council established during Linea's Mainnet Alpha launch plays a critical role in the oversight and control of the network. However, to prevent the concentration of power and potential bias, we plan to expand participation in the council, while also retaining a 6-of-8 multisig threshold (or stricter) for immediate upgrades. This modification ensures a balanced representation and fosters more robust collective decision-making, adding an additional layer of checks and balances to the system.
**Diversifying the Security Council** forms the first part of this stage. The Security Council
established during Linea's Mainnet Alpha launch plays a critical role in the oversight and control
of the network. However, to prevent the concentration of power and potential bias, we plan to expand
participation in the council, while also retaining a 6-of-8 multisig threshold (or stricter) for
immediate upgrades. This modification ensures a balanced representation and fosters more robust
collective decision-making, adding an additional layer of checks and balances to the system.

Closely tied to our principle of user sovereignty, enabling **censorship-resistant withdrawals** is a fundamental element of our roadmap. The architecture will be refined to prevent rollup operators from preventing user withdrawals. We will ensure that users can independently initiate exits, which guarantees continuous access to, and control over their assets on Linea. This assurance amplifies user confidence and upholds our commitment to ensuring users have sovereignty over their assets.
Closely tied to our principle of user sovereignty, enabling **censorship-resistant withdrawals** is
a fundamental element of our roadmap. The architecture will be refined to prevent rollup operators
from preventing user withdrawals. We will ensure that users can independently initiate exits, which
guarantees continuous access to, and control over their assets on Linea. This assurance amplifies
user confidence and upholds our commitment to ensuring users have sovereignty over their assets.

Through these initiatives, our Phase 2 aims to further decentralize power, enhance transparency, and boost the user experience, all while maintaining robust security and control measures.
Through these initiatives, our Phase 2 aims to further decentralize power, enhance transparency,
and boost the user experience, all while maintaining robust security and control measures.

## Phase 3

In this phase, we turn our focus to decentralizing the roles crucial to the functioning of the Linea ecosystem, as well as our governance system itself, thereby further reinforcing our commitment to trust minimization and decentralization.

The first part of this phase is **decentralizing operators**. At present, provers and sequencers, which generate zero-knowledge proofs and manage Layer 2 transactions respectively, are crucial roles within our ecosystem. By decentralizing these roles, we aim to significantly bolster the trust of our network participants and the overall integrity of our system. We acknowledge the technical complexities this may bring, such as potential latency, increased transaction costs, and potential MEV (maximum extractable value) issues. However, we are committed to navigating these challenges to shepherd forward a trustworthy, efficient platform for the community.

The second component of this phase is **decentralizing governance**. We believe that democratizing Linea's governance is key to our continued evolution. This approach fosters an equitable, transparent system where all stakeholders can participate and the future of Linea is steered by its user community. This shared governance not only mitigates unilateral decisions and the risk of a single point of failure but also reinforces the resilience of the network. In turn, this promotes collective ownership and trust among network participants, thereby enhancing the ecosystem's sustainable growth.
In this phase, we turn our focus to decentralizing the roles crucial to the functioning of the Linea
ecosystem, as well as our governance system itself, thereby further reinforcing our commitment to
trust minimization and decentralization.

The first part of this phase is **decentralizing operators**. At present, provers and sequencers,
which generate zero-knowledge proofs and manage Layer 2 transactions respectively, are crucial
roles within our ecosystem. By decentralizing these roles, we aim to significantly bolster the trust
of our network participants and the overall integrity of our system. We acknowledge the technical
complexities this may bring, such as potential latency, increased transaction costs, and potential
MEV (maximum extractable value) issues. However, we are committed to navigating these challenges to
shepherd forward a trustworthy, efficient platform for the community.

The second component of this phase is **decentralizing governance**. We believe that democratizing
Linea's governance is key to our continued evolution. This approach fosters an equitable,
transparent system where all stakeholders can participate and the future of Linea is steered by its
user community. This shared governance not only mitigates unilateral decisions and the risk of a
single point of failure but also reinforces the resilience of the network. In turn, this promotes
collective ownership and trust among network participants, thereby enhancing the ecosystem's
sustainable growth.

## Phase 4

The final phase of our roadmap, aims to further ensure the robustness of our ecosystem and mitigate trust-related risks through the implementation of a **multi-prover** and by **limiting governance powers**.

The EVM will continue to evolve as described in the Ethereum roadmap and will be driven by the larger Ethereum community and Ethereum Foundation. Therefore, in order to make changes to the Linea network at a reasonable pace and safeguard against implementation risk, we plan to incorporate multiple diverse implementations of a zkEVM prover, known as a **multi-prover** rollup. With each transaction on Linea verified by multiple heterogeneous implementations of the zkEVM, we can ensure that even if one prover encounters a bug or becomes unavailable, which is not improbable given the complexity, the system continues to operate uninterrupted. This approach not only boosts confidence in the reliability of our platform during a period where the EVM specification is constantly evolving but also encourages the exploration of innovative advancements, all while maintaining exceptional levels of system uptime.

Lastly, as part of our commitment to a robust and decentralized governance model limiting governance to where it is only necessary, we plan to **limit governance powers**. Upgrades to the rollup logic will be immutable, allowing upgrades only to be made to the verifier given a change in the EVM specification, of which users will be given reasonable notice to exit the rollup.

The role of the Security Council will be delineated to step in only in case of discrepancies or potential system issues, such as when the prover system disagrees or appears to be stuck. By implementing these measures, we hope to strike a balance between governance where necessary and the principles of decentralization.
The final phase of our roadmap, aims to further ensure the robustness of our ecosystem and mitigate
trust-related risks through the implementation of a **multi-prover** and by **limiting governance
powers**.

The EVM will continue to evolve as described in the Ethereum roadmap and will be driven by the
larger Ethereum community and Ethereum Foundation. Therefore, in order to make changes to the Linea
network at a reasonable pace and safeguard against implementation risk, we plan to incorporate
multiple diverse implementations of a zkEVM prover, known as a **multi-prover** rollup. With each
transaction on Linea verified by multiple heterogeneous implementations of the zkEVM, we can ensure
that even if one prover encounters a bug or becomes unavailable, which is not improbable given the
complexity, the system continues to operate uninterrupted. This approach not only boosts confidence
in the reliability of our platform during a period where the EVM specification is constantly
evolving but also encourages the exploration of innovative advancements, all while maintaining
exceptional levels of system uptime.

Lastly, as part of our commitment to a robust and decentralized governance model limiting governance
to where it is only necessary, we plan to **limit governance powers**. Upgrades to the rollup logic
will be immutable, allowing upgrades only to be made to the verifier given a change in the EVM
specification, of which users will be given reasonable notice to exit the rollup.

The role of the Security Council will be delineated to step in only in case of discrepancies or
potential system issues, such as when the prover system disagrees or appears to be stuck. By
implementing these measures, we hope to strike a balance between governance where necessary and the
principles of decentralization.
Loading

0 comments on commit 01e3d8f

Please sign in to comment.