From 84e5d19174c7e0f53896019a2e5bf61969026194 Mon Sep 17 00:00:00 2001 From: Dennis Date: Thu, 29 Feb 2024 15:59:51 +0100 Subject: [PATCH 01/10] chore(docs): reorganise learn section --- .../site/docs/learn/background/blockchains.md | 27 +++++++++++ docs/site/docs/learn/background/ethereum.md | 15 ++++++ .../docs/learn/background/fragmentation.md | 32 +++++++++++++ .../docs/learn/background/interoperability.md | 25 ++++++++++ docs/site/docs/learn/background/restaking.md | 42 +++++++++++++++++ docs/site/docs/learn/background/rollups.md | 21 +++++++++ docs/site/docs/learn/blockchains.md | 46 ------------------- docs/site/docs/learn/introduction/goal.md | 9 ++++ .../docs/learn/introduction/introduction.md | 11 +++++ .../vision.md} | 23 +--------- docs/site/docs/learn/omni/interoperability.md | 5 ++ docs/site/docs/learn/omni/restaking.md | 5 ++ docs/site/sidebars.ts | 28 ++++++++++- 13 files changed, 220 insertions(+), 69 deletions(-) create mode 100644 docs/site/docs/learn/background/blockchains.md create mode 100644 docs/site/docs/learn/background/ethereum.md create mode 100644 docs/site/docs/learn/background/fragmentation.md create mode 100644 docs/site/docs/learn/background/interoperability.md create mode 100644 docs/site/docs/learn/background/restaking.md create mode 100644 docs/site/docs/learn/background/rollups.md delete mode 100644 docs/site/docs/learn/blockchains.md create mode 100644 docs/site/docs/learn/introduction/goal.md create mode 100644 docs/site/docs/learn/introduction/introduction.md rename docs/site/docs/learn/{introduction.md => introduction/vision.md} (50%) create mode 100644 docs/site/docs/learn/omni/interoperability.md create mode 100644 docs/site/docs/learn/omni/restaking.md diff --git a/docs/site/docs/learn/background/blockchains.md b/docs/site/docs/learn/background/blockchains.md new file mode 100644 index 000000000..9716dfc41 --- /dev/null +++ b/docs/site/docs/learn/background/blockchains.md @@ -0,0 +1,27 @@ +--- +sidebar_position: 1 +--- + +# Blockchains + +The concept of modular blockchains is a mental model for building blockchains that has grown in popularity over the past few years in the crypto industry. Let's discuss the history of the idea, and how it's relevant to Omni. + +## Monolithic Blockchains + +Historically, blockchains were built in a monolithic fashion. Most Layer 1 blockchains were built as an "end to end" service – taking responsibility for all services that a blockchain must provide. Layer 1 solutions like Bitcoin and Ethereum were built in this fashion. + +As the industry evolved, new Layer 1s were developed that optimized their stacks to make different trade-offs in terms of security, scalability, and speed. Many of these new Layer 1s adopted the monolithic approach – optimizing the full chain stack to provide the optimal desired experience. Examples of these newer monolithic Layer 1s include [Solana](https://solana.com/), [Aptos](https://aptosfoundation.org/), and [Sui](https://sui.io/). + +## Modular Blockchains + +However, as time has passed the latest innovations have grown to more closely reflect the architecture of microservices in the traditional software engineering world. Blockchain developers realized that we could decouple the various components that make up a blockchain and optimize them independently. + +This approach was first proposed in Ethereum's rollup-centric roadmap, and more recently has been popularized by projects such as [Arbitrum](https://arbitrum.io/), [Celestia](https://celestia.org/) and now Omni. + +### Components + +Today, our understanding of blockchains has led us to disambiguate the stack into three primary components, broadly speaking: + +- **Data Availability**: ensuring that a blockchain's transaction data is available to network participants at block proposal time (read further [here](https://ethereum.org/en/developers/docs/data-availability/)). +- **Execution**: running a blockchain's state transition function (STF) on the input data (transactions from the Data Availability module) and computing its output. +- **Consensus**: mechanism for nodes to agree on the computed output of the execution layer (and optionally finalizing the chain's state). diff --git a/docs/site/docs/learn/background/ethereum.md b/docs/site/docs/learn/background/ethereum.md new file mode 100644 index 000000000..ebe3edc42 --- /dev/null +++ b/docs/site/docs/learn/background/ethereum.md @@ -0,0 +1,15 @@ +--- +sidebar_position: 2 +--- + +# Ethereum's Roadmap + +As the Ethereum ecosystem developed, we learned that scaling transaction throughput and decreasing costs would be extraordinarily difficult on Layer 1 Ethereum while maintaining its high security. Over time, various proposals have attempted to solve this problem: state channels, side chains, and plasma to name a few. However, each of these options came with unfortunate trade-offs that typically sacrificed security to achieve these goals. But their development was not in vain! They led to the growth of rollups, the currently agreed upon optimal solution for scaling Ethereum. + +## Rollup-Centric Roadmap + +Hence, the [rollup-centric roadmap](https://ethereum-magicians.org/t/a-rollup-centric-ethereum-roadmap/4698) was proposed. + +Today, Ethereum Layer 1 handles Data Availability, Execution, and Consensus. But over time, Ethereum will primarily become a Data Availability layer. Rollups will handle execution off-chain, and utilize either Ethereum's smart contract layer, or their own sovereign settlement layer, for consensus. This allows rollups (Layer 2s) to borrow Ethereum security while scaling throughput and decreasing cost. Upgrades like [EIP-4844](https://www.eip4844.com/) will even further improve Ethereum as a Data Availability layer by providing the service at lower cost. + +You can view the growth of rollup ecosystems at [L2Beat.com](https://l2beat.com/), a great resource for understanding the security trade-offs, current state of development, and adoption levels for rollups. diff --git a/docs/site/docs/learn/background/fragmentation.md b/docs/site/docs/learn/background/fragmentation.md new file mode 100644 index 000000000..5ce44c21c --- /dev/null +++ b/docs/site/docs/learn/background/fragmentation.md @@ -0,0 +1,32 @@ +--- +sidebar_position: 4 +--- + +# Fragmentation + +As rollups have become increasingly popular for scaling blockchain networks, a new challenge has emerged: fragmentation of users and liquidity. While rollups enhance performance by processing transactions off the main chain, they often operate in isolation from one another. This isolation can lead to siloed ecosystems where assets and interactions are confined to individual rollups, hindering the potential for broader interoperability and network effects. + +## The Fragmentation Challenge + +Fragmentation can manifest in several ways: + +- **Liquidity Split**: Assets are spread across multiple rollups, which can dilute the liquidity and make it harder for users to access the full value of the network. +- **User Experience**: With different rollups offering various features, users may have to navigate complex processes to move assets or data between them, impacting usability. +- **Developer Complexity**: Building applications that span multiple rollups requires dealing with disparate systems, which can increase development time and costs. + +## Omni's Approach to Unification + +The Omni protocol aims to address these fragmentation challenges by enabling seamless communication and interoperability between different rollups. Here's how Omni contributes to a more unified blockchain ecosystem: + +- **Cross-Rollup Communication**: Omni allows users and applications to interact across various rollups as if they were a single, cohesive network. +- **Unified Liquidity Pools**: By facilitating cross-rollup transactions, Omni helps aggregate liquidity, improving capital efficiency and reducing slippage for users. +- **Simplified User Journeys**: Users can enjoy a smoother experience with the ability to move assets or execute actions across rollups without complex processes or multiple steps. +- **Developer-Friendly Platform**: Developers can build applications with the confidence that they will work across the entire rollup ecosystem, thanks to Omni's standardized communication protocols. + +## Looking Forward + +The vision for the future is an interconnected blockchain landscape where fragmentation is a thing of the past. Rollups will continue to play a critical role in scaling, and protocols like Omni are key to ensuring that the ecosystem remains unified and user-friendly. + +For more information on how Omni tackles fragmentation and promotes a cohesive blockchain environment read further on [Omni's vision](../introduction/vision.md) and [EigenLayer's enhancing of security through restaking](https://eigenlayer.com/). + +Omni is dedicated to bridging the gaps between isolated rollups, fostering a more connected and powerful blockchain infrastructure. Through its innovative protocols, Omni is paving the way for a future where the full potential of blockchain can be realized without the barriers of fragmentation. diff --git a/docs/site/docs/learn/background/interoperability.md b/docs/site/docs/learn/background/interoperability.md new file mode 100644 index 000000000..330e5b88c --- /dev/null +++ b/docs/site/docs/learn/background/interoperability.md @@ -0,0 +1,25 @@ +--- +sidebar_position: 5 +--- + +# Interoperability + +Interoperability is the ability of different blockchain networks to communicate and interact with one another seamlessly. It's a foundational element for building a connected and accessible decentralized ecosystem. By allowing different chains to exchange information and value, interoperability breaks down barriers, enabling a more versatile and cohesive blockchain experience. + +## Why Interoperability Matters + +The rise of multiple blockchain networks, each with its unique features and advantages, has led to a fragmented landscape. Interoperability is critical in this context for several reasons: + +- **Enhanced User Experience**: Users can transact across chains without needing multiple wallets or accounts, streamlining the user experience. +- **Increased Network Effects**: Interoperability allows networks to leverage each other's strengths, leading to greater adoption and utility. +- **Combined Liquidity**: It consolidates liquidity from various networks, improving market efficiency and reducing slippage for traders. + +## Omni: Bridging Chains + +Omni addresses the need for interoperability by providing a protocol that facilitates cross-chain communication. It enables different blockchain networks to work together, creating a web of interconnected chains. + +### Key Features of Omni's Interoperability: + +- **Cross-Chain Communication**: Omni allows for the transfer of data and assets between chains, fostering collaboration and interaction between distinct blockchain ecosystems. +- **Unified Development Platform**: Developers can create applications that operate across multiple chains, reducing complexity and development time. +- **Security, Transparency and Trust**: With the integration of EigenLayer's restaking model, Omni ensures that cross-chain interactions maintain a high level of security and reliability. diff --git a/docs/site/docs/learn/background/restaking.md b/docs/site/docs/learn/background/restaking.md new file mode 100644 index 000000000..a6142672d --- /dev/null +++ b/docs/site/docs/learn/background/restaking.md @@ -0,0 +1,42 @@ +--- +sidebar_position: 6 +--- + +# What is Restaking? + +Restaking is a transformative concept in blockchain security, introduced by EigenLayer, a protocol built on Ethereum. It represents a new cryptoeconomic security primitive allowing the reuse of staked **\$ETH** to extend cryptoeconomic security to a wide array of applications on the network. + +## Introducing EigenLayer + +EigenLayer is a groundbreaking protocol that unlocks the potential of staked **\$ETH**, enabling it to secure additional services beyond the consensus layer. It allows users to restake their native **\$ETH** or liquid staking tokens (LSTs) through smart contracts, thereby contributing to the security of various applications while earning additional rewards. + +### Why Restaking Matters + +Restaking through EigenLayer has several significant advantages: + +- **Pooled Security**: Ethereum stakers can restake their staked **\$ETH** to provide pooled security across multiple services, reducing capital costs and elevating trust guarantees for each service. +- **Fragmentation Solution**: By allowing any service to tap into Ethereum's staked security, EigenLayer addresses the fragmentation of security efforts, fostering a cohesive ecosystem for decentralized services. +- **Permissionless Innovation**: EigenLayer's environment supports the seamless introduction of new services, enabling permissionless innovation and free-market governance where stakers choose which services to secure based on their risk-reward preferences. + +## EigenLayer: A Hub of Decentralized Services + +EigenLayer supports a variety of actively validated services (AVS), including but not limited to: + +- Sidechains +- Oracle networks +- Data availability layers +- Bridges and keeper networks + +### Core Features of EigenLayer + +- **Liquid Staking**: Users can stake their **\$ETH** and receive LSTs, which can be traded or redeemed, allowing for liquidity and participation in DeFi ecosystems. +- **Native and LST Restaking**: Stakers can opt to restake their assets natively or use LSTs to secure additional services within EigenLayer's framework. +- **Delegation and Operators**: Stakers can delegate their staked assets to operators who run the infrastructure required for EigenLayer services, simplifying participation for those who may not wish to operate the software themselves. + +## Securing the Future + +EigenLayer's innovative approach to restaking and its on-chain slashing mechanisms ensure robust security aligned with the principles of decentralized governance. As a result, EigenLayer sets the stage for a more secure, efficient, and unified blockchain ecosystem. + +For an in-depth understanding of restaking and the EigenLayer protocol read more in the [EigenLayer Documentation](https://docs.eigenlayer.xyz/eigenlayer/overview/). + +EigenLayer is redefining the landscape of blockchain security by enabling stakers to contribute to the security of the entire network, ushering in a new era of interconnectedness and mutual growth. diff --git a/docs/site/docs/learn/background/rollups.md b/docs/site/docs/learn/background/rollups.md new file mode 100644 index 000000000..4ab3f2bb2 --- /dev/null +++ b/docs/site/docs/learn/background/rollups.md @@ -0,0 +1,21 @@ +--- +sidebar_position: 3 +--- + +# Rollups + +Rollups are a type of layer 2 solution that aim to enhance the scalability and efficiency of blockchain networks. They do so by processing transactions outside the main blockchain (off-chain) and then posting the transaction data (on-chain) in a compressed form. This method significantly reduces the strain on the network, allowing for faster and cheaper transactions. Rollups are pivotal to the Omni protocol's ability to facilitate seamless cross-rollup communication. + +There are mainly two types of rollups that differ in how transaction data is processed and verified: **Optimistic Rollups** and **ZK-Rollups**. + +## Optimistic Rollups + +Optimistic Rollups assume transactions are valid by default and only perform computation, and hence incur expenses, when a transaction is challenged. They offer a significant increase in scalability by running computation off-chain and posting the transaction data on-chain. Users or "watchers" can challenge a transaction if they believe it to be fraudulent. + +[Learn more about Optimistic Rollups](https://ethereum.org/en/developers/docs/scaling/optimistic-rollups/) + +## ZK-Rollups + +ZK-Rollups, or Zero-Knowledge Rollups, bundle hundreds of transfers into a single transaction. Instead of publishing all data on the chain, they generate a cryptographic proof known as a SNARK (Succinct Non-interactive Argument of Knowledge). This proof confirms the validity of all transactions in the bundle. ZK-Rollups are highly efficient, as they allow the network to confirm the legitimacy of transactions without executing them fully. + +[Discover more about ZK-Rollups](https://ethereum.org/en/developers/docs/scaling/zk-rollups/) diff --git a/docs/site/docs/learn/blockchains.md b/docs/site/docs/learn/blockchains.md deleted file mode 100644 index 31478b694..000000000 --- a/docs/site/docs/learn/blockchains.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -sidebar_position: 2 -id: blockchains ---- - -# Blockchain Background - -The concept of modular blockchains is a mental model for building blockchains that has grown in popularity over the past few years in the crypto industry. Let's discuss the history of the idea, and how it's relevant to Omni. - -## Monolithic Blockchains - -Historically, blockchains were built in a monolithic fashion. Most Layer 1 blockchains were built as an "end to end" service – taking responsibility for all services that a blockchain must provide. Layer 1 solutions like Bitcoin and Ethereum were built in this fashion. - -As the industry evolved, new Layer 1s were developed that optimized their stacks to make different trade-offs in terms of security, scalability, and speed. Many of these new Layer 1s adopted the monolithic approach – optimizing the full chain stack to provide the optimal desired experience. Examples of these newer monolithic Layer 1s include [Solana](https://solana.com/), [Aptos](https://aptosfoundation.org/), and [Sui](https://sui.io/). - -## Modular Blockchains - -However, as time has passed the latest innovations have grown to more closely reflect the architecture of microservices in the traditional software engineering world. Blockchain developers realized that we could decouple the various components that make up a blockchain and optimize them independently. - -This approach was first proposed in Ethereum's rollup-centric roadmap, and more recently has been popularized by projects such as [Arbitrum](https://arbitrum.io/), [Celestia](https://celestia.org/) and now Omni. - -### Components - -Today, our understanding of blockchains has led us to disambiguate the stack into three primary components, broadly speaking: - -- **Data Availability**: ensuring that a blockchain's transaction data is available to network participants at block proposal time (read further [here](https://ethereum.org/en/developers/docs/data-availability/)). -- **Execution**: running a blockchain's state transition function (STF) on the input data (transactions from the Data Availability module) and computing its output. -- **Consensus**: mechanism for nodes to agree on the computed output of the execution layer (and optionally finalizing the chain's state). - -## Ethereum and Rollups - -As the Ethereum ecosystem developed, we learned that scaling transaction throughput and decreasing costs would be extraordinarily difficult on Layer 1 Ethereum while maintaining its high security. Over time, various proposals have attempted to solve this problem: state channels, side chains, and plasma to name a few. However, each of these options came with unfortunate trade-offs that typically sacrificed security to achieve these goals. But their development was not in vain! They led to the growth of rollups, the currently agreed upon optimal solution for scaling Ethereum. - -Hence, the [rollup-centric roadmap](https://ethereum-magicians.org/t/a-rollup-centric-ethereum-roadmap/4698) was proposed. - -Today, Ethereum Layer 1 handles Data Availability, Execution, and Consensus. But over time, Ethereum will primarily become a Data Availability layer. Rollups will handle execution off-chain, and utilize either Ethereum's smart contract layer, or their own sovereign settlement layer, for consensus. This allows rollups (Layer 2s) to borrow Ethereum security while scaling throughput and decreasing cost. Upgrades like [EIP-4844](https://www.eip4844.com/) will even further improve Ethereum as a Data Availability layer by providing the service at lower cost. - -You can view the growth of rollup ecosystems at [L2Beat.com](https://l2beat.com/), a great resource for understanding the security trade-offs, current state of development, and adoption levels for rollups. - -## Omni - -The modular stack is relevant to Omni in several ways. - -Omni is a solution to the vast proliferation of rollups that has resulted in user and liquidity fragmentation. It offers a platform for developers to *aggregate* their users and liquidity across rollups, rather than *fragment* it. - -In addition so solving problems introduced by the modular stack, Omni's architecture is inspired by the it. In particular, the Omni chain is defined by a Consensus Layer and an Execution Layer, that communicate through the Engine API – the same one as Ethereum Layer 1. Read more about this in our [architecture docs](../protocol/introduction.md). diff --git a/docs/site/docs/learn/introduction/goal.md b/docs/site/docs/learn/introduction/goal.md new file mode 100644 index 000000000..bbee8338a --- /dev/null +++ b/docs/site/docs/learn/introduction/goal.md @@ -0,0 +1,9 @@ +--- +sidebar_position: 3 +--- + +# Goal + +> **The goal of Omni is to pair an innovative security model with a novel, modular architecture to provide the highest performance interoperability network for rollup application developers.** + +Omni is a blockchain specifically designed to unify Ethereum's rollups, mitigating fragmentation by [restaking](../protocol/restaking/restaking.md) for enhanced security and simplicity, allowing developers to create cross-rollup applications effortlessly. It pioneers the use of ETH restaking to bolster security, streamlining the development process by abstracting cross-rollup complexities from users and developers. As the Ethereum ecosystem grows and diversifies, Omni positions itself as the essential infrastructure to support Ethereum's modular evolution, offering a seamless development experience amidst a landscape of increasing rollup networks. diff --git a/docs/site/docs/learn/introduction/introduction.md b/docs/site/docs/learn/introduction/introduction.md new file mode 100644 index 000000000..79823dd3c --- /dev/null +++ b/docs/site/docs/learn/introduction/introduction.md @@ -0,0 +1,11 @@ +--- +sidebar_position: 1 +--- + +# About + +Omni is a high performance, high security interoperability network built to aggregate users, liquidity and activity from all rollups, providing developers with the best platform to build cross-rollup applications. + +Omni is the future of interoperability for the Ethereum ecosystem that allows developers to build applications that are available across all rollups without fragmenting their liquidity. + +Omni abstracts away the complexity of building cross-rollup applications by establishing a global storage layer to manage cross-domain applications, accessing liquidity and users across every ecosystem.Developers can work in a familiar environment – the EVM – and don't need to worry about distributed state management. Instead of fragmenting liquidity, application developers can aggregate it across domains, meeting users where they are and creating a smooth product experience. diff --git a/docs/site/docs/learn/introduction.md b/docs/site/docs/learn/introduction/vision.md similarity index 50% rename from docs/site/docs/learn/introduction.md rename to docs/site/docs/learn/introduction/vision.md index 10a6bc994..1cd94ca01 100644 --- a/docs/site/docs/learn/introduction.md +++ b/docs/site/docs/learn/introduction/vision.md @@ -1,21 +1,8 @@ --- -sidebar_position: 1 -id: introduction +sidebar_position: 2 --- -# Introduction - -## About Omni - -Omni is a high performance, high security interoperability network built to aggregate users, liquidity and activity from all rollups, providing developers with the best platform to build cross-rollup applications. - -Omni is the future of interoperability for the Ethereum ecosystem that allows developers to build applications that are available across all rollups without fragmenting their liquidity. - -Omni abstracts away the complexity of building cross-rollup applications by establishing a global storage layer to manage cross-domain applications, accessing liquidity and users across every ecosystem.Developers can work in a familiar environment – the EVM – and don't need to worry about distributed state management. Instead of fragmenting liquidity, application developers can aggregate it across domains, meeting users where they are and creating a smooth product experience. - -## Vision - -### Background +# Vision The challenges stemming from rollup fragmentation underscore the need for robust interoperability solutions to facilitate connections between rollup networks. @@ -24,9 +11,3 @@ Past interop networks have been significantly constrained by their dependence on Externally verified interoperability protocols provide a scalable framework for arbitrary message passing between a wide range of networks. However, outsourcing the responsibilities of verification creates additional trust assumptions for the system. To mitigate these new trust assumptions, protocols can introduce cryptoeconomic security measures that require the verification set to commit capital that is at risk of being slashed in the event of misconduct. Interoperability protocols that choose to implement this model can be considered game-theoretically secure so long as the staked value of their verifier set is greater than the value that the verifier set can transfer in a single state transition period. These drawbacks underscore the need for a new approach that is capable of achieving secure interoperability at scale, effectively addressing the foundational gaps in existing solutions. - -### Goal - -> **The goal of Omni is to pair an innovative security model with a novel, modular architecture to provide the highest performance interoperability network for rollup application developers.** - -Omni is a blockchain specifically designed to unify Ethereum's rollups, mitigating fragmentation by [restaking](../protocol/restaking/restaking.md) for enhanced security and simplicity, allowing developers to create cross-rollup applications effortlessly. It pioneers the use of ETH restaking to bolster security, streamlining the development process by abstracting cross-rollup complexities from users and developers. As the Ethereum ecosystem grows and diversifies, Omni positions itself as the essential infrastructure to support Ethereum's modular evolution, offering a seamless development experience amidst a landscape of increasing rollup networks. diff --git a/docs/site/docs/learn/omni/interoperability.md b/docs/site/docs/learn/omni/interoperability.md new file mode 100644 index 000000000..345475ef8 --- /dev/null +++ b/docs/site/docs/learn/omni/interoperability.md @@ -0,0 +1,5 @@ +--- +sidebar_position: 1 +--- + +# Rollup Interoperability diff --git a/docs/site/docs/learn/omni/restaking.md b/docs/site/docs/learn/omni/restaking.md new file mode 100644 index 000000000..2db7bd4da --- /dev/null +++ b/docs/site/docs/learn/omni/restaking.md @@ -0,0 +1,5 @@ +--- +sidebar_position: 1 +--- + +# Restaking to Omni diff --git a/docs/site/sidebars.ts b/docs/site/sidebars.ts index 32449478a..2e790eea8 100644 --- a/docs/site/sidebars.ts +++ b/docs/site/sidebars.ts @@ -3,8 +3,32 @@ import type { SidebarsConfig } from "@docusaurus/plugin-content-docs"; const sidebars: SidebarsConfig = { learnSidebar: [ { - type: "autogenerated", - dirName: "learn", + type: "category", + label: "Introduction", + className: "sidebar-title", + collapsible: false, + items: [ + { + type: "autogenerated", + dirName: "learn/introduction", + } + ] + }, + { + type: "html", + value: "
", + }, + { + type: "category", + label: "Background", + className: "sidebar-title", + collapsible: false, + items: [ + { + type: "autogenerated", + dirName: "learn/background", + } + ] }, { type: "html", From 0c512361e3db0f0612bb4d8725be4b13921e92e4 Mon Sep 17 00:00:00 2001 From: Dennis Date: Thu, 29 Feb 2024 17:17:52 +0100 Subject: [PATCH 02/10] chore(docs): further learn reorg and add restaking docs --- docs/site/docs/learn/omni/architecture.md | 5 +++ docs/site/docs/learn/omni/cometbft.md | 5 +++ docs/site/docs/learn/omni/consensus.md | 5 +++ docs/site/docs/learn/omni/evm.md | 5 +++ docs/site/docs/learn/omni/gas.md | 5 +++ docs/site/docs/learn/omni/interoperability.md | 2 +- docs/site/docs/learn/omni/restaking.md | 34 +++++++++++++++++++ 7 files changed, 60 insertions(+), 1 deletion(-) create mode 100644 docs/site/docs/learn/omni/architecture.md create mode 100644 docs/site/docs/learn/omni/cometbft.md create mode 100644 docs/site/docs/learn/omni/consensus.md create mode 100644 docs/site/docs/learn/omni/evm.md create mode 100644 docs/site/docs/learn/omni/gas.md diff --git a/docs/site/docs/learn/omni/architecture.md b/docs/site/docs/learn/omni/architecture.md new file mode 100644 index 000000000..c66813402 --- /dev/null +++ b/docs/site/docs/learn/omni/architecture.md @@ -0,0 +1,5 @@ +--- +sidebar_position: 6 +--- + +# Dual-Chain Architecture diff --git a/docs/site/docs/learn/omni/cometbft.md b/docs/site/docs/learn/omni/cometbft.md new file mode 100644 index 000000000..8ad2ae06a --- /dev/null +++ b/docs/site/docs/learn/omni/cometbft.md @@ -0,0 +1,5 @@ +--- +sidebar_position: 5 +--- + +# CometBFT diff --git a/docs/site/docs/learn/omni/consensus.md b/docs/site/docs/learn/omni/consensus.md new file mode 100644 index 000000000..d0a501492 --- /dev/null +++ b/docs/site/docs/learn/omni/consensus.md @@ -0,0 +1,5 @@ +--- +sidebar_position: 7 +--- + +# Parallelized Consensus diff --git a/docs/site/docs/learn/omni/evm.md b/docs/site/docs/learn/omni/evm.md new file mode 100644 index 000000000..0d7b66d89 --- /dev/null +++ b/docs/site/docs/learn/omni/evm.md @@ -0,0 +1,5 @@ +--- +sidebar_position: 3 +--- + +# EVM diff --git a/docs/site/docs/learn/omni/gas.md b/docs/site/docs/learn/omni/gas.md new file mode 100644 index 000000000..be62f62af --- /dev/null +++ b/docs/site/docs/learn/omni/gas.md @@ -0,0 +1,5 @@ +--- +sidebar_position: 4 +--- + +# Gas Abstraction diff --git a/docs/site/docs/learn/omni/interoperability.md b/docs/site/docs/learn/omni/interoperability.md index 345475ef8..bd8184d3d 100644 --- a/docs/site/docs/learn/omni/interoperability.md +++ b/docs/site/docs/learn/omni/interoperability.md @@ -1,5 +1,5 @@ --- -sidebar_position: 1 +sidebar_position: 2 --- # Rollup Interoperability diff --git a/docs/site/docs/learn/omni/restaking.md b/docs/site/docs/learn/omni/restaking.md index 2db7bd4da..0b584410f 100644 --- a/docs/site/docs/learn/omni/restaking.md +++ b/docs/site/docs/learn/omni/restaking.md @@ -3,3 +3,37 @@ sidebar_position: 1 --- # Restaking to Omni + +## Enhancing Security with Staked **\$ETH** + +The Omni protocol introduces a groundbreaking approach to blockchain security through the innovative use of restaked **\$ETH**. This process involves validators and delegators working in tandem to verify protocol messages, manage reward and slashing events, and maintain the integrity of the validator set. Here, we explore how restaking contributes to the robust security of the Omni network. + +## The Role of Validators and Delegators + +In the Omni network, **validators** have the critical job of verifying the authenticity of protocol messages and managing the network's staking balances and voting powers. **Delegators**, on the other hand, support the network by delegating their restaked **\$ETH** to validators of their choice, thereby contributing to the overall security and efficiency of the network. + +## How Restaking Works + +Omni's staking implementation is supported by a suite of smart contracts designed to facilitate the staking process: + +- **Omni Staking Contract**: Implemented on the Omni EVM, this contract tracks each validator’s stake and delegations, distributes rewards, and manages slashing events. +- **Omni AVS Contract**: Located on Ethereum L1, it registers Omni as an application with the EigenLayer protocol, enabling operators to provide validation services to the Omni blockchain. +- **Omni Portal Contracts**: Deployed on the Omni EVM and connected rollup VMs, these contracts maintain a record of the Omni validator set’s stake, delegations, and voting power. + +## Securing the Omni Chain with Restaked **\$ETH** + +Restaking **\$ETH** to secure the Omni chain leverages the existing cryptoeconomic security of the Ethereum network. By allowing Ethereum stakers to restake their **\$ETH** within the Omni ecosystem, Omni can tap into Ethereum's substantial security budget, significantly enhancing its own security without the limitations faced by other interoperability solutions. + +### Dual Staking Mechanism + +Omni employs a dual staking mechanism that combines restaked **\$ETH** and staked **\$OMNI** tokens, offering a layered security model. This approach not only allows Omni to inherit Ethereum's vast security resources but also enables it to scale its security budget over time as more OMNI tokens are staked. + +### Communication and Updates + +Omni uses its XMsg format to communicate staking events. Validators and delegators stay informed about stake changes and delegation updates through the Omni staking and AVS contracts, ensuring the network remains responsive and secure. + +## The Impact of Restaking + +The restaking model allows Omni to establish a new standard in protocol safety, offering security guarantees that are orders of magnitude higher than existing solutions. It facilitates a secure, decentralized environment for validators and delegators to contribute to the network's integrity, paving the way for a more interconnected and resilient blockchain ecosystem. + +By integrating restaked **\$ETH** into its security model, Omni is setting a precedent for how blockchain networks can leverage existing assets to bootstrap and enhance their security, driving forward the vision of a secure, interconnected blockchain future. From b68d564fe03fe31c2e7df67a7ff1cf634089f080 Mon Sep 17 00:00:00 2001 From: Dennis Date: Thu, 29 Feb 2024 17:23:01 +0100 Subject: [PATCH 03/10] chore(docs): learn omni interop --- docs/site/docs/learn/omni/interoperability.md | 22 +++++++++++++++++++ docs/site/sidebars.ts | 20 +++++++++++++++-- 2 files changed, 40 insertions(+), 2 deletions(-) diff --git a/docs/site/docs/learn/omni/interoperability.md b/docs/site/docs/learn/omni/interoperability.md index bd8184d3d..17410aa58 100644 --- a/docs/site/docs/learn/omni/interoperability.md +++ b/docs/site/docs/learn/omni/interoperability.md @@ -3,3 +3,25 @@ sidebar_position: 2 --- # Rollup Interoperability + +At the heart of Omni's mission is the enablement of seamless interoperability between different blockchain networks, particularly focusing on rollup technologies. This capability is essential for creating a cohesive and efficient blockchain ecosystem where assets, information, and applications can freely move across chains. + +## Breaking Down Barriers + +Traditionally, blockchain networks operate in isolation, creating silos that limit the interaction between different ecosystems. Omni addresses this challenge by providing the necessary infrastructure for rollups to communicate and transact with one another without friction. + +### What is Rollup Interoperability? + +Rollup interoperability refers to the ability of different rollup solutions, such as Optimistic Rollups and ZK-Rollups, to interact and exchange data. This interaction enables: + +- **Cross-chain Transactions**: Users can perform transactions across different blockchain networks, enhancing liquidity and accessibility. +- **Unified Applications**: Developers can create decentralized applications (dApps) that leverage the strengths of multiple chains, offering users a richer experience. +- **Shared Security Model**: By enabling rollups to interoperate, Omni contributes to a shared security model, where the security of one network can benefit others. + +## Omni's Approach to Interoperability + +Omni's protocol leverages advanced cryptographic techniques and smart contract functionality to ensure secure and efficient cross-rollup communication. Key features include: + +- **XMsg Format**: Omni utilizes a specialized message format, XMsg, designed to standardize and secure the transfer of data between rollups. +- **Portal Contracts**: Deployed across connected rollups, these contracts facilitate the verification and execution of cross-chain transactions. +- **EigenLayer Integration**: By building on top of the EigenLayer protocol, Omni extends the cryptoeconomic security of Ethereum to support interconnected rollup operations. diff --git a/docs/site/sidebars.ts b/docs/site/sidebars.ts index 2e790eea8..2c6252728 100644 --- a/docs/site/sidebars.ts +++ b/docs/site/sidebars.ts @@ -6,7 +6,7 @@ const sidebars: SidebarsConfig = { type: "category", label: "Introduction", className: "sidebar-title", - collapsible: false, + collapsible: true, items: [ { type: "autogenerated", @@ -22,7 +22,7 @@ const sidebars: SidebarsConfig = { type: "category", label: "Background", className: "sidebar-title", - collapsible: false, + collapsible: true, items: [ { type: "autogenerated", @@ -34,6 +34,22 @@ const sidebars: SidebarsConfig = { type: "html", value: "
", }, + { + type: "category", + label: "Omni", + className: "sidebar-title", + collapsible: true, + items: [ + { + type: "autogenerated", + dirName: "learn/omni", + } + ] + }, + { + type: "html", + value: "
", + }, { type: "doc", id: "resources/glossary", From b61d16bb4debf0d759ea90b7ab50a8b74d627c1c Mon Sep 17 00:00:00 2001 From: Dennis Date: Thu, 29 Feb 2024 17:25:20 +0100 Subject: [PATCH 04/10] chore(docs): learn omni evm --- docs/site/docs/learn/omni/evm.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/site/docs/learn/omni/evm.md b/docs/site/docs/learn/omni/evm.md index 0d7b66d89..4cbf362e5 100644 --- a/docs/site/docs/learn/omni/evm.md +++ b/docs/site/docs/learn/omni/evm.md @@ -3,3 +3,29 @@ sidebar_position: 3 --- # EVM + +## Enhancing Global Programmability with Omni's EVM + +The Ethereum Virtual Machine (EVM) stands as a cornerstone of decentralized application (dApp) development, providing a sandboxed environment for executing smart contracts. Omni elevates this concept by implementing its own EVM, aiming to achieve global programmability across its network. This initiative ensures developers and users can interact with a unified, secure, and efficient ecosystem. + +## The Essence of EVM in Omni + +At its core, Omni's EVM integration signifies a commitment to interoperability and standardization, enabling: + +- **Seamless Smart Contract Deployment**: Developers can write and deploy smart contracts just as they would on Ethereum, utilizing Solidity or Vyper, thus lowering the barrier to entry for creating cross-chain applications. +- **Unified Development Experience**: Omni's EVM provides a consistent environment for dApp development, removing the need to adapt to disparate blockchain architectures. +- **Cross-Chain Functionality**: By embedding an EVM, Omni facilitates not just communication but also complex interactions and transactions across different blockchain networks. + +## Expanding the EVM Ecosystem + +Omni's approach extends the reach of EVM-compatible smart contracts, allowing for: + +- **Global State Management**: The Omni EVM can interact with states across various rollups and chains, offering a broader context for smart contracts. +- **Enhanced Security and Performance**: Leveraging the EigenLayer protocol, Omni enhances the EVM's cryptoeconomic security model while optimizing for performance and scalability. +- **Innovative Application Scenarios**: With global programmability, developers can envision and realize applications that operate on a truly interoperable scale, from decentralized finance (DeFi) to non-fungible tokens (NFTs) and beyond. + +## The Future Powered by Omni's EVM + +By integrating an EVM, Omni is not just bridging networks; it's fostering a paradigm where the entire blockchain landscape can operate as a cohesive and fluid ecosystem. This vision of global programmability empowers developers to build applications that are both innovative and universally accessible, driving the next wave of blockchain adoption. + +Omni's EVM represents a leap towards realizing the full potential of blockchain technology, enabling a world where networks are not just interoperable but universally programmable. From b6372e0af80eca5e93eb12233711e5a914aae4e6 Mon Sep 17 00:00:00 2001 From: Dennis Date: Thu, 29 Feb 2024 17:31:45 +0100 Subject: [PATCH 05/10] chore(docs): learn omni gas abstraction --- docs/site/docs/learn/omni/gas.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/docs/site/docs/learn/omni/gas.md b/docs/site/docs/learn/omni/gas.md index be62f62af..5ebf380b9 100644 --- a/docs/site/docs/learn/omni/gas.md +++ b/docs/site/docs/learn/omni/gas.md @@ -3,3 +3,25 @@ sidebar_position: 4 --- # Gas Abstraction + +## Simplifying Transaction Fees Across Rollups + +In the evolving landscape of blockchain networks, managing transaction fees across multiple chains and rollups can be a daunting task for users. Omni addresses this challenge head-on with its innovative gas abstraction feature, allowing users to pay transaction fees on any rollup, regardless of where their funds are located. This concept, metaphorically encapsulated by the phrase "Omni is oil," revolutionizes how transaction costs are handled, making cross-chain interactions seamless and user-friendly. + +## The Challenge of Cross-Rollup Transaction Fees + +Traditionally, executing transactions on different rollups or chains requires users to have the native token of each network to pay for gas fees. This requirement complicates the user experience, especially in a multi-chain environment where users interact with various decentralized applications (dApps) spread across multiple platforms. + +## Omni's Solution: Universal Fee Payment + +Omni's gas abstraction mechanism introduces a streamlined approach: + +- **Unified Fee Payment**: Users can pay transaction fees with a single token, regardless of the rollup or chain on which the transaction occurs. This simplification enhances accessibility and usability across the blockchain ecosystem. +- **Flexibility and Convenience**: Whether users hold their funds on Ethereum, an Optimistic Rollup, a ZK-Rollup, or any other connected network, they can seamlessly transact without worrying about specific gas tokens for each network. +- **$\OMNI is Oil**: Drawing an analogy with oil powering various engines seamlessly, Omni acts as a universal 'fuel' for the blockchain world, powering transactions across different networks without the friction of multiple currencies. + +## Empowering Users and Developers + +Gas abstraction not only simplifies the user experience but also empowers developers by broadening the potential audience for their dApps. Developers can design applications that are truly chain-agnostic, knowing that gas fees won't be a barrier for users engaging with their platforms. [Learn more about understanding Blockchain transaction fees here](https://ethereum.org/en/developers/docs/gas/) + +With **\$OMNI** as oil, the protocol is setting a new standard for how transaction fees are managed in a multi-chain future, ensuring that blockchain technology is more accessible and user-friendly than ever before. From af75ba79f9b051312180442cceb2178184a16c60 Mon Sep 17 00:00:00 2001 From: Dennis Date: Thu, 29 Feb 2024 17:40:51 +0100 Subject: [PATCH 06/10] chore(docs): learn omni cometbft --- docs/site/docs/learn/omni/cometbft.md | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/docs/site/docs/learn/omni/cometbft.md b/docs/site/docs/learn/omni/cometbft.md index 8ad2ae06a..cb89c6f9f 100644 --- a/docs/site/docs/learn/omni/cometbft.md +++ b/docs/site/docs/learn/omni/cometbft.md @@ -2,4 +2,22 @@ sidebar_position: 5 --- -# CometBFT +# CometBFT: Consensus Engine + +At the core of Omni's robust and efficient blockchain infrastructure is CometBFT, a battle-tested consensus algorithm that powers the Omni consensus chain. Drawing from years of research and real-world application, CometBFT offers a secure and scalable foundation for Omni's cross-chain communication protocol. + +## What is CometBFT? + +CometBFT is a Byzantine Fault Tolerant (BFT) consensus mechanism designed to ensure network agreement in a distributed system, even in the presence of faulty or malicious nodes. Its resilience and efficiency make it an ideal choice for Omni, which aims to provide a reliable cross-rollup and cross-chain communication service. + +### Features of CometBFT + +- **High Security**: CometBFT's design incorporates advanced cryptographic techniques to safeguard against attacks, ensuring the integrity and finality of transactions on the Omni network. +- **Scalability**: Optimized for performance, CometBFT can process a high volume of transactions while maintaining low latency, supporting Omni's goal of providing a seamless user experience across different blockchain ecosystems. +- **Decentralization**: By allowing broad participation in the consensus process, CometBFT fosters a more decentralized network structure, aligning with the blockchain ethos of distributed authority. + +## How CometBFT Powers Omni + +- **Cross-Chain Consensus**: CometBFT enables Omni to achieve consensus not just within its own network but also in coordinating state changes across connected blockchains and rollups, ensuring coherent and reliable cross-chain communication. +- **Robust Network Stability**: The resilience of CometBFT against Byzantine faults means that Omni can maintain operational stability even under adversarial conditions, making it a dependable backbone for the protocol. +- **Facilitating Innovation**: With CometBFT at its core, Omni provides a secure platform for developers to build innovative applications that leverage cross-chain capabilities without compromising on performance or security. From 781b77e97dab167c146015fdb93178e53dcce4b2 Mon Sep 17 00:00:00 2001 From: Dennis Date: Thu, 29 Feb 2024 17:45:54 +0100 Subject: [PATCH 07/10] chore(docs): learn omni dual chain --- docs/site/docs/learn/omni/architecture.md | 26 +++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/site/docs/learn/omni/architecture.md b/docs/site/docs/learn/omni/architecture.md index c66813402..461d7f129 100644 --- a/docs/site/docs/learn/omni/architecture.md +++ b/docs/site/docs/learn/omni/architecture.md @@ -3,3 +3,29 @@ sidebar_position: 6 --- # Dual-Chain Architecture + +## Consensus Layer + Execution Layer + +Omni introduces an innovative approach to blockchain architecture, designed to enhance performance and scalability without compromising on security. At its core, Omni's architecture is split into two primary layers: the **Consensus Layer** and the **Execution Layer**. This dual-chain structure enables Omni to efficiently process transactions and manage global state across multiple networks. + +## The Consensus Layer + +At the heart of Omni's network lies the **Consensus Layer**, powered by the CometBFT consensus engine. This layer is where validators come together to agree on the state of the network, ensuring every transaction is valid and finalizing the global state across all connected networks within seconds. The key benefits include: + +- **Immediate Transaction Finalization**: With CometBFT, once a transaction is included in a block, it's considered final—eliminating the need for additional confirmations. +- **Delegated Proof of Stake (DPoS)**: This mechanism allows users to delegate their restaked ETH directly to validators, bolstering the network's security. +- **Proven Robustness**: CometBFT is battle-tested and trusted in securing billions of dollars across various blockchain networks. + +## The Execution Layer + +Parallel to the Consensus Layer is the **Execution Layer**, or the Omni EVM, mirroring the Ethereum L1 execution layer's functionality. This is where users' transactions are processed, and the following features stand out: + +- **Scalable Transaction Processing**: The Omni EVM handles transactions in its mempool, enabling high throughput without overloading the network. +- **Compatibility with Ethereum Clients**: Omni leverages existing Ethereum execution clients (e.g., Geth, Besu, Erigon), ensuring stability and up-to-date features. +- **Dynamic Fee Mechanism**: Supporting [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559), the Omni EVM allows for dynamic transaction fees and partial fee burning, optimizing network usage costs. + +## Unifying Consensus and Execution + +Omni's dual-chain architecture facilitates **Parallelized Consensus**, allowing validators to simultaneously run consensus for the Omni EVM and cross-network messages. This innovative design, supported by tools like ABCI++ and the Engine API, makes Omni's sub-second finality possible. Validators efficiently attest to the state of external rollup VMs, ensuring seamless state transitions and unified state management. + +By separating consensus operations from transaction execution, Omni effectively scales activity across its network and connected rollups. This architecture not only mitigates the risk of network congestion but also enhances the security and reliability of cross-network transactions. From 811729cd598fa6338c551c01b1a41e7eaba71b91 Mon Sep 17 00:00:00 2001 From: Dennis Date: Thu, 29 Feb 2024 17:51:07 +0100 Subject: [PATCH 08/10] chore(docs): learn omni parallel consensus --- docs/site/docs/learn/omni/consensus.md | 37 +++++++++++++++++++++++++- 1 file changed, 36 insertions(+), 1 deletion(-) diff --git a/docs/site/docs/learn/omni/consensus.md b/docs/site/docs/learn/omni/consensus.md index d0a501492..083d6232a 100644 --- a/docs/site/docs/learn/omni/consensus.md +++ b/docs/site/docs/learn/omni/consensus.md @@ -2,4 +2,39 @@ sidebar_position: 7 --- -# Parallelized Consensus +# Omni Parallelized Consensus + +Omni introduces a groundbreaking approach to blockchain consensus known as **Parallelized Consensus**. This innovative method allows the Omni network to simultaneously process consensus on its Ethereum Virtual Machine (EVM) and manage cross-chain data or messages, known as XBlocks. This dual-path consensus mechanism enhances network performance, ensuring swift and secure validation of transactions and cross-chain interactions. + +## How Parallelized Consensus Works + +Parallelized Consensus in Omni consists of two main sub-processes, each handling a distinct aspect of network operations: + +### Omni EVM Consensus + +1. **Block Proposal**: Validators take turns proposing new blocks. The proposing validator's Halo client requests the latest block from the Omni EVM through the Engine API. +2. **Block Construction**: The execution client compiles a block from pending transactions and sends the block header back to the Halo client. +3. **Block Inclusion**: The proposed block is wrapped as a CometBFT transaction and added to the consensus layer block, ready for network validation. +4. **Validation**: Other validators use the Engine API to verify the proposed block's validity by running the state transition function on the block header. + +### `XBlock` Consensus + +1. **XMsg Event Monitoring**: Each validator's `halo` client monitors rollup VMs for `XMsg` events emitted by Portal contracts. +2. **`XBlock` Creation**: Validators construct `XBlock`s containing `XMsg`s for each rollup VM block that includes cross-chain messages. +3. **Attestation**: After cross-chain message data is finalized on Ethereum L1, validators attest to the hash of the corresponding `XBlock`, incorporating these attestations into the current consensus layer block. + +### Finalizing Blocks + +The combined efforts of validating Omni EVM transactions and attesting to `XBlock` hashes culminate in a unified consensus vote. If a proposed block garners approval from two-thirds of the validator set, it is finalized and added to the Omni chain. These finalized blocks encompass both the Omni EVM transactions and attested XBlock hashes, enabling full node operators of specific rollup VMs to reconstruct and verify XBlock contents. + +## The Significance of Parallelized Consensus + +Omni's Parallelized Consensus represents a significant leap forward in blockchain technology, enabling: + +- **Efficient Processing**: By separating the consensus processes for the Omni EVM and `XBlock`s, Omni achieves rapid state transitions and block finalization. +- **Enhanced Security and Reliability**: The dual-path consensus strengthens the network's integrity, providing robust security for both on-chain transactions and cross-chain communications. +- **Global Scalability**: This consensus model paves the way for a scalable and interoperable blockchain ecosystem, where diverse networks can communicate and transact seamlessly. + +Omni's adoption of Parallelized Consensus underscores its commitment to fostering a more connected and efficient blockchain world, where the boundaries between different chains and technologies blur, creating a unified and powerful platform for decentralized applications and services. + +For a deeper dive into Omni's Parallelized Consensus and its impact on blockchain interoperability, [visit the protocol section](../../protocol/introduction.md). From 77db50f12bb87656a81aa5749035478d937af5dc Mon Sep 17 00:00:00 2001 From: Dennis Date: Thu, 29 Feb 2024 17:55:20 +0100 Subject: [PATCH 09/10] chore(docs): fix links --- docs/site/docs/home.md | 2 +- docs/site/docs/learn/introduction/goal.md | 2 +- docs/site/docusaurus.config.ts | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/site/docs/home.md b/docs/site/docs/home.md index 4edabd72a..7b7d4a59b 100644 --- a/docs/site/docs/home.md +++ b/docs/site/docs/home.md @@ -11,4 +11,4 @@ slug: / _Welcome to the documentation portal for all things Omni!_ -Please read on to learn [about Omni](./learn/introduction.md), [the network](./protocol/introduction.md), [developer docs](./develop/contracts.md) and [running a validator](./operate/introduction.md). +Please read on to learn [about Omni](./learn/introduction/introduction.md), [the network](./protocol/introduction.md), [developer docs](./develop/contracts.md) and [running a validator](./operate/introduction.md). diff --git a/docs/site/docs/learn/introduction/goal.md b/docs/site/docs/learn/introduction/goal.md index bbee8338a..6aafe05a3 100644 --- a/docs/site/docs/learn/introduction/goal.md +++ b/docs/site/docs/learn/introduction/goal.md @@ -6,4 +6,4 @@ sidebar_position: 3 > **The goal of Omni is to pair an innovative security model with a novel, modular architecture to provide the highest performance interoperability network for rollup application developers.** -Omni is a blockchain specifically designed to unify Ethereum's rollups, mitigating fragmentation by [restaking](../protocol/restaking/restaking.md) for enhanced security and simplicity, allowing developers to create cross-rollup applications effortlessly. It pioneers the use of ETH restaking to bolster security, streamlining the development process by abstracting cross-rollup complexities from users and developers. As the Ethereum ecosystem grows and diversifies, Omni positions itself as the essential infrastructure to support Ethereum's modular evolution, offering a seamless development experience amidst a landscape of increasing rollup networks. +Omni is a blockchain specifically designed to unify Ethereum's rollups, mitigating fragmentation by [restaking](../background/restaking.md) for enhanced security and simplicity, allowing developers to create cross-rollup applications effortlessly. It pioneers the use of ETH restaking to bolster security, streamlining the development process by abstracting cross-rollup complexities from users and developers. As the Ethereum ecosystem grows and diversifies, Omni positions itself as the essential infrastructure to support Ethereum's modular evolution, offering a seamless development experience amidst a landscape of increasing rollup networks. diff --git a/docs/site/docusaurus.config.ts b/docs/site/docusaurus.config.ts index 40a80cda8..d8f95d094 100644 --- a/docs/site/docusaurus.config.ts +++ b/docs/site/docusaurus.config.ts @@ -16,7 +16,7 @@ const config: Config = { baseUrl: "/", onBrokenLinks: "throw", - onBrokenMarkdownLinks: "warn", + onBrokenMarkdownLinks: "throw", // Even if you don't use internationalization, you can use this field to set // useful metadata like html lang. For example, if your site is Chinese, you From 847fa2152d05e9cbb559274ee271c95110fcc9f8 Mon Sep 17 00:00:00 2001 From: Dennis Date: Thu, 29 Feb 2024 17:58:15 +0100 Subject: [PATCH 10/10] chore(docs): collapsed false for intro --- docs/site/sidebars.ts | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/site/sidebars.ts b/docs/site/sidebars.ts index 2c6252728..ce46596df 100644 --- a/docs/site/sidebars.ts +++ b/docs/site/sidebars.ts @@ -7,6 +7,7 @@ const sidebars: SidebarsConfig = { label: "Introduction", className: "sidebar-title", collapsible: true, + collapsed: false, items: [ { type: "autogenerated",