sui-move

Writing Sui Move smart contracts requires using Sui-specific object model patterns and correct ability design for structs. This guidance enforces idiomatic code by separating Sui patterns from Aptos Move, preventing incorrect transfers and build failures.

Debugging and reviewing Move contracts on Sui involves checking ability design, event patterns, and standard library usage. Applying Sui-specific correctness guardrails helps identify non-idiomatic code and prevents costly mistakes before running tests.

Sui Move does not support the same design patterns as Aptos Move due to its unique object model. Enforcing strict Sui-vs-non-Sui pattern boundaries prevents incorrect resource handling and ensures smart contracts compile correctly.

Sui Move packages fail tests due to non-idiomatic patterns, incorrect abilities, or improper event and error configurations. Reviewing object model implementations and standard library usage resolves test failures and ensures correct module behavior.

Setting up a Sui Move package for shared-object modules requires configuring modules with correct abilities and event patterns. Following Sui object model design patterns during setup ensures the contract compiles and passes tests.

Specific abilities in Sui Move structs are needed when defining object model behavior for resource transfers and event handling. Correct ability design separates Sui patterns from Rust-like habits, preventing incorrect API usage and build errors.