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

Specification of GRAM trasnfers #38

Open
phil-dolgolev opened this issue Sep 25, 2019 · 0 comments
Open

Specification of GRAM trasnfers #38

phil-dolgolev opened this issue Sep 25, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@phil-dolgolev
Copy link

phil-dolgolev commented Sep 25, 2019

I think that all community need specify GRAM transfer process, cause current examples from HOW-TOs is not enough, and possibly some part of community start development with assumes that in their services need create separate account/address per client. It's bad approach, cause require more commissions, specific workarounds for frozen accounts and storage for all shardchains for all created accounts.

In https://test.ton.org/smc-guidelines.txt proposed good ideas with comments in messages. This approach is similar to Tags from Ripple and Memo from EOS, and very robust in TON, cause every account should pay commissions for code/data, and it's allow decrease technical requirements for installed TON Nodes.

I think we should specify transfer process according to smc-guidelines, possibly develop special contracts/explorers for awesome work with it.

Under specification I assume something like this:

  • Message should be 32 symbols length
  • Every symbol should be in [A-Z]|[0-9]
@phil-dolgolev phil-dolgolev added the enhancement New feature or request label Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant