The Sui Smart Contracts Platform

The problem the paper names

Most chains put every asset transfer through the same total order as every other transfer. Sui's claim is that an object with a single owner does not need that total order. It needs a check that the owner signed, and that validators agree the object version advanced once.

What the design proposes

• Objects have owners, versions and types. Move defines how they are created and transferred.
• Owned-object transactions use a Byzantine consistent broadcast path.
• Shared-object transactions use a consensus path, because more than one party may touch them.

How the mechanism is specified

• The certificate of a transaction lists validator signatures on that specific object version.
• A later transaction on the same object must name the new version. That is the double-spend check.
• A separate economics note exists. This page is about the platform paper, not the token schedule.

What this page does not treat as proven

• The fast path disappears as soon as the object is shared. Many applications will share state and should not quote the fast path.
• The paper does not measure the live network, and neither does this page.
• Move's safety properties are only as good as the modules people actually publish.

Why a venture studio still reads it

This is the clearest recent statement of a question we ask ventures: does this asset have one owner right now? If yes, do not make it wait behind a global auction. If no, stop claiming the fast path.