A detector that identifies suboptimal message passing functions that could be replaced with more gas-effective alternatives.

Tact 1.6 introduced more gas-effective alternatives to send that might decrease gas consumption when used properly:

  • message: a regular non-deployment message
  • deploy: an effective contract deployment function
  • cashback: more efficient way to send the remaining balance

Using suboptimal send functions might lead to out-of-gas attacks, especially when using at hot points.

let init = initOf SomeContract(p1, p2, p3);
send(SendParameters{
  to: contractAddress(init),
  code: init.code,
  data: init.data,
  value: 0,
  body: FooBar{}.asCell(),
});

Use instead:

deploy(DeployParameters{
  init: initOf SomeContract(p1, p2, p3),
  value: 0,
  body: FooBar{}.asCell(),
});

Hierarchy (view full)

Constructors

Properties

category: Category = Category.OPTIMIZATION
severity: Severity = Severity.MEDIUM

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