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

Migration flag EQ-UQ TEPs 123 #1

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

inozemtsev-roman
Copy link

Proposal that will prevent the loss of user funds in case of erroneous sending address update proposal #123

Suggested behaviour:

  1. 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:
image

New:
image

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

Successfully merging this pull request may close these issues.

1 participant