Fix nep245

[marco-sundsk]

Now, we have a revision of this standard. This time, we focus on the combination of FT and NFT in those core functions cause we noticed some misunderstandings on FT and NFT workflow on near network in those interfaces. Beside that, we also make a supplement to the nep-0245.md to include all the extensions while leaving the one in specs untouched as a comparision base point, so that you could have a clear view about what have been changed in this revision.

The plan is to have an agreement on nep-0245.md first, then the corresponding fix would be applied to those in specs. And the standard code implementation would be the last.

The detailed explaination of this revision could be found in the discussion.

[frol]

Hi @marco-sundsk @ruseinov, thank you for pushing this NEP forward! I see that this is still an on-going effort, so as a NEP moderator, I marked this PR as draft and marked that it needs reference implementation (as per our discussion in Telegram, we don't need a full SDK-grade library implementation, we just need a standalone contract that implements all these methods and some client that demonstrates that the API surface is not lacking and ergonimic)

Please ping the @near/nep-moderators once you are ready for us to review it.

[victorchimakanu]

Hi @marco-sundsk @ruseinov, i'd like to understand the current status of this NEP.

[ruseinov]

Hi @marco-sundsk @ruseinov, i'd like to understand the current status of this NEP.

The status is that we have a small MVP in another repo that's supposed to drive this effort. I'm currently busy with other things, but planning to eventually come back to it.

[flmel]

Hi @ruseinov @marco-sundsk Do you still want to proceed with this NEP-fix?

[ruseinov]

Hi @ruseinov @marco-sundsk Do you still want to proceed with this NEP-fix?

At some point. Currently swamped, but hoping to come back to it sometime in the future.