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

chore(docs): update overview #2361

Merged
merged 2 commits into from
Nov 5, 2024
Merged

chore(docs): update overview #2361

merged 2 commits into from
Nov 5, 2024

Conversation

fabtreb
Copy link
Contributor

@fabtreb fabtreb commented Nov 4, 2024

Update overview and architecture

issue: none

Copy link

github-actions bot commented Nov 4, 2024

Docs preview complete 🚀 see it here: https://omni-gvssixvek-omni-engineering.vercel.app

Copy link

github-actions bot commented Nov 5, 2024

Docs preview complete 🚀 see it here: https://omni-r0gir5r17-omni-engineering.vercel.app

@fabtreb fabtreb requested review from ttarsi and chmllr and removed request for ttarsi November 5, 2024 08:43

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.
Omni is a network purpose built for fixing fragmentation across the Ethereum ecosystem. This is accomplished by combining a secure messaging protocol for cross-rollup communications with a computational environment (the Omni EVM). Given that Omni is purpose built for solving fragmentation across Ethereum’s rollup ecosystem, it derives its security from Ethereum L1 through the use of re-staking.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find the usage of "purpose built for solving fragmentation across Ethereum" in two subsequent sentences too repetitive. Maybe replace the second sentence with something like: Since Omni spans multiple rollup chains and must provide a secure infrastructure for cross-chain message exchange, it derives its economic security from Ethereum L1 through the restaked ETH. Or something like that?


## The Consensus Engine
To achieve this, Omni was designed with a novel protocol architecture, Octane, that runs a consensus and execution engine in parallel. While Octane was developed specifically for Omni’s use case, it is open sourced and is being used by protocols that have raised over $150M, such as [Story Protocol](https://www.story.foundation/).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I'm not sure it's "novel" as it is exactly what Ethereum PoS is doing, we also mention this ourselves in multiple places.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "novel" part is combining the EVM with the CometBFT consensus engine


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:
Omni uses Octane to combine the EVM with the [CometBFT](https://docs.cometbft.com/v0.38/) (formerly Tendermint) consensus engine, providing fast consensus on every rollup network connected with Omni. Within Octane, the Engine API separates the execution environment from the consensus engine, preventing transactions from interfering with blockchain consensus. Octane is the first consensus implementation of the EngineAPI besides Ethereum itself (the Beacon Chain). [ABCI 2.0](https://docs.cometbft.com/v1.0/spec/abci/) complements the Engine API by providing a programmable interface for high-performance consensus engines like CometBFT.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

providing fast consensus on every rollup network

This is a bit misleading. I am not sure what we want to say here, but Tendermint is only providing consensus on the Omni chain itself.

preventing transactions from interfering with blockchain consensus

I am not sure I understand this either...

Octane is the first consensus implementation of the EngineAPI besides Ethereum itself (the Beacon Chain).

From what I understand, Octane is a middleware that glues the EVM engine with the CometBFT consensus by implementing both the EngineAPI of the EVM engine and the ABCI 2.0 API of CometBFT.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"preventing transactions from interfering with blockchain consensus"
ie a spike in transactions on the execution layer does not directly impact the consensus layer


1. **Extended Development Timelines**

Building a cross-chain application is resource-intensive, requiring up to four months for design, implementation, and security audits. In a fast-evolving industry where most applications are still pursuing product-market fit, this long development cycle is impractical.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find "four months" a bit too specific. How about:

Building a cross-chain application is resource-intensive, often taking several months for design, implementation, and security audits.


2. **Higher Security Risks**

Cross-chain implementations introduce complex smart contracts, increasing vulnerability to hacks. If an interoperability protocol is compromised, all applications relying on it are at risk. This heightened risk has discouraged widespread adoption of cross-chain applications.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Cross-chain implementations introduce complex smart contracts, increasing vulnerability to hacks. If an interoperability protocol is compromised, all applications relying on it are at risk. This heightened risk has discouraged widespread adoption of cross-chain applications.
Cross-chain implementations introduce complex smart contracts, increasing vulnerability to hacks. If an interoperability protocol is compromised, all applications relying on it are at risk. This increased risk has discouraged widespread adoption of cross-chain applications.

The **\$OMNI** token serves several crucial roles within the Omni protocol. **\$OMNI** can be used to pay for gas to process both cross-rollup transaction requests and Omni EVM transaction requests.

All **\$OMNI** gas fees are burned from circulation. **\$OMNI** can also be staked by or delegated to Omni validators to contribute to the network’s economic security. Staking or delegating **\$OMNI** earns rewards and will allow users to participate in network governance when it is live. Before the mainnet launch, users can participate in the Genesis Staking program by staking their **\$OMNI** tokens through the [staking portal.](https://app.omni.network/)
OMNI will several crucial roles within the Omni protocol. **OMNI** will be used to pay for gas to process both cross-rollup transaction requests and Omni EVM transaction requests. All **OMNI** gas fees will be burned from circulation. **OMNI** can also be staked by or delegated to Omni validators to contribute to the network’s economic security, along with restaked ETH. Staking or delegating OMNI earns rewards and will allow users to participate in network governance when it is live. Before the launch on mainnet, users can help bootstrap the network’s security by participating in the Genesis Staking program by staking their **OMNI** tokens through the [staking portal](https://app.omni.network/).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
OMNI will several crucial roles within the Omni protocol. **OMNI** will be used to pay for gas to process both cross-rollup transaction requests and Omni EVM transaction requests. All **OMNI** gas fees will be burned from circulation. **OMNI** can also be staked by or delegated to Omni validators to contribute to the network’s economic security, along with restaked ETH. Staking or delegating OMNI earns rewards and will allow users to participate in network governance when it is live. Before the launch on mainnet, users can help bootstrap the network’s security by participating in the Genesis Staking program by staking their **OMNI** tokens through the [staking portal](https://app.omni.network/).
OMNI will play several crucial roles within the Omni protocol. **OMNI** will be used to pay for gas to process both cross-rollup transaction requests and Omni EVM transaction requests. All **OMNI** gas fees will be burned from circulation. **OMNI** can also be staked by or delegated to Omni validators to contribute to the network’s economic security, along with restaked ETH. Staking or delegating OMNI earns rewards and will allow users to participate in network governance when it is live. Before the launch on mainnet, users can help bootstrap the network’s security by participating in the Genesis Staking program by staking their **OMNI** tokens through the [staking portal](https://app.omni.network/).

Copy link
Contributor

@chmllr chmllr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving, assuming the comments will be addressed.

@fabtreb fabtreb merged commit 8d05a64 into main Nov 5, 2024
21 checks passed
@fabtreb fabtreb deleted the fab-docs-updateoverview branch November 5, 2024 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants