How can a builder check whether an addition contract behaves correctly for every input? An article published on September 1, 2026, compared three tools using five variants of a simple Soroban contract. Three variants contained bugs that broke commutativity—the expectation that swapping the two inputs does not change the result—but only for particular inputs.
The comparison found that the fuzzing tools cargo-fuzz and Komet quickly found obvious or more easily triggered bugs, but missed defects that required precise inputs. A clean fuzzing run therefore meant no bug was found, not that the contract was correct.
Certora Sunbeam, a formal verification tool, could instead produce a counterexample or prove that a specified rule held for all inputs. That offers a stronger guarantee for the rule being checked, though the article noted that verification can also time out.
