The post Sui launches Mysticeti v2 consensus engine appeared on BitcoinEthereumNews.com. The Sui blockchain has taken a major step to overhaul transaction handling in a major consensus update that targets lower latency and higher efficiency. Summary Sui upgraded its consensus engine to reduce latency. Transaction handling is now lighter and more efficient. A new submission path cuts bandwidth and CPU usage. Sui is rolling out a new version of its consensus engine, designed to make transactions faster and less resource-intensive, without altering how the network operates at its base layer. The update was announced by Mysten Labs engineers on Nov. 6, outlining how Mysticeti v2 integrates transaction validation directly into the consensus process. A shift in how transactions move through the network Mysticeti, first activated on Sui’s (SUI) mainnet in July 2024, is a DAG-based consensus model built for speed and responsiveness. The goal was always to reduce waiting time between when a transaction is submitted and when it becomes final.  While the first version of Mysticeti improved network latency, part of Sui’s transaction handling still depended on a separate pre-consensus validation step. That step made sense from a control and security standpoint, but it added extra computation and slowed finalization for more complex transactions. Mysticeti v2 eliminates that separation. Validation and consensus now occur simultaneously, eliminating redundant work and reducing the time required to confirm non-fast-path transactions. This change allows the network to move closer to the performance levels the original Mysticeti design aimed for — processing many transactions at once without increasing network strain. A new path for submitting transactions Alongside the consensus change, Sui is also replacing its transaction submission flow. The previous Quorum Driver sent every transaction to all validators and required multiple rounds of signature aggregation before ordering could begin. This protected the fast-path flow but consumed a large amount of bandwidth and CPU. The new… The post Sui launches Mysticeti v2 consensus engine appeared on BitcoinEthereumNews.com. The Sui blockchain has taken a major step to overhaul transaction handling in a major consensus update that targets lower latency and higher efficiency. Summary Sui upgraded its consensus engine to reduce latency. Transaction handling is now lighter and more efficient. A new submission path cuts bandwidth and CPU usage. Sui is rolling out a new version of its consensus engine, designed to make transactions faster and less resource-intensive, without altering how the network operates at its base layer. The update was announced by Mysten Labs engineers on Nov. 6, outlining how Mysticeti v2 integrates transaction validation directly into the consensus process. A shift in how transactions move through the network Mysticeti, first activated on Sui’s (SUI) mainnet in July 2024, is a DAG-based consensus model built for speed and responsiveness. The goal was always to reduce waiting time between when a transaction is submitted and when it becomes final.  While the first version of Mysticeti improved network latency, part of Sui’s transaction handling still depended on a separate pre-consensus validation step. That step made sense from a control and security standpoint, but it added extra computation and slowed finalization for more complex transactions. Mysticeti v2 eliminates that separation. Validation and consensus now occur simultaneously, eliminating redundant work and reducing the time required to confirm non-fast-path transactions. This change allows the network to move closer to the performance levels the original Mysticeti design aimed for — processing many transactions at once without increasing network strain. A new path for submitting transactions Alongside the consensus change, Sui is also replacing its transaction submission flow. The previous Quorum Driver sent every transaction to all validators and required multiple rounds of signature aggregation before ordering could begin. This protected the fast-path flow but consumed a large amount of bandwidth and CPU. The new…