[R4R]BEP12: Introduce customized scripts and transfer memo validation #17
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.
Background
For tokens on binance chain, recently exchanges tender to use a single address for client deposit and require clients to input memo to identify client account information.
This causes a lot of problems for both exchange customer support and clients. Clients may be panic when their tokens are missing and exchange supports have to verify the client deposit transactions manually. This is caused by that many users don’t realize that memo is required or they just forget to do that. What’s worse, sometimes their wallets don’t support transaction memo at all.
So we plan to implement a memo check mechanism on binance chain to filter out all transactions which are intend to deposit tokens to exchanges and have no valid memo.
Motivation
This memo validation can be used for any membership based deposit/charge business model.
This BEP also proposes an important infrastructure for customized scripts. In the future, more amazing features will be built on it.