NEAR Contract Standards Working Group Meetings, 18 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Contract Standards Working Group Meeting – November 18, 2022

Description

The second NEAR Contract Standards Working Group Meeting!

Today the working group covered some of the recent NEAR Enhancement Proposals (NEPs) and voted to approve NEP-276, an extension proposal to the Payout NFT standard.

Chapters:
00:13 Agenda
00:39 Update on Developer Governance and the NEP process
03:55 Introductions
06:30 NEP Discussion: NEP-200
08:36 NEP Discussion: NEP-249
10:23 NEP Discussion: NEP-276
14:01 Voting
19:42 Q&A
21:37 Getting Involved

Learn about Developer Governance:
Website: https://neardevgov.org
Twitter: https://twitter.com/NEARDevGov
NEP Process: https://github.com/near/NEPs/blob/master/neps/nep-0001.md

💬 Join the Contract Standards Community Group:
Telegram: https://t.me/nearnft

Review the NEPs from today's call:
👉 https://github.com/near/NEPs/pull/200
👉 https://github.com/near/NEPs/pull/249
👉 https://github.com/near/NEPs/pull/276

Join NEAR's community:
Website: https://near.org/
Reddit: https://www.reddit.com/r/nearprotocol/
Discord: https://near.chat/
Medium: https://medium.com/nearprotocol
Blog: https://near.org/blog/
Twitter: https://twitter.com/NEARProtocol
GitHub: https://github.com/near https://github.com/nearprotocol
Dev Docs: https://docs.near.org/
Create a wallet: https://wallet.near.org/create
Apps on NEAR: https://awesomenear.com/
Learn to Build On NEAR: https://www.near.university/
Grants & Funding: https://near.org/grants/
#Blockchain #FutureisNEAR #NEAR #nearprotocol
#nft #dao

A

Good morning, hi everyone, my name, is Ori Applebaum and I'm super excited to welcome you to The second contract standards, working group meeting so just to go over our agenda today. First I'm gonna do a quick overview of developer governance. Then we're going to do brief introductions, then we'll jump into the main discussion, which includes some recent naps that we took a look at as well as the main one that we want to formalize, a decision on which is payout and if the standard extension and then we'll open it up to q.

A

A and lastly talk about next steps and how you can get involved so just to go into developer. Governance updates uh for those of you who may not be familiar. We've been engaging with the community over this concept uh for the last few months, and really this is about decentralizing nearest development and empowering anyone in the community to contribute to evolving the ecosystem and we've been bucketing developer governance into three areas or stages, I should say ideas, voting and implementation and just to go into the ideas.

A

Basically, anyone can submit an idea for improving the the protocol of standards and it starts with the community from individuals to uh to groups, and there are several Community groups that have self-organized around various topics and they have been meeting and coming up with ideas and submitting next, and that's really.

A

Cool and you're welcome to join any of these Community groups or start one yourself, and once you have an idea yeah, you can submit it through a net in your enhancement proposal, and this is a similar process to other open source projects like rust and basically, we've introduced working groups in the voting stage, which allows them to basically take a look at these naps.

A

Help move them forward, make decisions and we've we've picked several subject matter: experts to stand each working group and already bootstrap this process and had recent meetings and yeah very excited to be doing that today, with the contract standards group, so just to highlight the roles that are involved in case you're not familiar. There are four key ones: author moderator, reviewer and approval. The author is the person who writes the nap and presents presents it here in the call.

A

The moderator is the person who facilitates the the process and helps ensure that MEPS move forward reviewer, provide technical expertise and just make sure that you know the net is viable and then the approvers are the working group members who make the final decision, and they do that through this process that is outlined in nep001. It includes three stages: draft review and voting and two outcomes approved and rejected, and most of the activities in this process happen. Asynchronously like on GitHub, except for the voting stage, which is what we are doing today.

A

That's when we schedule an actual meeting with the author and the working group members to formalize the vote so just to touch on the last stage implementation. This is an area that we're still actively developing, but the idea is that, once an app gets approved, we want to be able to enable anyone, whether it's the author or somebody from the community to actually implement it, and so we're currently working on an overarching Dao which will be responsible for funding distribution from the near foundation and other orgs, and there will be more information coming soon.

A

So just again. To put it all together, we have Community which submits ideas using apps working groups which vote in those naps and help them move them forward and then implementers who Implement them for the benefit of.

B

A

So with that super quick overview, I'm going to jump right into today and do the introductions. So first I'd like to welcome the working group members and introduce them so I'll hand it over to Marcelo.

C

Yeah, thank you. Eddie uh hi, everyone uh again, uh I am Marcelo from from Aurora I've been involved in your community since, uh probably for years now and yeah. Looking forward to see uh like make this uh built in heaven.

B

My name is: I am working at Pagoda for more than three years and I'm working on the core protocol and cryptography at in near.

D

And hey everybody, uh I'm Vlad I, also work for God and joined quite early on and I've been involved in developing the Explorer and the indexers. So we have and well I helped to shape some of the Naps previously and I'm happy to be part of the working group members these days. So thanks everybody so.

A

Just uh moderator in the process today is myself, so I already said hello, but just hi again and excited to be here and now I'd like to move it over to the author of the nap that we have today, William so hi William.

E

Hi I'm Willem I used to work at UH Pagoda well before it was Pagoda and now I have a company called aha labs and we develop uh develop tooling for near and now with the new grant for uh sorbon Stellar's near the VM Charles, also in wasm, so um I've also written, probably the most popular uh nft contract for launching collections and um that's how I got involved with this NEP, because I was one of the first to develop what the payouts or use the payout standard, and so this NEP is just trying to fix some issues that I found with it.

E

And um you know my implementation is probably the most widespread, so it doesn't match the standard. So I just wanted to. You know, have parody later.

A

Well, welcome William and we're super excited that you're still actively participating and and contributing, and we're excited to get to that next discussion in just a moment so cool before we do that. uh We're going to start, as I mentioned, with the other two recent maps that we looked at and I'm going to hand it over to Vlad to talk uh through them. So, let's start with NEP 200, so yeah.

D

Just a little bit of context, so, as already mentioned, we actually started this developer Gardens not so long ago, and it's all only the second call for this group and we were actively looking into the backlog of different proposals that were sitting there for too long to be honest, but it's it's still the time to uh to address them, and this was the nap 200 which suggested to extend the nap uh nft nap 171, the the the proposal was to add three new methods into the the reality that we first of all lost the momentum when it was proposed.

D

The second we haven't seen any demand to have those methods, and if we introduce them these days, we would need to arrive to some migration strategy how to how to make sure that all the new contracts can reliably work together. I mean the the old wouldn't be hurt in any way, but the new ones adding those methods uh would not have a huge help because the um from the user's point of view, they would need to account for the chance that these methods are not implemented there.

D

So, overall, uh together with the author, we decided to reject this map and keep it in in the Box uh and but still like. If, if you want to pick it up, feel free to follow up with the discussion, it's all we try to communicate everything on the GitHub pull request. So if you think that you can improve and propose a new nap, please go ahead and do so so, let's move to the next one.

D

So the next snap that was proposed quite some time ago was about adding in a standardized method, called ft mint to the fungible token contract for fungible token standard uh and the the reason we rejected it is to fold. First of all, the main purpose of that method was to introduce observability uh from the outside world, like indexers, to notice that something some new tokens were minted. This was actually addressed with later in time, but quite some time ago, as well.

D

They through the fungible token Json events which are already implemented in in the standard sdks, and the second reason for rejecting this proposal is that the there is usually no standard way to mean tokens. They are usually minted when the contract is created on initialization, you initialize, you mint the initials total Supply and then, after that, rarely there is like a standardized way to meet new tokens.

D

So this was the was discussed extensively in the comments and we agreed that, together with the author as well, that it's not needed anymore and we closed it with the rejection. So now we are coming to the uh more exciting news, and then this nap 276 right and I I'm passing the stage to William, who is the author, but.

E

Yeah, so um basically, this was an extension of the nft transfer, um API and and I noticed when I was implementing it, that that was missing the memo uh parameter, which meant that internally, the you would always pass. None now I haven't used memo in any of the things that are, you know I, but at the same time this is you know it should be used by any.

E

uh You know third party, that's trying to facilitate a a sale, so if they want to use a memo for whatever reason this this allows them to do it um I. Also, uh the the max uh Lynn method was uh also required, um with the idea that you know this contract would uh not allow a certain number of payouts uh and fail, but um I think that that's also a little too strict. Considering that you know the contract itself will understand the the run out of gas.

E

If that's an issue and then have a fallback, so you either fail because of that option or you fail because of gas, but they have the same result.

D

And I guess: I guess that approval lady became optional right well,.

E

uh Did that change too I.

D

E

um Well, I, guess that is that also optional on the nft transfer, Yeah.

D

So basically reflect reflect reflected the state of things there: okay cool, so let's uh go to the next slide and I will take it from here. I I wanted to summarize the benefits of that I identified when I was reviewing the the snap that we finally resolved the misalignment of this method, which should be very similar to nft transfer in Ft transfer call uh as William already mentioned, memo was missing approvalid he was required which shouldn't be, and the Max land was not always useful in all the cases.

D

So it's great and this there is no breaking changes. There is no system, Fork, so I think it's safe to move forward and if we like, if we would talk about the blockers and potential concerns, uh I haven't found any uh that are still outstanding, so um I think it's uh overall all good to move forward to the voting stage right already. Yeah.

A

Unless there's anyone else that has any concerns that they'd like to surface so.

A

Okay, I see a comment from Nate and I'll. Read it one technicality that William pointed out the assert one yokto should still exist, as hashtag payable only specifies that you can attach near to a function call everything else looks good.

E

Yeah, that's uh I, I added the payable back and that that's still, um you know, uh yeah.

D

The change was rewarded and like now we are all good yeah, thanks for mentioning Nate.

A

Yeah thanks Nate Nate, says neat, so I think we're good to continue unless anyone else has any other comments, cool all right. So now we are coming to the final uh voting stage and I guess.

A

I would like one of the working group member to maybe uh present a decision on behalf of the group or, if you each want to speak individually, that works well. uh Yeah.

D

I'd like to take a word here, but uh I I well, I want to ask Marcelo and you need to maybe just also chip in and waste their decisions out loud. So we are like kind of have the the Quorum here.

D

um How do you feel guys.

C

um Yeah, thank you. Vlad um I myself have uh read the snap I'm, not that involved in the development of smart contract using this standard, but it kind of under understood the description and I think this is a pretty easy decision that it's mostly improving and have no drawback, so yeah on my side, I'm uh onboarding, yes,.

D

C

D

Thanks Marcela you're gay.

B

I'm also voting yes, mostly for the same reason that were already mentioned here. It makes the IPA more consistent and it doesn't, it doesn't introduce any new real functionality. It just makes the API more consistent and it doesn't have any downsides that they could share.

D

Yeah totally agree thanks, Phil for like fixing this misalignment for sure. I feel like this is a small, but yet very important uh nap to to make sure like, like the standards, are clear and aligned and uh useful, and also reflect this. The reality that we have, as you said in the most used uh implementation out there, so I was supporting for yes uh merging it right moving forward.

E

Right yeah I, wish we had this process when we first wrote the payout, because I don't think this would have fallen through. Also the one thing that I started out when I wanted to with this NEP was to you know. Paris at the time was just using a hash map to represent the the payouts and uh but the the standard says that that the hash map should be embedded inside of a struct, um but then, as Nate will attest to the mint base.

E

It already uh used that because it was in the standard, so they didn't want to have to deal with two different data types. So we're stuck with the it's extra wrapping, I.

D

See a c: well, it's good to know that we we recognize that there is potential breakage of the ecosystem. If we do certain sharp moves and yeah.

E

Yeah and there should be like more eyes on on a standard before it.

B

E

Know gets uh widely spread because then yeah thanks.

A

Yeah so very exciting, so I guess uh I heard we formally are voting yes to approve this move forward, so we can definitely, uh after the meeting, uh add that to the nap and take the next steps. Speaking of the next steps, let's talk about that.

D

Yeah, so basically I noticed that there is already Implement uh implementation submitted to near SDK arrest, which is almost ready, I, I think, uh and the only missing bit is just addressing the remaining comments. uh This is quite an old PR. It's from April this year and uh I'm not sure like how we'll address it, um given that the author could have potentially moved on.

D

So if you, if somebody who is watching this or like willing to take it on, it, would be awesome to to see this follow-up from the community.

D

uh Javascript SDK seems to be not having um support for this at all, like at least at least I haven't seen the it's in the pull request State, um but, given that the structure, the project is almost identical, maybe it's it's not that uh problematic to Port it once the rust version will be there, so I'm definitely encouraging um Community to chip in with with the contribution to those is the case and the in terms of like next steps from our from the working group point of view, um Ori and I serene's moderators for the naps and collect process will need to merge this pull request and making sure that we have all the meeting, notes and summary of the decision recorded there.

D

So just FYI we're keeping track of all those things on GitHub is our single source of truth truth. So you will find, if necessary, all the references there I, don't think we we need to do anything like beyond that. I think this nap will be adopted. Well is already adopted, as Lily mentioned uh implicitly through the implementation on the contract side, um but we can also like add it to. We still I think should add it to the SDK. So it's more widespread um cool.

A

Awesome yeah so I think now our next step is just to open it up to.

B

A

Already see that Albert posted something, so we can look at that, but also what I want to add is uh if you have any feedback on the process uh and just how we can make it even better we'd love to hear it as well so yeah we encourage anyone to speak up.

A

You can either type in the Q a or in the chat or request to speak, and we can let anyone do that so yeah, let's start with Albert's uh first uh Point here, which is I, would love to help with the JavaScript libraries I'm, not the best java Dev, but I'm learning and growing. Let me know how I can help.

D

Yeah I can probably take it from here. I guess all the contributions are welcome for sure. uh Please follow up with the near SDK GS repo and start from learning from there. How like the nap 171 was like smart non-fungible tokens is implemented there and consider adding also inspecting how it's done in in Rust SDK. This uh pull request that I just mentioned, and maybe just Port it almost file by file into it and see how that goes, but I think it's.

D

uh It could be, have a lift for somebody who is just starting uh with with like learning JavaScript um but yeah I'm, encouraging and I would love to see you succeed for sure any other questions. Do we have.

A

D

It's like no, no other questions. Okay,.

A

Cool all right so just to touch on more ways to get involved. In addition to uh Albert's uh comments, so uh I want to say that there are many ways to get involved and, as Vlad mentioned, we just recently kind of started, uh developer, governance and and this process so very much we're bootstrapping this and we're open to feedback. But let me share some of the ways that anyone uh can get involved. So if you have a specific idea in mind, uh we absolutely welcome you to author and submit a nap on GitHub.

A

You can check out the net001 Just for information and best practices, or you can talk to William who who's just went through this process and can probably share uh insights. The other thing you could do is discuss upcoming next, uh so just join uh discussions that are happening uh here are some open contract standards and apps that are in their review stage. That are probably going to be good candidates for uh close to decision uh stage. So please take a look at these and then oh wait. I see a question.

A

Let me know Albert just asked. Let's say: I need help with something. If I had a question on the library who can I contact, is there a form.

E

You can always ask questions on Discord, but I think opening an issue or discussion on the relevant repos. The best way.

A

D

There's a really good.

A

Vlogger sorry, we're gonna say something.

D

uh Yeah I was saying that totally second, that uh suggestion to follow up on the relevant people.

A

Yes or if, if you maybe uh have an idea or you don't necessarily know exactly what you want to build, you just want to discuss something in an early phase. Another great way is to join Community groups, as I mentioned earlier on the call and there's actually a telegram channel for the near contract standards. Community group. It has about 141 people as the last time that I checked uh so feel free to join that telegram, Channel, but also to you can start your own community group.

A

If you have a topic uh in a different area, Albert Rhodes thanks a lot I will follow up on repo. Can you send a Discord link too? Do you have links to these groups perfect? Thank you bye for posting. That uh then the other thing I wanted to mention is you can join other working group calls and I just wanted to put a plug for the next working group meeting, which is happening this Monday, it's the protocol working group and we're going to be making a decision on net 366, which is meta transaction.

A

So if you're interested the link is over there and also I will share another URL, that's a little bit easier to to copy and paste. Actually, let me copy this and put it in the chat so yeah, and this is the general link so near.org developer governance has information about everything we discussed and the ways to get involved, and we also recently launched a Twitter account near devgov. So we encourage you to follow that and and over there we'll be posting about more naps and more meetings in the future.

A

So this brings us to the end and I want to say a huge thank you to William for submitting the snap and for taking the time to come here, to discuss it with us and with the community and also for the working group members who took the time to review it and give your your your thoughts and to the community and those who attended. It's really awesome that we're starting to make progress, and hopefully we'll continue to do that. So thank you all. Take care.