Skip to content
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

Closed
aleksandr-hramcov opened this issue Apr 15, 2022 · 9 comments
Closed

Remove truncation of the body of bounced messages. #140

aleksandr-hramcov opened this issue Apr 15, 2022 · 9 comments

Comments

@aleksandr-hramcov
Copy link

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.

@30mb1
Copy link

30mb1 commented Apr 15, 2022

Must have feature, will simplify contracts logic much

@itgoldio
Copy link

Must needed feature. Pls, just do it!

@Futurizt
Copy link

WIP

@abionics
Copy link

Waiting for this feature for a long time!

@cassandrus
Copy link

It was proposed long ago - https://forum.freeton.org/t/tip-8-bounce-message-size/10866

@NoamDev
Copy link

NoamDev commented Apr 17, 2022

i believe this will be very useful and wil finally allow real error handling.

@mnill
Copy link

mnill commented Apr 18, 2022

Why this was not solved already? :-)

@cryshado
Copy link

Good idea! That must solve a lot of problems. Signed.

@bvscd
Copy link
Collaborator

bvscd commented Nov 7, 2023

Already done

@bvscd bvscd closed this as completed Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants