A detector that identifies improper use of exit codes outside the developer-allowed range.

In the TON blockchain, exit codes are divided into specific ranges: 0 to 127 are reserved for the TVM or FunC, and 128 to 255 are reserved for Tact. This structure leaves the range from 256 to 65535 for developers to define custom exit codes.

When exit codes are defined outside this allowed range, it may lead to conflicts with existing reserved codes, causing unintended behavior or errors in the contract.

contract Foo {
    receive("foobar") {
        // Bad: exit code defined in the reserved range for Tact
        let code: Int = 128;
        nativeThrowUnless(code, sender() == self.owner);
    }
}

Use instead:

contract Foo {
    receive("foobar") {
        // OK: using exit code from the allowed range
        let code: Int = 256;
        nativeThrowUnless(code, sender() == self.owner);
    }
}
  1. Exit Codes | Tact Docs

Hierarchy (view full)

Constructors

Properties

severity: Severity = Severity.HIGH

Gets the severity of the detector.

Accessors

  • get id(): string
  • Gets the short identifier of the detector, used in analyzer warnings.

    Returns string

    The unique identifier of the detector.

  • get shareImportedWarnings(): WarningsBehavior
  • Defines the behavior of warnings generated by this detector when working with multiple projects within a single Tact configuration.

    Here are the available options:

    1. "union" Leave this value if you don't care about warnings generated in other projects.
    2. "intersect" If the warning is generated for some source location of the imported file, it should be generated by each of the projects. Example: Constants from an imported file should not be reported iff they are unused in all the projects, so you need "intersect".

    Returns WarningsBehavior

  • get usesSouffle(): boolean
  • Checks whether this detector needs the Soufflé binary to be executed.

    Returns boolean

Methods