From 807ab8dfee34f00797df63995f150aefbdb31c83 Mon Sep 17 00:00:00 2001 From: cdevens1 <162626247+cdevens1@users.noreply.github.com> Date: Thu, 7 Nov 2024 15:01:07 -0700 Subject: [PATCH] chore(docs): update language for Octane (#2420) Update language for Octane issue: none --- docs/content/learn/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/learn/architecture.md b/docs/content/learn/architecture.md index e770398b3..66a54429b 100644 --- a/docs/content/learn/architecture.md +++ b/docs/content/learn/architecture.md @@ -8,7 +8,7 @@ Omni is a network purpose built for fixing fragmentation across the Ethereum eco 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/). -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. +Omni uses Octane to combine the EVM with the [CometBFT](https://docs.cometbft.com/v0.38/) (formerly Tendermint) consensus engine, creating a scalable, high performance network with fast transaction finality at scale. 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.