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.
Proposal that will prevent the loss of user funds in case of erroneous sending address update proposal #123
Suggested behaviour:
bounceable
flag from address representation should now be taken as "force-bounceable".When sending, wallets must accept this flag as follows:
if
true
- all messages to this address can ONLY be sent in bounceable mode, even if the destination contract has an uninitialized state.if
false
- means that a non-bounceable message can be sent to the destination address.The wallet app checks the destination address - if it has an
uninitialized
state, then it sends a non-bounceable message, otherwise it sends a bounceable message.Since only wallets will use the non-bounceable form, it will also be possible to distinguish the wallet from the service smart contract using this flag.
Old:

New:
