Practical overview
When it fits
Use Sui when a project needs a Move-based Layer 1 for asset-oriented smart contracts, SUI gas and staking workflows, or integrations through its client components. Its parallel-processing design is relevant to applications handling many transactions.
Who it is for
- Developers building Move smart contracts and on-chain assets
- Teams creating blockchain applications for gaming, payments or asset transfer
- Engineers integrating with Sui through CLI, REST-client or RPC-client components
- Operators or integrators working with Sui authorities
Documented uses
- Deploy smart contracts that define transferable and composable on-chain assets.
- Build gaming applications around Sui asset ownership and parallel transaction processing.
- Create retail payment applications using payment and asset-transfer primitives.
- Develop tools for SUI gas payment and delegated-staking workflows.
- Integrate with Sui authorities using client and networking components.
Requirements & limits
The evidence identifies Sui as a public, active, open-source repository under the Apache-2.0 license.
- Move is the application smart-contract language, while the core implementation is in Rust.
- The platform is designed for parallel transaction processing, which matters for transaction-heavy asset applications.
- SUI is used for gas payment and delegated staking.
- The repository includes CLI, REST-client and RPC-client components for development and integration.
- The Apache-2.0 license and public repository support inspection and self-hosted development.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Design Move smart contracts for owned, transferable assets
Define asset-oriented Move programs with ownership, creation, transfer, and mutation operations.
Before you start
- A Sui development context.
- Familiarity with the Move programming language.
- An asset model requiring custom creation, transfer, or mutation rules.
Steps
Model the on-chain assets and their ownership using Move.
Define creation operations with the desired custom rules.
Define transfer operations for moving assets to new owners.
Define mutation operations for changing asset state.
Use the Sui client architecture as the integration context, which includes CLI, REST, and RPC clients connected through client services to authorities.
Expected outcome
A documented design for Move smart contracts that define owned assets and their creation, transfer, and mutation operations.
Guide limitations
- The source does not document installation, build commands, deployment commands, testing procedures, or network configuration.
- The source describes the architecture and programming model but does not provide a complete implementation example.
Plan a Sui application around parallel transactions and asset transfers
Identify an application design that uses Sui’s documented parallel-processing model and low-latency payment or asset-transfer primitives.
Before you start
- A Sui application use case such as gaming or retail payment.
- Assets or payment transactions suitable for Sui’s Move-based ownership model.
- A client integration approach using the documented CLI, REST, or RPC components.
Steps
Identify transactions that can be processed independently, such as common payment or asset-transfer operations.
Represent application assets and ownership rules with Move programs.
Select a documented client path—CLI, REST client, or RPC client—to connect through the client service architecture.
Design the application flow around transfers or payments that use Sui’s low-latency primitives.
Expected outcome
An application architecture aligned with Sui’s documented asset model, client components, and parallel transaction-processing approach.
Guide limitations
- The source does not document client setup, API calls, deployment, performance measurements, or a complete gaming or retail implementation.
- The source states that many transactions are processable in parallel but does not specify application-specific throughput or latency.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 30 September 2026
- Original website title
- MystenLabs/sui · Official homepage title · retained in its source language