About SUI Network
Sui is the first permissionless Layer 1 blockchain designed from the ground up to enable creators and developers to build experiences that cater to the next billion users in web3. Sui achieves an extremely composable programming model, allowing it to be one of the best solutions for developers and creators.
Sui blockchain has a few killer features:
- Easy to scale. Sui scales horizontally with no upper bound to meet application demand while maintaining extremely low operating costs per transaction.
- Everything is an object in Sui. A smart contract is an object (called Move Package). Once an Move package is published on-chain, it becomes immutable. A package object can depend on other package objects that were previously published to the Sui ledger. This means Sui achieves an extremelly composable programming model. This makes it one of the best solutions as it allows developers and creators to build incredible games, NFTs and applications.
- Move Programming language is a Smart Contracts language in the Sui network that allows developers and creators ample opportunities. About the differences between Move and Solidity, you can read here.
Traditional blockchain validators collectively build a shared accumulator: a representation of the state of the blockchain, a chain to which they add increments over time, called blocks. In blockchains that offer deterministic finality, every time validators want to make an incremental addition to the blockchain, i.e., a block proposal, they sequence the proposal. This protocol lets them form an agreement over the current state of the chain, whether the proposed increment is valid, and what the state of the chain will be after the new addition.
This method of maintaining a common state over time has known practical success over the last 14 years or so, using a wealth of theory from the last 50 years of research in the field of Byzantine Fault Tolerant distributed systems.
Yet it is inherently sequential: increments to the chain are added one at a time, like pearls on a string. In practice, this approach pauses the influx of transactions (often stored in a "mempool"), while the current block is under consideration.
A lot of transactions do not have complex interdependencies with other, arbitrary parts of the state of the blockchain. Often financial users just want to send an asset to a recipient and the only data required to gauge whether this simple transaction is admissible is a fresh view of the sender's address. Hence Sui takes the approach of only taking a lock - or "stopping the world" - for the relevant piece of data rather than the whole chain -- in this case, the address of the sender, which can only send one transaction at a time. Therefore, the transaction can occur in parallel with the rest of the blockchain because the action of the transaction's result is independent.
Sui further expands this approach to more involved transactions that may explicitly depend on multiple elements under their sender's control, using an object model and leveraging Move's strong ownership model. By requiring that dependencies be explicit, Sui applies a "multi-lane" approach to transaction validation, making sure those independent transaction flows can progress without impediment from the others.
This doesn't mean that Sui as a platform never orders transactions with respect to each other, or that it allows owners to affect only their owned microcosm of objects. Sui also processes transactions that have an effect on some shared state in a rigorous, consensus-ordered manner. They're just not the default use case. See the State-of-the-art consensus section for details on the Narwhal and Bullshark consensus engine.
Last modified 1mo ago