NEP-636: Sharded Fungible Token

[mitinarseny]

Sharded Fungible Token standard

NEP text: WIP
Originally discussed at: #607 (comment)
Reference implementaton: near/near-sdk-rs#1376

[gagdiez]

Hi @mitinarseny, any updates on this draft? need help with something from the contract standard's working group?

[mitinarseny]

Hey @gagdiez, I'm constantly adapting the reference impl when noticing some inconsistencies or things that can be improved.

The NEP will be more tied to & motivated by the reference impl than it is for regular smart-contracts due to NEP-616 mechanics and strong dependencies on the initialization state. The most non-trivial and important part is to design ABI in such a way that it will be compatible with other extended implementations as well.

I'll publish the NEP text as soon as we're sure that this main concern was fully addressed and we have a clear path for extensions and how they should be implemented. I have some ideas in the PR so far and I would appreciate if interested people, including contract's working group, can leave their feedback/suggestions there first as it would be easier to keep track of them, due to close relationship to the actual implementation. 🙏🏻

PS: I recommend reading through this discussion first: #607 (comment)