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