Sui Lutris: a distributed system protocol at the heart of Sui

After months of testing, Mysten Labs updated the Sui Lutris white paper on August 18 , confirming the following:

  1. Using PTBs and 5K TPS, Sui can handle 140k to 150k operations per second, which shows that Sui's benchmarks at mainnet peak (~700 TPS) are well below its actual performance.
  2. Sui’s finalization latency remains below 0.5 seconds, even when a certain number of validator nodes stop functioning.

The Sui Lutris white paper contains instructions on how external testers can obtain relevant numerical instructions in their own verification tests, proof of security, and a detailed description of how Sui operates.

Shortly after the launch of the Sui mainnet, we saw exciting applications being launched on the chain, such as games and NFTs. Recently, Mysten Labs released a technical report on Sui Lutris, a distribution system that supports Sui. Sui Lutris allows Sui to maintain low latency with high throughput and long-term stability.

Since Bitcoin emerged ten years ago, blockchain technology has come a long way, with new use cases such as games and NFTs emerging. The blockchain community also continues to explore to improve the efficiency of blockchain technology, especially in handling high loads and providing real-time latency.

We believe that L1 blockchains face two main challenges today: achieving high throughput while maintaining low latency, and ensuring that the consensus protocol remains stable in the long term. These challenges can be achieved through dynamic participation of validator nodes and configuration challenges.

An effective way to achieve high throughput is to use a DAG-based consensus protocol such as Narwhal/Bullshark used by Sui . These consensus protocols enable blockchains to execute large numbers of transactions simultaneously, making them ideal for use cases such as gaming and NFTs. However, DAG-based protocols can cause a delay of several seconds, which has a significant impact on common transfer or gaming operations.

On the other hand, consensus-free protocols have shown great potential in reducing latency and scaling, such as FastPay , a prototype we have studied in the past . These protocols eliminate consensus and allow transactions to be processed quickly without the need for independent transactions to be processed in parallel. However, this is limited to a limited class of simple operations on the blockchain. This limits the expression of smart contracts and makes it challenging to reconfigure a dynamically changing set of validator nodes.

Although both of the above protocols have potential, neither of them are currently used in production-level blockchains. They are currently only presented at academic conferences and are not widely used by the blockchain community. Sui Lutris is the protocol that underpins the Sui network, combining DAG-based consensus with consensus-less approaches to achieve the best of both worlds: sub-second latency (less than 1 second) and sustained throughput of thousands of transactions per second . Sui achieves both goals while maintaining the ability to express complex contracts on shared objects, generate checkpoints, and reconfigure the set of validators across epochs.

Combining consensus-based and consensus-free approaches

Sui Lutris uses a unique approach that combines the two methods mentioned above. To ensure the operational security of assets (unique objects) owned by a single owner, the system employs a consistent broadcast protocol among validator nodes, resulting in lower latency than consensus. Sui Lutris relies solely on consensus to handle complex smart contracts running on shared objects, that is, objects that can be changed by any user. Sui Lutris also supports network maintenance operations such as defining checkpoints and reconfiguring validator nodes. This novel strategy provides the best of both worlds when processing transactions in a replicated Byzantine environment.

Diagram representing high-level description and transaction lifecycle in Sui Lutris

➊ Users with private keys create and sign transactions that change the objects they own, or a mixture of their private and shared objects. ➋ Transactions are usually sent to each Sui Lutris verification node through the full node. The verification node is responsible for performing a series of validity and security checks, signing it, and returning the signed transaction to the client. ➌ The client collects responses from the vast majority of verification nodes to form a transaction certificate. At this point the transaction can be confirmed as irreversible, that is, it has reached its finality. ➍ After the certificate is integrated, it will be sent back to all verification nodes, and the verification nodes will check its validity and confirm receipt to the client. If a transaction involves an exclusive object, the transaction certificate can be processed and executed immediately without waiting for the consensus engine (direct fast path). All certificates are forwarded to the DAG-based consensus protocol (run by Sui validator nodes). ➎ The consensus finally outputs the number of the certificate, and the verification node checks and executes the included shared object. ➏ Clients can collect responses from the vast majority of validating nodes, assemble them into valid certificates , and use them as proof of transaction settlement. ➐ Subsequently, checkpoints are formed for each consensus commit, and these checkpoints can also be used to drive the reconfiguration protocol.

In addition to the main transaction processes described above, Sui Lutris provides a series of facilities to support product-level blockchains:

  1. Implement a checkpoint protocol after finality is achieved, which generates a history of all transactions in the system. This is suitable for complete auditing, as well as keeping full nodes and lagging validator nodes in sync in an efficient manner.
  2. Sui Lutris supports reconfiguration at the end of each epoch, when the set of validator nodes and their voting rights may change. To ensure that all final transactions are contained in an Epoch, each Epoch needs to be carefully closed and confirmed to be ultimately safe.
  3. In the previous consensus-free protocol, when a double-spend attack occurred on a client's assets, the assets would be locked forever. Sui Lutris will safely "unlock" mistakenly locked assets at the end of the epoch, minimizing the loss of errors.

Sui is a blockchain that manages massive amounts of value for its users, and Sui Lutri is the foundation of Sui. The full technical report provides more details on how the security and liveness protocols operate, as well as a proof of security with partial synchronization with Byzantine actors in a standard distributed system model.

在完整的Sui Lutris报告中查看更多细节:

https://github.com/MystenLabs/sui/blob/main/doc/paper/sui-lutris.pdf


关于 Sui Network

Sui是基于第一原理重新设计和构建而成的L1公有链,旨在为创作者和开发者提供能够承载Web3中下一个十亿用户的开发平台。Sui上的应用基于Move智能合约语言,并具有水平可扩展性,让开发者能够快速且低成本支持广泛的应用开发。获取更多信息:https://linktr.ee/sui_apac

官网英文Twitter中文TwitterDiscord英文电报群中文电报群

Guess you like

Origin blog.csdn.net/Sui_Network/article/details/132741670