Contract Standards Work Group Call – NEAR DevHub June 30, 2023

Captions as YouTube publishes them, usually machine-generated, so product and people names can be misheard.

1. 0:05

   to the fifth contract standards work group call my name is Maxwell I'm a community moderator and contributor working with Dev Hub and I'm looking forward today to us uh going and looking at a new token NEP and coming to a decision about it so here's some you know background about the agenda we'll just go through these things before we get into the meat of it um I'm just going to give some context about the new developer ecosystem and introduce all the participants and then we'll get into the name we did

2. 0:39

   the discussion and open it up to q a if anybody has shown up to ask some questions so to get started Let's uh discuss the purpose of today's call we're here to vote and come to a final decision on net 393 which is a new token standard for what you call a soul bound token on a the near protocol we're also here to celebrate the effort and time that everybody invested into this NEP as this has gone through a rigorous review process and has taken the time and effort of a lot of subject matter experts as well

3. 1:16

   okay so before we jump into this let's give a little bit more background on our process so Dev Hub is a current year initiative that we're looking to decentralize nearest development and really open it up to any interested members of the community um we provide the social structure and tools to empower anybody to contribute to near from submitting ideas on dev hub for people to discuss to actually contributing the code that we may eventually Implement into the protocol

4. 1:47

   or as a contract standard or something like that so today our main tool for interfacing with this organization is this near devhub.org it's a boss component and this is our main platform for new developers to contribute and stay informed we have various communities on this website that you can join and get involved in or create your own and this is a great place to meet with other like-minded

5. 2:12

   individuals to brainstorm make proposals and also to get technical support and also funding now in additional to these uh informal groups that we have on dev Hub we also have our formalized work groups who help make decisions on various ecosystem areas such as protocol and contract standards and these groups have selected recognized experts who engage in the community and help review proposals in a fairer and timely manner so for example they help come to decisions on technical proposals that

6. 2:45

   you may want to get integrated across the ecosystem such as contract standards or improvements to the protocol anyone can submit an idea for a technical proposal using an NEP it's our formalized uh format for making improvements to the protocol and we have a process that will that's detailed in this mep-001 that we tape all of these through to come to a final decision review Implement all those sorts of things

7. 3:19

   as part of this process we have four e responsibilities in this in this um formalized process we have the author of The MEP himself who writes and presents the proposal takes it through reviews we have the moderator which is Ori or myself who who facilitates this process and discussion and kind of helps to move things along we have technical reviewers who get involved to go through the proposal and the implementation and kind

8. 3:51

   of submit comments give feedback and suggestions of what things people can change and then finally we have this recruit itself which functions to approve and finalize the proposal so these are the three stages that every MEP will go through first you have an author that creates a draft you move it to a review it gets reviewed by reviewers people give suggestions it gets revised and all of this is done in a very transparent asynchronous way on GitHub and one sometimes on dev hub

9. 4:24

   and finally once we take it through all these reviews and all these edits and approvals we take it to this final formalized voting call with the uh with the working group which is what we're here to do today all right so let's highlight the participants that are actually involved in this MEP so we have Robert who is the author of this proposal we have um Ori who helped to move things along and myself who is here just to leave the call we have our viewers because I'm their

10. 4:58

    dad and Alex a and then we have the contract standards work group working as our approvers we also invited the wallet group to participate but in the end they chose not to um just wanted to point out that as Robert is the author of this proposal he will not be voting whether or not to approve this uh this Ned which means that it's only two people voting on this but I guess that's what we're left with and uh now I guess we'll get into the meat of the actual NEP so first I'd like

11. 5:30

    to have Robert present a summary of the nap and why that's important and from there we'll have the work you've discussed and ultimately get to the final decision so Robert if you're there I'd like to take it away sure yes hi everyone um could you switch to the to the uh to The Nap page itself Maybe like if you can open that up okay anyways right anyways like the summary here is in the in the screenshot right so um the the goal of of the standard is

12. 6:09

    really to um to provide a standard interface which will allow to compose um different contracts and different use cases yes for sbts in a way how we use it for fungible tokens non-fungible tokens or like even the house which is coming up soon so uh I think it's like obvious why we need a standard interface for you know all sorts of tokens um and like here the major thing is that

13. 6:40

    uh SBT like it took us probably eight months right to like get into this final shape and then the main um founding finding here is that SBT is really not nft initially we wanted to model it as nft it's a non-fungible token but eventually uh we arrived um earlier this year in fact the model where um we we really separated and another thing is that you know um SBT must have internal economical costs of transferability so transferability is

14. 7:20

    possible but it must be limited in a way that it as the name suggests so Soul bands token so uh the transferability is limited yes to to keep bonding that bounding the token right to the soul um so this is what it's all ordered about uh we um at the beginning we explain how um how this banding Works what's the what's the cell so soul is basically a property of an account that it has kind of a digital identity

15. 7:59

    and the main focus we are very of of design of this design is really like a human identity um so this leads us to like various decisions um notably the the major one is the separations of concern between the registry so where the tokens are registered the balance book and the issuer so who and how issues the tokens so traditionally this is done in the same smart contract so let's say if you have your own smart contract let's say um USD team

16. 8:37

    then it will have both these use cases in the coded in the same contract right so it will have the logic of of issuing token and also it will have authorizing yes the issuance and also a logic for for recording the token yes here for the reasons mentioned previously so bounding the soul to an account as we we decided to separate it um it also unlocks few interesting properties notably what I call a semi-atomic transfers

17. 9:12

    so um we can like really do some migrations between accounts in a way that um it will limit the um let's say civil attacks or like a civil Behavior that um a malicious user yes would like to keep them I mean avoid the system of uh of really bonding this all to an account yeah so that's like from high level this is the motivation um uh we have a primary use case which we are working on for

18. 9:47

    for a while already right so I am human uh it's already in production we got uh two beta releases and finally the the final release around April this year uh we also like successfully change the issuer so we proved various Flows In in that within that model so in our first Beta release we we had like one issuer which we used to qualify Humanity over a time we change it um we prove that the model works it allows for compatibility notably for

19. 10:26

    elections for for voting for nominations for like now the the next area of research implementation it's kind of a kudos right so it's not only about like approving Humanity but you can also like proof um with SBT uh your membership to a community and again like allow it to I mean combining it then with Humanity so let's say you have a proof that you are a member of a community and you're a human uh then you can have like a more specific

20. 10:58

    um rules for for let's say for a governance um or um other notable examples yes are related to uh to a finance where you want to let's say can create like a more and dedicated instruments while knowing that say someone is okay firstly a human or maybe an institution with a specific background or um uh Financial requirements so all this is possible also like we don't here need to share like any specific information so it's open the standard the whole

21. 11:37

    standard is open how uh how the I mean like the relation between the the token and the proof of what this token represents right it's it's not really uh a part of the standard this is open in the same way how let's say um uh proof of um what is called proof of Reserve right for let's say values um uh stable coins is is done so I think that's enough for the like a general introduction um

22. 12:10

    we we have like many more use cases described in the um in that net so yeah please have a look all right awesome um thank you so much for that summary and your submission and work on this NEP um Robert would you like to like give a quick overview of like potential benefits that sort of thing like just in general the uh of introducing the I know you just touched on some of this in your overview but

23. 12:41

    right so actually like this nice also like um uh already let's say outline that um the the main use case here is is really like you know creating that kind of a properties for the accounts which are not possible today with uh with nft so for example NST could be very good for representing a real world asset right like maybe a picture traditionally or a car a wine a unit of a gold right but um but as good it's more suited for

24. 13:18

    um for a property ownership um I mean human Clarity or let's say entity or property right um uh uh this kind of things right and finally right like because this property is bound to the soul yes we have like all this all this definition right it allows us to create some simple resistance mechanisms for many many use cases also like you know like the whole whole thing is it's really driven by the um decentralized Society so if you look like more broadly in the research of the

25. 13:51

    centralized societies this all done is really like the foundation of of the model proposed by um uh the idea cool thank you all right um so we have like some of these concerns that were posted on GitHub a lot of these are still marked as open would anybody like to like take us through some of these and whether we should you know mark them as resolved completed or right so actually we had yeah actually you had a

26. 14:25

    discussion about it I kept them open because um I thought that we would close them basically we made this decision today and if there's various concerns yes that will be like publicly sharp here so I guess that uh with uh two other um uh standard uh contract standard work group members we basically like you know Mark them or I mean might become like as a closed or add maybe some additional notes

27. 14:54

    how about that yeah that sounds pretty reasonable can you Robert probably uh like read or like conceptualize each individual point and right then so let me let me go one by one and then let's say we do like a voting so the first one is about like the snap uh NFL 70 171 is nft right and that's one of the early concerns where we were really discussing uh that's already different last year in fact if um

28. 15:25

    uh if SBT should follow some of the um um uh nft interfaces or events in order to keep compatibility and the reason for the motivation for for having that compatibility was really to um um have for free the support from the existing ecosystem right tools indexers and so on over a time you realize that that would require some patching that's um it's not desirable and instead of like adding a

29. 16:03

    compatibility layer which could potentially create a wrong implementations or maybe like technical depths for the future yes we decided basically to really separate it so even if some events would make sense from NST perspective right we decides okay let's just separate it because those those two are two different entities um also like another motivation for like the separation was that we we agreed to use the class which is like this you know um another level of abstraction so if

30. 16:42

    you if you anyone is familiar with this multi-token um uh idea multi-talken standard yes we can have kind of like a class or a namespace for the token this is similar to what's in ethereum ERC 1155 or like a fractional fractionized fractional nfts here we adopted it from the get-go basically because it really composes well about like certificates some additional proofs in a way how the um

31. 17:17

    issuer would like to like qualify or separate and that's let's say a different expertise for the same user so overall uh the the here like the funding from various comments is that okay uh we uh we don't do like any compatibility layer and we do dedicated interfaces and dedicated events yeah this was uh originally brought from my site when the original nap was submitted with more like more closely resembling non-transrual nfts and the

32. 17:58

    argument was that we don't we would create a lot of Burden for for the indexers and the rest of the ecosystem uh collapse into two uh so I I was insisting on having a different uh prefix and like a couple completely different namespace and now looking at the final version of the nap I'm I'm glad that we did go that route because there are many more uh specific extensions to to those events to to the methods and they would be very hard and

33. 18:32

    non-intuitively smashed into the existing like nft nap if we would follow that route so I'm glad that it's it's a separate thing and we don't need to discuss that compatibility and burden that that could put into the system so totally agree that's yeah resolved now correct yes and like this argument of a technical depths it turned out I think to be real yep okay so the next one is I mean does anyone else have like a different comment if no let's go forward

34. 19:11

    okay now um some memo fields in um most of the let's say transactions yes we include the manual field related to uh so again like SBT could be like used for some legal terms legal as like legal actions yes which might have some uh um legal relate to like a legal action okay so Unchained transaction yes which has to be reference to some uh Real World um action and this is why we have like an

35. 19:50

    animal field think about it like you know in money transfers Bank transfers we have a memo field as well which we use I mean as we call a reference um in various other let's say blockchains yes the memo field is part of the transaction rather than like a function called in nap 141 we you have the we have the memo field right so the concern was okay do we want to include it in event or not so the reason is that okay with the I propose here to basically not include it

36. 20:21

    it's part of the transaction there is an event even is always linked to a transaction so there is no need to copy it right so like the idea of the event here okay like the motivation at least I want to or the narrative yes I want to provide here is that you know event should be something that you know like many indexers or off chain um applications will listen for and and then like based on that like react so let's say it should like have something that is like a menu it should not be a

37. 20:53

    copy of the transaction right because but it should be like really meaningful what is the purpose of the transaction what is that transaction about right the transactions for example can be a bundle of few different actions like let's say um a transfer maybe account creation um or uh I don't know again Newport creation uh bonding things like that right so um so technically that's why we have these events right because we uh we

38. 21:23

    can have few different actions in a single single transaction I think we don't need to go into like very deep all right details uh so overall I think we are like all in agreement that's uh okay uh memo is like optional and even in in nft uh world it's not very widely used so let's let's see without it as part of the standards if anybody needs it they can edit no no it's extendable uh the events

39. 21:54

    the support would be limited but it's fine I guess so moving on to the next one I can probably take it uh so there is a concern about token spam and given that you can't burn and transfer away the tokens um there is there was broadly concern that well what to do with those uh cell bound tokens issued to your account and I I think it's the same uh problem all around in in FTS and nfts as well uh spam and flood

40. 22:28

    is uh like is there and and people will spend their tokens and I don't think it's uh it's our like it's job of the standards and it's not the job of the owner to burn those tokens so I think we can just uh rely on the uh like on the um wallets and other entities who display the the data to just filter out the spam that's right so here actually yes the concern was like okay that we I mean should we require it or not

41. 23:01

    required as a part of the standard so from the very beginning the standard defined a burn event that you know tokens currently burned however the standard doesn't require a specific function and the reason for that is that the burn function can be different for various Registries right so let's say also it could change like let's say if you want to be more specific how the burn Works what arguments what extra let's say arguments should be provided that's that's why we don't keep it right

42. 23:32

    it's not needed for composibility here uh if we will find like a solid use case we can always add it right but um as an extension but it's resolved now for current state yeah let's move on uh multiple Registries can you shed some light on it right so there's also like a spicy uh discussion about it so mainly because we have the saturation of concern that um there's issuer and registry and what if one issuer will try to issue the same

43. 24:07

    token for multiple registries so first of all like we cannot dictate that there is only let's say one blessed registry it doesn't work in the permissionless blockchain right um so we can make a recommendation right but we cannot we cannot require it so the concern is valid like if one issuer will um will issue the same token in the Registries and then kind of a duplicate but the same argument so our recommendation is of course to not do it but we cannot enforce it

44. 24:40

    and the same concern in fact is in any other traditional uh token right so if you have an nft representing again your picture and the issuer decides to copy it you can prevent it right if there will be like a second bold Apes collection exactly the same by the same issuer you cannot do anything about it right so it's a permissionless blockchain so um that's basically um yeah I would call it out of scope for

45. 25:13

    for the standard exactly more concern for the audit for specific contract rather than the standard uh also I mean we made the recommendation that you know how this should be interpreted right like how it should be used but that that was the founding here right we made the recommendation yeah let's move next uh yeah the multi-talkends are like to approve it or to not have it yeah so at the beginning we're talking about it discussing like who needs it who doesn't

46. 25:44

    need it at the end of the day we found that okay let's do it because uh it provides a better model if you do it from the beginning that issuers can like you know really separate the different sbts in fact also in I am human right it turns out to be helpful because let's say there is a community SVT right and Community has Beauty can have like a few different types like OG or maybe uh I don't know like a community Master

47. 26:13

    something like that and those will be represented as as a different class so that's the the multi-token approach so again like um the month of um of application it I mean using it in in big project turned out to be to be really helpful for proving this approach yeah makes sense to me though it seems like it's a different approach like it's not completely multi-talken standard it's just some like variation of it that makes sense for the SBT rate

48. 26:52

    correct kind of right because multi I mean the the near multi-token standard is for the fungible tokens right so this is like have multi-talken for I am in isil called multi-token it's technically not a multi-dog can write but the idea is similar is that we have like another level um in the model so you have token ID and you can have numbers several of them uh yeah and you have like a class so like you have issuers then any issuer can have okay like you know the site so I mean like a few principal examples so

49. 27:26

    let's say you have University right and then the class will be that okay what is your graduation I mean the class will represent both your graduation year and the uh the strategy that you made right so uh instead of like creating multiple issuers each issue will represent uh let's say a tuple uh you know the university the graduation year and the uh and the study you did so instead of that you have like issue value which is a university so you keep

50. 27:59

    the The Entity which is you know providing the certificate the same and uh the graduation study will be here modeled by the class and then hsbt is basically like its certificate for that study so now that's like one example another like I mentioned with the community and the team okay sounds good let's move on um right so uh use of milliseconds as a Time unit um yeah so again like various comments

51. 28:28

    here um the the motivation about like using milliseconds okay like we were considering seconds milliseconds or nanoseconds um right so um yeah the let's say default in here is of course nanosecond right but uh like if you think about like a block propagation right it and and I mean how where this millisecond is used so the millisecond is only used for the expiration time right and given that you know all of these are transactions we don't need to go to this let's say nanosecond

52. 29:06

    um precision and if I remember correctly okay I don't remember now but if I remember correctly NST is also using the nearly Second Son that was like a second argument I mean initially I wanted to do the seconds but because I think nft was using um milliseconds we decided to um just for context it's a hard balance to strike here um the conflicts environment exposes the nanoseconds time Precision from near

53. 29:43

    blockchain so the like if you just use the like nearest Decay standard function to get the current timestamp you will get it in nanoseconds Precision already so you will need to do any operations and like you just use that number um the problem however is that it doesn't fit into uh like number Precision value in in JavaScript so it's more than uh two in power 253 and then it it just it loses the Precision and it's like you don't it doesn't matter that much but it's it's cutting some

54. 30:25

    like precise number at the end um and and seconds is not enough because it's uh basically um we could have several blocks in the same seconds and probably uh not a great idea to have like potentially colliding to to events in single second right I mean because you wouldn't have like attack Collision yes because you always have like a strict rule I don't know either if it's the first one or not

55. 30:56

    but anyways like a million seconds have basically way more advantages here right it's also like compatible with what we use in a web so that's that was the final rounding right so I think we agree yeah I guess I guess so okay so the next one is burn um I think we already like made that um I repeated her burn because uh actually part of the standard and the token stamps are kind of similar right so in a token spam I mean Vlad you already commented here

56. 31:29

    uh I extended.com and yes that we don't add burn as a part of the standard but we keep the burn event as a part of the standard yeah it's the same story with nft ft events as well like the excitement and burn methods did not make sense but events are very valuable for indexers exactly properly track uh what's what's going on okay so the next one is the salt transfer so the salt transfer is like

57. 32:02

    this unique thing um or a unique feature yes of SBT and in fact that's what we got really qualify as between so salt transfers is like a special um action let's call it this way uh where we allow in fact a token to be transferred by a user rather than like glow back or enforced by the issuer what kind of recoverability and the reason for the sole transfer is that you know like users at the beginning don't think that much about the identities right

58. 32:35

    like very often like we realize that lay down down the line that okay we made some mistakes but you know creating many identities or like at the beginning creating our let's say public identities where we would like to start rather not fully public and this kind of things however right because of the composibility how it works here and maybe like some mechanisms would enforce us you know to merge some accounts or like proof that um

59. 33:06

    for whatever reason right that you know one account should be merged into another one so like you know we want to move the soul from one account to another one uh then then we need to have some way yes to to handle that use case so this is really what the sole transfer is uh and um at the beginning the sole transfer was part of the standard and so the function um later on uh like firstly as we change the implementation and that triggered me in fact to

60. 33:43

    um not put it as a part of the standard in the same way and the motivation here is again the same like as a mint mint is not part of the standard but means even the spark of the standard so here's the same thing right uh salt transfer is is not something that you know one contract can request for another one but it's something that you know should be rather ad hoc and um uh and we didn't include in a standard later if if needed probably it can come

61. 34:13

    as an extension today we don't see it seeing it that this will be part of the standard however yes again the the event the event is part of the standard all right and I guess I'll just kind of quickly go through this last one um there's a couple concerns about privacy you can see here that the uh comment one and two are and just pull this up really quickly um these are quite involved answers so

62. 34:46

    if uh people want to know more um please just take a look at the uh the net page and and read through the comments here so we'll just kind of move things along from here I guess if that's all right with everybody yes this privacy was like this classical I'm not sure should I like summarize it a bit if you can yeah maybe like a one minute summary something like that that's right so there were a few Concepts that you

63. 35:20

    know since the SBT kind of um can qualify your identity right it can be used to uh deducts like a real identities right so it's a valid concern right but you know if someone would like to like specifically deduct it by so my mind point is here the following right like uh we really recommend that to not include any personal information in SBT right but uh it's in fact like cannot be enforceable because I can create a token and I call it deducts

64. 35:59

    and I can only know I know all the accounts for whatever reason and I will accept I will that would be non-transfoldable nft and that token has will have like a memo field or whatever a reference and you know I will be a troll and I will just mint it for already or we will not be able to like to all this account and I will put his name his address everything there I can do it this is a permissionless blockchain in the same way I can do it like in a spreadsheet and share it with

65. 36:28

    everyone then Google spreadsheet and share it with everyone right and if I will do it anonymously right then there is like no even like a legal litigation that you know someone can can find me to because I'm serving personal um personal information opening the internet so yes it is sorry it is a real concern right we cannot do much about it uh in a in a let's say open permissionless world you can only do recommendation to to keep it private

66. 37:01

    um also yes um I think that you know we should go to towards more like a ZK related stuff so the the standard is like you know more following the approach of of like a traditional token standards right where you know balance token balances and everything is public right because um it's really like targeting uh existing new ecosystem and hopefully yes this will be upgraded once we have more Primitives more

67. 37:33

    um more work done related to um to zero knowledge um Frameworks directly in here and I think like the standard won't need to change yes because then we would like the the SBT can represent a proof um or a Cavaliers proofs yes without um telling anything right so it will it could be like even like um the reason that my account has an SBT might not even like mean anything because let's say the proof can be that

68. 38:05

    even not valid right so there's like a various ways how this can be upgraded um but that's more an open reset okay sounds great all right uh actually there is one more like we discussed it um like one more concern I think it's about the token ID let's not sure do you want to to talk about it we didn't include it here but that was like a chat about it uh two hours ago well there was a concern about

69. 38:37

    the actual type of uh token IDE uh the original proposed like the current the current map seems to be uh asking people to use uh uh unsigned integer up to uh two in hello kittens uh yeah uh Power and then in JS world if you try to digitalize it you will lose the Precision if if the value is more than uh two in the power 53 so my proposal was to in order to avoid the uh the hustle for uh JavaScript developers who want to be compliant with the standard uh is to

70. 39:17

    either turn it into a string which was the approach taken by nft contracts and standards or um explicitly state that the value should not be more than two in the power of 53 so JavaScript developers can you know sleep without problems you know uh thinking about the their like token ID could collide with something else by just you know leveraging the numbers um and yeah dude what what did you decide to go with right um yeah thanks so um

71. 39:59

    um that's also a kind of an interesting concern I mean like already at the beginning in the um in the design yes I made like a narrative about it uh and there are like a few motivations for me to use a number rather than a string uh so like firstly number it's also a kind of a uh like moving the using a string is in fact asking developers to use a library rather than a native type directly correct because uh uh like the JavaScript doesn't work with

72. 40:32

    that like even if you use number I mean if you want to use number and then like really put it in a string there has to be a library as to to validate that uh so like if you are going in that direction then we are already let's say saying asking everyone okay sorry you need to use a library this is how it works um and my motivation is in fact like from the beginning we have still thousands of years before this will be

73. 40:56

    like a really problem for the JavaScript developers based on an analysis I made um and issuers like technically should not have that problem because they can like even combine it with the with the class which I mentioned before which in fact not doubles yes but Powers too the the space so uh in fact like I required in the registry to use like a sequence because issuer cannot request the registry so in this model the current model in

74. 41:26

    the in the interface issued cannot specify the token ID it's the register which has the balance book and keeps track of that of the of the tokens so registry doesn't know like what should be like the next token ID or like what are the what are the fee unless they double or copy the the balance book right so I require in the registry that you know they should use like a sequence numbers to like avoid potential problems related to let's say different values different

75. 41:57

    token distributions so that's one uh second drug you know combining with with a Class A Class ID that you know the space is in fact like open not for thousands years but for Millions years right so um basically I don't see it a concern and I would rather prefer to have like a native types and JavaScript is evolving maybe we'll use wasn't in the next 10 years or maybe in 100 years uh so yeah hard to say they made like

76. 42:28

    what would be the decision what would be the best decision like in the next hundred years or a thousand years and based on this analysis I think uh for 253 right it gives us I don't remember but if you open it it's like tens tens of thousands years or um let me quickly find it all right I think yeah it didn't matter but it covers that shall we move on from now yeah twenty eight thousand years overview yes okay all right so moving along with the nmd

77. 43:02

    process we need a two-thirds majority to move forward with this net which I suppose in this case means that the both of the non-authors would need to approve we've already had indications provided on the GitHub discussion thread and here's a quick summary we have an inclination of yes from that and from uh Sasha I'd like to invite you to speak first probably and given that you didn't have a chance to put the word here

78. 43:34

    um yeah hello so basically like my idea is that we are on the states where we just got a reasonable um design you know like a reasonable design variation from everything we discussed and um kind of we can spend one more year to polish it however it just doesn't make sense you know like from my my perspective is that uh it's totally reasonable to kick the standard off you know to make some um impact on the Lyrica system like

79. 44:19

    let's let's move on uh so this is my perspective you can see that we have uh uh 333 comments on the GitHub you know conversation it's red and um of course we have trade-offs and in any complex design you will have trade-offs you will have some you know unpolished things and at this point like I believe like we fixed critical things we don't have red flags at this moment and you

80. 44:55

    can see that Robert just had put a lot of thoughts and he can you know he can not just explain but uh you know deeply go into every tale so that's why I give like my approval my consent and yeah um my consent is here Oh Yeah from my point of view I I totally agree with with what Sasha just said basically we uh there is no there is always room for Perfection and we can uh always find what what to tune but I I don't want to call those back from

81. 45:34

    potential Evolution like uh much bigger changes once we will have a real production use uh I think we can always revisit and issue new standards no no Pro if that is it turns out to be uh like the findings that we'll learn will outweigh the the problems of migration so overall I feel like this standard is already good enough to be implemented and called in production and it's not a huge scope for

82. 46:11

    integration from the uh like wallets point of view or indexers so it should be uh fairly straightforward for them which is which was my concern initially with no non-transportable nfts for example uh so yeah I totally totally support the snap so let's let's get it trying awesome and uh Vlad you mentioned a few next steps here yeah I I try to outline the immediate next steps uh for for us to

83. 46:48

    basically be on the same page uh so first we need to fill out the change log section on the map uh Robert can you do that please uh so basically what's it include it should include is per previous examples you can open previous maps for references uh it should like there will be a video recording of This call uh and you please integrate the benefits and concerns tables uh from like preview discussion that we already have here so just bundle bundle together

84. 47:20

    into the nap uh document so it's much easier for the future reference instead of Sky through the like over 300 comments uh or whoever will read it in the future um and second step would be for like I can take it I will just approve and merge an app on the report cell uh and Robert then it's on probably on you again to endorse cell bound token support in wallets uh there is no other

85. 47:53

    way around uh you we need some Champion to to brag about it to uh to to to show the uh the benefits and like the use use cases and I'm sure that you have the all the context there to uh to make it true so I hope this makes sense to you guys and we can move forward it sounds like we're all I've already read about the approval correct just making sure that we're formalizing this correctly sorry all right yeah and the final maybe word is that like you know um

86. 48:37

    we got like a really I mean Real World Adoption with NDC for that and it took like many people in fact uh I mean it's not only me yes but like many people like votes into shaping it so I would also like to thank you like everyone uh from NDC for um for helping with that and moving with moving it forward oh yeah sure we we actually have a slide right uh Maxwell about like just mentioning the the

87. 49:09

    thinkings and yeah the thing is like this of course um yeah so it's definitely it's it's important to recognize that we have like uh over a dozen uh people can like just uh leave in the comments and reviewing this snap document on GitHub but I'm sure there were other reviewers of the code of the smart contracts uh itself so it's a it's a truly Community effort here and I'm glad that we have so many uh people

88. 49:43

    uh like pushing it Forward uh championing it and uh it's it's our pleasure to to support even though we like as a working group members we need to be a bit harsh and make making sure we're standing on the on the guard okay so maybe let me like uh endorse you like a few people here sure yeah right so firstly I mean no AG with who I started that uh so thanks also for like you know like going into the reviews helping with like putting that attacks together

89. 50:13

    and then Henry the NDC Champion for like you know uh helping on uh getting the group together and and working with that then like every developer in NDC for like really using it using it testing it like playing with it um Alex alexstratum from uh I forgot the the project name right so he's championing like another nft project so he also put like all independent like few independent thoughts into that

90. 50:46

    um and uh yeah finally the the world group members so thank you Vlad and and and Sasha for like a few reviews I know that it wasn't like easy for you like to go through like all the site comments because you know then like we were bombarded with hundreds of of of comments from multiple people and then you had to decide okay what to do I mean should I read this hundreds of comments or not right

91. 51:11

    so um yeah and like like I said everyone else from the NDC yeah and thank you Robert for championing and pushing it through like since when it was open it was open in September 14th last year right so it was it wasn't like and and it started way before that I imagine given that you already came up I was just I was just looking it up uh when near Khan was and we came in short of a year July 16 I think was a near-con learning that's when we had uh the first

92. 51:49

    hackathon about this nircon was September I think September something yeah it was in September all right all right sorry yeah but that was already championing this idea in the summary all right yeah yeah now you were so just a year that's a lot of effort thank you Robert at least it means that it aged enough you know like a good wine I think it's comments awesome thank you guys yeah thanks very important

93. 52:22

    um I guess I'll just uh put a bell on this then um if anybody's looking for ways to get involved in this kind of process in the future um I'm just going to quickly highlight a few ways to get involved in the ecosystem uh if you have a specific idea in mind you can submit it using Dev Hub and find communities to collaborate with you can work on and submit at NEP like the one that Robert worked on for such a long time here and put so much thought and effort into

94. 52:54

    and you can also view all these MEPS on the board on GitHub these are the contract standards any fees that are currently listed there right now um if anybody would like to submit more you know that's where to do it and of course you can get involved in the contract standards community group here on the telegram so you can kind of see that here and if you're not already involved you know we have a more than

95. 53:20

    150 people there now I think so um and if you want to learn more you know follow our Twitter and telegram channels and uh please use and interact with Dev Hub in the future so um thanks everybody and thank you for bearing with me on my uh first attempt at moderating one of these hopefully it gets a little bit smoother in the future and yeah again thanks to again to everybody and congratulations on all the hard work that people put in and all the deep

96. 53:52

    thinking and all that so yes thank you very much and we'll uh see you on the next one I suppose there's nothing scheduled for now but uh keep an eye out I know the multi-token standard is still moving along and hopefully we'll see more of that coming in the in the coming weeks so all right thanks everybody again for showing up