An optional detector that identifies send functions being called inside loops.

Calling send functions inside loops can lead to unintended consequences, such as excessive message sending, increased gas consumption, and potential race conditions. Loops with send calls should be refactored to avoid these issues. This detector helps flag such code, prompting the developer to reconsider the design.

fun exampleWhileLoop(limit: Int, owner: Address) {
  let i = 0;
  while (i < limit) {
      send(SendParameters{ // Highlighted: An auditor should review the loop
          to: owner,
          value: 0,
          bounce: false,
          body: Msg{ a: i }.toCell()
      });
      i += 1;
  }
}

Hierarchy (view full)

Constructors

Properties

severity: Severity = Severity.MEDIUM

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