bit-shift-safety

To prevent Move VM aborts, you must identify and analyze unvalidated bit-shift operations in Sui Move code. This involves inventorying all shift sites and evaluating their abort risk to ensure shift amounts do not exceed critical bit widths.

A static analysis security audit on Sui Move requires scanning modules to detect unvalidated bit-shift usage. You inventory shift operations, classify their sources, and trace cross-function propagation to evaluate transaction abort risks.

Cross-function propagation allows unvalidated shift amounts to pass through function calls and reach critical bit widths in Sui Move. Tracing this data flow is essential to accurately evaluate abort impact and identify hidden vulnerabilities.

Yes, bit-shift safety analysis applies across both Move modules and scripts within Sui-based projects. It inventories explicit shifts in public or sensitive functions to evaluate abort risk across the entire project.

You inventory bit shift sites in a Sui Move project by running a full static analysis scan of the source code. This process enumerates all explicit shift operations in public or sensitive functions and records findings with traceability.

Unvalidated bit-shift operations cause Move VM aborts when the shift amount exceeds the critical bit width of the data type. Static analysis identifies these unvalidated shifts and evaluates their risk to prevent transaction failures.