What Sui Move Checks—and What Formal Verification Still Needs to Test

Originally published November 14, 2026, at 12:01 p.m. (UTC+8).

Sui Move’s type system and verifier provide security guarantees, but they do not cover every property a protocol may depend on. An article on Certora Sui Prover identifies five gaps to examine: bits lost during shifts, signed values stored in unsigned integers, privileged functions without caller checks, unchecked object ownership relationships, and older package versions that remain callable.

The author discusses vulnerabilities involving Cetus, Aftermath Finance, Typus Finance, and Scallop, and expresses the gaps as verifiable Certora rules labeled P1–P4. The article also extends the approach to protocol invariants labeled P5–P8. It suggests using test_scenario and Sui Prover to test the gaps.

For builders, the practical point is to define the property and its assumptions before attempting formal verification. The verifier cannot establish a requirement that has not been specified.

Source: learnblockchain.cn (originally published 2026-11-14 12:01 UTC+8)

Further reading