Sui feature analysis: Why is there a chance for the fastest Web3 application on the Sui blockchain?

In this article, we analyze how single-write principle applications work and what they can achieve, and the most critical “Why will Sui have a chance to build the fastest applications in Web3?”

Original: Trace Twitter

Although many people are optimistic about Sui, they don’t actually know one of the most important functions of Sui in protocol implementation: the application of the single-write principle.

In this article, we analyze how single-write principle applications work and what they can achieve, and the most critical “Why will Sui have a chance to build the fastest applications in Web3?”

How does Sui handle transactions?

Sui has a dual consensus model – dependent transactions are ordered and processed sequentially, while independent transactions are executed in parallel.

Dependent transactions are handled using the novel Narwhal and Bullshark protocols. Narwhal is a mempool protocol, while Bullshark is a consensus protocol that integrates effectively with Narwhal for consensus.

Dependent transaction models only need to be executed sequentially with other transactions they are associated with. Sui organizes them in batches, executing each batch in parallel.

Sui Feature Analysis: Why is there a chance for the fastest Web3 application on the Sui blockchain?

Sui originally planned to use Narwhal and Tusk, but recently switched from Tusk to Bullshark.

Tusk and Bullshark are similar consensus protocols, but Bullshark has slightly lower throughput and faster speed.

Narwhal + Bullshark is very fast (~2 seconds).

However, Sui’s true speed will only become apparent when the transactions are completely independent. For these transactions, instead of using Narwhal + Bullshark, Sui uses a different method called Byzantine Consensus Broadcasting (BCB).

In this path, the network submits transactions without global consensus, allowing it to process transactions almost instantly.

Note that this does not result in a reduction in security or effectiveness guarantees.

The Sui transaction model has 2 paths:

  • Narwhal + Bullshark for causal dependent transactions (~2 seconds delay)
  • BCB is used for independent transactions (almost instant).

So, when are transactions on Sui independent?

In Sui, the basic unit of storage is an object, not an account. Objects can be NFTs, DeFi protocols, games, or anything else you want to build, and each object has an “owner” property that specifies who can interact with that object. There are 4 different types of ownership:

1) Owned by an address (this is what you mean by “owning” something on Sui, eg: tokens).

2) Owned by another object (eg: an NFT is part of another NFT).

3) Immutable (no one can change it, anyone can interact with it).

4) Shared (Anyone can read or write the object. For example: AMM)

So, how do these ownership types fit into Sui’s dual consensus?

Transactions with shared objects need to be ordered – since users can change the objects they interact with, the ordering of transactions is important.

However, if an object is owned by an address, only that address can use it in a transaction. If the owner wants to interact with their object, it is completely independent of other transactions, which means it can use BCB.

Any Sui application or object that has only one owner can perform transactions that interact with that object almost immediately.

This means that Sui supports Web3 applications running at Web2 speeds, which Mysten Labs refers to as “write-single-principle applications”.

Of course, not every Web3 application can be written as a single-write principle application.

In fact, most popular applications, such as DEXs and money markets, must have multiple writers, and interactions with these protocols can take seconds to process.

However, Sui supports a long list of single-write principle applications that will provide an unparalleled Web3 experience.

Here are some of the most exciting potential applications of the single-write principle:

Sui Pay:

Asset transfers only require one owner, enabling it to utilize BCB.

Developers can build a payment platform that utilizes Sui for fast payments, while keeping their assets within a composable Web3 ecosystem.

Public bulletin board:

Users can publish data, files or text on the chain and read each other’s information. Note that Sui’s storage model eliminates the problems that cause state bloat. Users pay for data storage and can delete data at any time for a refund.

Messaging service:

Messages and responses can be programmed in Sui Move as single-write principle NFTs, enabling them to leverage BCB, where applications and users can exchange information extremely fast.

Social network:

Similar to messaging services, all features of social networks can be designed as single-write principle NFTs, such as posts.

Non-Interactive Games:

Like many single-player games, encrypted games that don’t involve shared objects can be applications of the write-once principle, performance has always been a key bottleneck for Web3 games, and Sui’s architecture will help unlock its potential.

Oracle quotation:

The faster the oracle data feed is updated, the more dynamic the DeFi market will be. Oracle data feeds can be written entirely as single-write principle applications, opening up new opportunities for lending markets, prediction markets, and other applications that benefit from high data flows.

Support for blazingly fast single-write principle applications is one of Sui’s strongest features, and I can’t wait to see what the future holds for Sui.

Posted by:CoinYuppie,Reprinted with attribution to:
Coinyuppie is an open information publishing platform, all information provided is not related to the views and positions of coinyuppie, and does not constitute any investment and financial advice. Users are expected to carefully screen and prevent risks.

Like (0)
Donate Buy me a coffee Buy me a coffee
Previous 2022-09-22 11:51
Next 2022-09-22 11:52

Related articles