Guide Sui Move object modeling with ownership, storage, and transfer patterns.
npx skills add https://github.com/MystenLabs/skills --skill sui-object-model
Please help me install this Agent Skill. Skill: sui-object-model Source: https://github.com/MystenLabs/skills/tree/main/object-model Command: npx skills add https://github.com/MystenLabs/skills --skill sui-object-model
It solves confusion and costly mistakes when modeling onchain data in Sui by explaining how objects work (structure, versioning, ownership) and how to choose the right storage, transfer, and access patterns.
Use the sui-object-model skill to answer: “How should I model an inventory that holds arbitrary NFTs and keep them transferable according to my rules, including the right ownership and storage pattern?”
High-intent search queries and answers about installing and using this skill.
Dynamic fields store values by hashable names, while dynamic object fields preserve object structure for direct access. Choosing dynamic object fields keeps nested objects transferable and independently owned within Sui Move collections.
Model capabilities as objects like AdminCap or TreasuryCap to manage permissions in Sui Move. Transfer the capability object to an address, requiring the caller to pass it into functions to prove authorization for restricted operations.
Object ownership affects parallelism in Sui Move because address-owned objects allow transactions to execute concurrently without consensus. Shared objects require global sequencing, reducing parallel throughput for operations touching them.
To delete a Sui Move object without drop, explicitly call delete_obj in a module function and pass the object by value. Unpack the object's fields first, ensuring inner objects are transferred or deleted individually.
Use Table for typed key-value storage in Sui Move when keys and values share specific types. Use Bag for heterogeneous collections holding diverse types, though both require manual cleanup of dynamic fields upon deletion.
Implement custom transfer rules in Sui Move by restricting transfer functions to internal module logic and omitting public transfer. Use Receiving<T> patterns or keep objects address-owned to enforce non-transferable soulbound behavior.
widnyanaGuide Sui Move smart contract development with Sui-specific object model patterns.
0x-ShashiMap Sui Move object ownership and lifecycle to surface security vulnerabilities.
dwallet-labsIntegrate Ika's 2PC-MPC dWallet workflow into Sui Move contracts for cross-chain signing.
Canhada-LabsAudit Solidity smart contracts for security vulnerabilities and best practices.
