ton-blockchain/highload-wallet-contract-v3

highload-wallet-contract-v3's Issues

Critical omission in the wrapper | internal_transfer value

Since Highload V3 sends itself an internal message before sending the main batch, we need to set some value to this. However, in the wrapper this field is optional (which it should not be at all) and in this case the whole balance is sent, which deprives Highload of its meaning, because while this balance is wandering somewhere, other externals may fail or there may be an error on Action Phase when receiving internal_transfer.

In such a case, the contract will show that the message is processed, but it will not be processed.

The second omission is created_at, which by default will always fail because the time on the user's computer or server will always be greater than the time on the LiteServer.

It's not written about these things anywhere and it's very strange that the wrapper doesn't handle this either. As a result, it is very easy for a user to run into these problems, because it usually means it doesn't affect anything much.