<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/e8d8f0e5-5ad8-4dde-a9f5-6d8095505f13/Sui_Icon_Brand.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/e8d8f0e5-5ad8-4dde-a9f5-6d8095505f13/Sui_Icon_Brand.png" width="40px" /> Sui - платформа смарт-контрактов нового поколения с высокой пропускной способностью, низкой задержкой и моделью программирования, ориентированной на активы, основанной на языке программирования Move

</aside>

General idea.

Sui provides scalability and unprecedented low latency for common use. The technology allows the vast majority of transactions to be processed in parallel, making better use of processing resources and offering the ability to increase throughput at the expense of more resources. Sui eschews consensus to instead use simpler, lower-latency primitives for common use cases such as payment transactions and asset transfers. This is unprecedented in the world of blockchain and enables a number of new distributed, latency-sensitive applications, ranging from games to retail payments at physical points of sale.

Sui is written in Rust and supports smart contracts written in the Move programming language to define assets that may have an owner. Move programs define operations on these assets, including custom rules for creating them, transferring these assets to new owners, and operations that modify the assets.

Sui has its own token called SUI with a fixed sapple. The SUI token is used to pay for gas and is also used as a delegated bid for authorities within the era. Authority voting power within this epoch is a function of this delegated stake. Authorities are periodically reconfigured according to their delegated stake. In any epoch, the set of authorities is Byzantine refuse-proof. At the end of the epoch, the fees charged for all processed transactions are distributed among the authorities according to their contribution to the functioning of the system. Authorities, in turn, can share some fees as a reward with users who have delegated a share to them.

What SUI offers us:

• Unmatched scalability, instant settlement
• Secure smart contract language available to mainstream developers
• Ability to identify rich and composite assets in the chain
• The best user interface for web 3 applications

Architecture

How the protocol works:

In the diagram below, we can see the high-level interaction between the client and the SUI to perform a transaction. This interaction can be explained as follows:

• A user with a private signing key creates and signs a user transaction to modify objects he owns or shared objects in the SUI. Consequently, the user signature keys are not needed and the rest of the verification can be performed by the user's client or gateway on behalf of the user (denoted in the diagram as a keyless operation).
• The user transaction is sent to the SUIs, who validate it, and if successful, sign it and return the signed transaction to the client. The client collects responses from the SUI authorities to generate a transaction certificate.
• The transaction certificate is then sent back to all authorities, and if the transaction involves shared objects, it is also sent to the agreement protocol managed by the SUI authorities. They verify the certificate, and if shared objects are involved, also wait for the agreement protocol to order it against other transactions with shared objects, and then execute the transaction and summarize its results in a signed response.

• Once the authority has completed all actions on a certificate, its action becomes final (indicated as Finality in the diagram). Clients can assemble a quorum of authoritative responses and create an action certificate and use it as proof of finality of transaction results.