Sui Name Service Scalability is one of Sui's strong points, which Sui does thanks to its ability to process transactions in parallel. Most blockchains today have limited throughput because transactions must be ordered and placed in a block that is then resolved gradually. The difference of Sui is that they will organize data into independent objects (objects) and process them in parallel.

Sui divides asset types into objects to perform transactions, of which there are 3 main types:

-Owned object: Owned by a specific owner and can only be modified by that owner.
-Shared object: Mutable, has no specific owner and can be included in the transaction of different parties without any permission.
-Read-only object: Has no exclusive owner, cannot be changed by anyone after being published, and can be used in transactions by all users.

To process transactions in parallel, Sui uses two paths to reach consensus:

Byzantine Consistent Broadcast (BCB): For independent transactions that do not depend on other parts of the blockchain state, usually transactions involving owned objects and read-only objects. Byzantine Fault-Tolerant (BFT) consensus: For complex transactions involving shared objects, these transactions will be sorted and processed sequentially. → This means that independent transactions will be processed in parallel, only requiring consensus for complex transactions. Thereby reducing network latency, improving throughput, helping Sui scale linearly horizontally.

Do you have questions about Sui's investors? Please look forward to reading part 4 !

Sui Name Service Scalability is one of Sui's strong points, which Sui does thanks to its ability to process transactions in parallel. Most blockchains today have limited throughput because transactions must be ordered and placed in a block that is then resolved gradually. The difference of Sui is that they will organize data into independent objects (objects) and process them in parallel.

Sui divides asset types into objects to perform transactions, of which there are 3 main types:

-Owned object: Owned by a specific owner and can only be modified by that owner.
-Shared object: Mutable, has no specific owner and can be included in the transaction of different parties without any permission.
-Read-only object: Has no exclusive owner, cannot be changed by anyone after being published, and can be used in transactions by all users.

To process transactions in parallel, Sui uses two paths to reach consensus:

Byzantine Consistent Broadcast (BCB): For independent transactions that do not depend on other parts of the blockchain state, usually transactions involving owned objects and read-only objects. Byzantine Fault-Tolerant (BFT) consensus: For complex transactions involving shared objects, these transactions will be sorted and processed sequentially. → This means that independent transactions will be processed in parallel, only requiring consensus for complex transactions. Thereby reducing network latency, improving throughput, helping Sui scale linearly horizontally.

Do you have questions about Sui's investors? Please look forward to reading part 4 !