-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove truncation of the body of bounced messages. #140
Comments
Must have feature, will simplify contracts logic much |
Must needed feature. Pls, just do it! |
WIP |
Waiting for this feature for a long time! |
It was proposed long ago - https://forum.freeton.org/t/tip-8-bounce-message-size/10866 |
i believe this will be very useful and wil finally allow real error handling. |
Why this was not solved already? :-) |
Good idea! That must solve a lot of problems. Signed. |
Already done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem:
Currently the body of bounced messages is truncated to 256 bits. In this case, the first 32 bits store the functionId.
This leads to the fact that it is impossible in the onBounce function to get sufficient information about the failed call.
When developing smart contracts, you have to save all the temporary necessary parameters in a mapping with the uint64 nonce key, make the first argument of the called function uint64 nonce, and then send another additional callback if successful for cleaning.
This approach cannot always be used and is not without drawbacks, as it can lead to an uncontrolled growth of temporary data and additional bugs.
Offer:
Do not truncate the body of bounced message and send all original data.
The text was updated successfully, but these errors were encountered: