TIP: 8 Title: Bounce message size Author: Anton Platonov <email@example.com> Status: Discussion Type: Core Created: 2021-06-16
This TIP proposes increasing Bounce message size from 32 bytes to a bigger size (e.g. 1024 bytes).
Current Bounce message size is 32 bytes and first 4 bytes are always Function ID. That leaves the developers with 28 bytes (224 bits) of effective space to recover bounced message contents. Assuming the call has several variables (including
uint256 types), current approach to handle the Bounce is creating local variables that store each call information.
Increasing the limit even to 1 Kb will allow most of the functions to bounce the variables back properly and contracts to receive all the data needed for Bounce processing.
P.S. Currently it costs 0.01 TON in forward fees to send 1Kb of data in Free TON blockchain.
P.P.S. New Bounce message size is also a subject of discussion.