TON Masterchain Contracts Formal Verification

CertiK14 Sep 2022Code version: not recorded (see the report)

CertiK reviewed TON (TON Masterchain Contracts Formal Verification) on 14 Sep 2022: 5 findings, 0 critical; 4 marked fixed, 1 open.

No open critical findings

Open the report Open TON’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings5

Statuses are the security firm’s own, from its report.

Severity	Open	Fixed
Critical	0	0
High	0	0
Medium	0	1
Low	1	3

Low`losses` is not updated if there are no votes inOpen

The voting configuration includes the parameters `min_wins` and `max_losses`, which are used to initialize new proposals. As we prove in this report, a proposal needs to win at least `min_wins` times in order to pass. If it loses more than `max_losses` times, it may be discarded. However, the latter is not a hard guarantee. The check for losses happens either when somebody votes for the proposal, or if the proposal is selected by the `scan_random_proposal()` function. If nobody voted on it for a long period of time, where the validator set changed multiple times and the proposal did not happen to be scanned, then the fact that it did not win in that period would not get recorded, so the loss count would be smaller and it could still pass.