Vlad Frolov

@alexastrum It would be awesome if you could sum up what work is left to be done. I see this draft implementation for near-sdk-rs: https://github.com/near/near-sdk-rs/pull/776

> I want to take over authorship and push to finalize this spec and its standard implementation. @alexastrum I think you can go ahead and prepare a PR, and this...

*(I am cross-posting this message for visibility from here: https://github.com/near/NEPs/pull/245#issuecomment-1351844674)* Hey folks, I want to give an update here as it seems that the work regarding this NEP is not...

There has been quite an old discussion on nearcore about different encoding schemes: https://github.com/near/nearcore/issues/2100 Personally, I prefer hex as it is commonly used for hash representation, straightforward, URI-friendly, stable in...

@telezhnaya Thanks for bringing it up here, and proposing a change that we can review. I feel we need a better structure there. "Tokens" section reflects the common implementation detail,...

@bowenwang1996 Should this be merged eventually? Can you reassign the reviewer?

@garvitgoel Thanks for opening up the conversation! Could you, please, elaborate more on the action items here and what immediate next steps you believe should be taken?

> So it would be good if someone from the standards team could take a look at that I don't see anything the standards team can offer here unless there...

@lachlanglen Do you see an opportunity for improvement in NEP-171 (NFT standard) or maybe introducing a new NEP regarding TokenId naming strategy allowing more efficient implementations down the road?

@uncle-T0ny good catch! I wonder how to proceed with this. I feel we should take down the MT standard from the nomicon and get them back to the NEPs (neps...