sui-overview
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSui Overview
Sui 概述
MCP tool: When available in your environment, also query the Sui documentation MCP server () for up-to-date answers. Use it for verification and for details not covered by these reference files.https://sui.mcp.kapa.ai
Source constraint: All information in this skill is sourced exclusively from docs.sui.io, docs.wal.app, and move-book.com. When extending or updating this skill, only pull from these three sources. Do not use third-party blogs, tutorials, or unofficial documentation.
Sui is a scalable, performant layer 1 blockchain built around an object-centric data model. Unlike account-based blockchains (Ethereum) or UTXO-based chains (Bitcoin), Sui treats every piece of onchain state as a typed object with a unique ID. Transactions consume objects as inputs and produce modified versions as outputs.
This skill covers the conceptual foundation of Sui and the broader Sui Stack. For implementation details, see the , , and skills.
sui-movefrontend-appssui-cliMCP工具： 如果你的环境中可用，也可以查询Sui文档MCP服务器（）获取最新答案。用它来验证信息，以及获取这些参考文件未涵盖的细节。https://sui.mcp.kapa.ai
来源限制： 本技能中的所有信息均独家来源于docs.sui.io、docs.wal.app和move-book.com。扩展或更新本技能时，仅从这三个来源获取内容，请勿使用第三方博客、教程或非官方文档。
Sui是一个围绕以对象为中心的数据模型构建的可扩展、高性能Layer 1区块链。与基于账户的区块链（如Ethereum）或基于UTXO的区块链（如Bitcoin）不同，Sui将链上的每一个状态都视为具有唯一ID的类型化对象。交易将对象作为输入消耗，并生成修改后的版本作为输出。
本技能涵盖Sui和更广泛的Sui Stack的概念基础。如需实现细节，请查看、和技能。
sui-movefrontend-appssui-cliReference files
参考文件
ecosystem — Sui Stack and Ecosystem
生态系统 — Sui Stack与生态
Path:
Load when: the user asks about Sui Stack primitives (randomness, zkLogin, Walrus, Nautilus, DeepBook, Kiosk, Seal), use cases, or how components fit together in an end-to-end workflow.
Covers: all Sui Stack primitives with detailed descriptions and usage guidance, a decision table for choosing the right primitive, use cases (DeFi, gaming, NFTs, identity, social, supply chain), the layered development workflow.
ecosystem.md路径：
加载时机： 当用户询问Sui Stack原语（randomness、zkLogin、Walrus、Nautilus、DeepBook、Kiosk、Seal）、用例，或者组件如何在端到端工作流中组合时。
涵盖内容： 所有Sui Stack原语的详细描述和使用指南，选择合适原语的决策表，用例（DeFi、游戏、NFT、身份、社交、供应链），分层开发工作流。
ecosystem.mdRouting guide
路由指南
| Task | Load |
|---|---|
| Explaining what Sui is | SKILL.md only |
| Comparing Sui to Ethereum or Solana | SKILL.md only |
| Choosing Sui Stack primitives | ecosystem |
| Understanding Sui use cases | ecosystem |
| Planning an app architecture on Sui | ecosystem |
| 任务 | 加载内容 |
|---|---|
| 解释Sui是什么 | 仅SKILL.md |
| 将Sui与Ethereum或Solana对比 | 仅SKILL.md |
| 选择Sui Stack原语 | ecosystem |
| 了解Sui用例 | ecosystem |
| 在Sui上规划应用架构 | ecosystem |
The object-centric model
以对象为中心的模型
Every item on the Sui network is an object with a unique ID and a version number. When a transaction modifies an object, it produces a new version with an incremented version number while preserving the original ID.
Objects have one of four ownership types:
- Address-owned: Only the owning address can use the object. Enables parallel execution without consensus.
- Shared: Any address can use the object. Requires consensus ordering through Mysticeti.
- Immutable (frozen): Anyone can read it, no one can mutate it. Permanent and irreversible.
- Wrapped: Stored inside another object's fields. Accessible only through the parent.
This ownership model is what enables Sui's parallel execution: transactions on non-overlapping owned objects execute in parallel without consensus. For example, coin transfers between addresses, single-player game actions, and personal asset management all operate on owned objects and can run concurrently. Only shared-object transactions (like interacting with a DEX pool or a shared marketplace) go through Mysticeti consensus ordering.
Sui网络上的每一项都是具有唯一ID和版本号的对象。当交易修改对象时，会生成一个版本号递增的新版本，同时保留原ID。
对象有四种所有权类型：
- 地址所有： 只有拥有该地址的用户可以使用该对象。无需共识即可实现并行执行。
- 共享： 任何地址都可以使用该对象。需要通过Mysticeti进行共识排序。
- 不可变（冻结）： 任何人都可以读取，但无人能修改。永久且不可逆。
- 包裹： 存储在另一个对象的字段中。只能通过父对象访问。
这种所有权模型正是Sui并行执行能力的核心：针对不重叠的自有对象的交易无需共识即可并行执行。例如，地址间的代币转账、单人游戏操作和个人资产管理都针对自有对象，可同时运行。只有针对共享对象的交易（如与DEX池或共享市场交互）才需要经过Mysticeti共识排序。
Move instead of Solidity
使用Move而非Solidity
Sui uses the Move programming language instead of Solidity. Move enforces resource safety at compile time: objects cannot be duplicated or silently dropped. This is fundamentally different from Ethereum's approach, where the EVM uses gas-based pricing to prevent abuse at runtime. In Move, invalid resource handling is a compilation error, not a runtime cost. Ethereum developers must unlearn the gas-as-safety-mechanism mindset — on Sui, the compiler prevents resource misuse before code ever runs.
Sui使用Move编程语言而非Solidity。Move在编译时强制资源安全：对象不能被复制或静默丢弃。这与Ethereum的方法根本不同，EVM使用基于Gas的定价在运行时防止滥用。在Move中，无效的资源处理是编译错误，而非运行时成本。Ethereum开发者必须摒弃“以Gas作为安全机制”的思维——在Sui上，编译器会在代码运行前就防止资源误用。
Programmable transaction blocks
可编程交易块
Programmable transaction blocks (PTBs) batch multiple commands into a single atomic transaction. You can call multiple Move functions, pass results between them, split and merge coins, and transfer objects, all in one transaction. This composability replaces the need for multi-transaction workflows common on other chains.
可编程交易块（PTBs）将多个命令批处理为一个原子交易。你可以在一个交易中调用多个Move函数、在函数间传递结果、拆分和合并代币、转移对象。这种可组合性替代了其他链上常见的多交易工作流需求。
Key differences from Ethereum
与Ethereum的主要差异
| Concept | Ethereum | Sui |
|---|---|---|
| Data model | Account-based with contract storage mappings | Object-centric with typed, owned objects |
| Smart contract language | Solidity (EVM bytecode) | Move (compile-time resource safety) |
| State storage | Shared global state in contract storage slots | Individual objects with unique IDs and ownership |
| Transaction composition | Separate transactions or internal calls | PTBs batch multiple operations atomically |
| Parallel execution | Sequential execution of all transactions | Parallel execution of owned-object transactions |
| Safety model | Gas-based runtime abuse prevention | Compile-time resource safety guarantees |
| 概念 | Ethereum | Sui |
|---|---|---|
| 数据模型 | 基于账户，使用合约存储映射 | 以对象为中心，使用类型化自有对象 |
| 智能合约语言 | Solidity（EVM字节码） | Move（编译时资源安全） |
| 状态存储 | 合约存储槽中的共享全局状态 | 具有唯一ID和所有权的独立对象 |
| 交易组合 | 单独交易或内部调用 | PTBs将多个操作原子化批处理 |
| 并行执行 | 所有交易顺序执行 | 自有对象交易并行执行 |
| 安全模型 | 基于Gas的运行时滥用预防 | 编译时资源安全保障 |
Rules
规则
- Always frame Sui explanations around the object-centric model. It is the foundational concept.
- When comparing to Ethereum, emphasize the shift from shared-state contracts to individually owned objects.
- Do not describe Sui as "just another EVM chain." The programming model is fundamentally different.
- The Sui Stack components (Walrus, zkLogin, DeepBook, Kiosk, Seal, Nautilus, Randomness) are native primitives, not third-party add-ons.
- When describing the Sui Stack, always include concrete use cases it enables. Cover at least 3 distinct categories from: DeFi, gaming, NFTs, identity, social, and supply chain. See the use cases section in .
ecosystem.md
- 解释Sui时始终围绕以对象为中心的模型展开，这是核心概念。
- 与Ethereum对比时，强调从共享状态合约到独立自有对象的转变。
- 不要将Sui描述为“又一个EVM链”，其编程模型存在根本差异。
- Sui Stack组件（Walrus、zkLogin、DeepBook、Kiosk、Seal、Nautilus、Randomness）是原生原语，而非第三方附加组件。
- 描述Sui Stack时，始终要包含它支持的具体用例。至少涵盖以下3个不同类别：DeFi、游戏、NFT、身份、社交和供应链。请查看中的用例部分。
ecosystem.md