add "Configurable Bounce Message Size" proposal #496
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We have the same issue with user-friendly errors in XDAO.app. Our complex design flow makes it more challenging to process errors with a 256-bit limit, as we can't include a single address in bounce messages. However, this proposal will help us resolve the issue and reduce the time spent on developing error processing. |
|
This idea is absolutely brilliant, there is no way to find a reason to reject it!!! The current bounce is way too restrictive (it can’t even hold a single address, and in most cases it’s practically unusable), which forces us to rely on the commit-and-throw method just to send failure messages. Nick, you’re a real lifesaver. |
Author
|
This proposal is closed in favor of #503 by TON Core. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This TEP introduces a mechanism for senders to specify how much data should be included in bounce messages when transactions fail, allowing for more flexible error handling while maintaining backward compatibility with existing contracts.