Description

As described by the Tact documentation↗,

When a contract sends a message with the flag bounce set to true, and if the message isn’t processed properly, it will bounce back to the sender. This is useful when you want to ensure that the message has been processed properly and, if not, revert the changes.

To handle these bounced messages, the contract needs to implement bounced handlers — for example:

contract MyContract {
    bounced(msg: bounced<MyMessage>) {
        // ...
    }
}

There are no bounced handlers in the pool contract, despite many of the messages being sent with the bounce flag set to true.

Impact

Depending on the intentions of the contract developers and the way the contract is used, these missing handlers could be undesirable.

Recommendations

Create bounced handlers for the messages that are sent with the bounce flag set to true, implementing the logic that is appropriate for each message.

Remediation