NEAR Tools Working Group, 19 Jan 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Tools Working Group Meeting – January 19, 2023

Description

Today the Tools Working Group met for the first time to vote on: https://github.com/near/NEPs/pull/418

Meeting Summary:
https://bit.ly/3D2wrqQ

Chapters:
00:11 Agenda
00:52 Update on Developer Governance
07:07 Introductions
11:02 NEP-418 – Author Summary
13:18 NEP-418 – Benefits
15:01 NEP-418 – Concerns
21:04 NEP-418 – Voting
24:51 Getting Involved

Learn about Developer Governance:
Website: https://neardevgov.org
Twitter: https://twitter.com/NEARDevGov
Telegram: https://t.me/NEARDevGov
Dev Gov Gigs Board: https://devgovgigs.near.social
NEP Process: https://github.com/near/NEPs/blob/mas...

Join the NEAR Tools Community Group:
Telegram: t.me/NEAR_Tools_Community_Group

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

A

I'd like to say hello, everyone and welcome to the first near tools working group meeting. So first I'll give a quick overview of developer Gardens. Next, we will do some brief introductions. As we have a few panelists joining us today, then we will get into the main discussion. Snap 418 and the link for the nap is on the invite. So you can follow us over there and after we'll open up a q a session.

A

So if you have any questions drop them down in the appropriate section and lastly, we'll talk about the next steps and how we can get involved in the developer. Gardens General, going forward. The developer Gardens is still shaping and I'd like us to walk through the the latest view on the framework that we are trying to build here for the everybody's sake and benefits.

A

Over the last few months, we've been engaging with the community over the initiative, which is about bringing people and organizations together to help build a decentralized developer governance and a system for near Community. They want to empower everyone to contribute from idea to code. We've been bucketing most of the developer community of activities into four buckets right.

B

A

Ideation and implementation review and support and I just want to quickly highlight them and bring some context. So first variation is about sharing, exploring dat radius. So it's the very first step and we'd like everybody to be able to to have a place where they you can share your ideas and iterate on them. It's very important to have such a place. So we have. We are all on the same page, because previously we were scattered across all sorts of resources.

A

Now we have this gigsport, which helps us to bring everybody to the same place, make it a feat of new ideas, sparkling there and also further iterations that we will discuss shortly. So if you want to share your idea, please check it out. There's hosted on your social by the way. Sometimes before you have an idea, you you want to to explore it and brainstorm before posting and Community groups is a perfect place to to do so. Community groups are self-recognized, it's permissionless you can join.

A

You can build your own, it's great tool for the community to ideate. We currently have a bunch of them already. You can see them on the screen and there are more on the go forum. For example, the zero knowledge group is shaping right now, and we also have tools and specific. We don't have specific working groups or Community groups uh like python tooling, so it's very narrow it could be brought to the narrow it doesn't really matter, and the next iteration would be then to jump into iteration or implementation.

A

And after you have an idea after you discussed it, there could be some somebody to submit a solution or you can also propose a solution initially. So this is Natural Evolution of your idea. Basically yeah. You can also help others to find the solution so feel free to collaborate there and it's also cost it's the same. Big gigs boards gigs board allows you to do so moving forward and closer to what we are having the meeting for today, which is in naps, which is more formal one.

A

We have this meeting with leading experts in the in the key areas we identified initially and we Define the standards for the Holocaust system here, and this is important to be aligned and help applications to build a certain expectations about how things could operate and what to expect from third-party applications and standards are helping us a lot.

A

So naps is crucial part in, in my opinion, to get this forward and scale then, basically, even closer to what we're doing today is the review stage once an app is submitted, experts will help to shape it and pass the review and conserve for approval, which is so basically this step involves experts, Auditors and currently working groups in general, helping us to move forward.

A

Currently we have four areas in the protocol: the contract standards all its standards, and today we are excited to launch a new one, the tooling working group, let's jump right into the structure of and like roles of the working groups or like mostly like nap process, and there are basically four key roles. The author anybody can, you can be the author of an app and submit the proposal and the moderators helping to bridge author with relevant experts and reviewers or subject matter.

A

Experts will help to identify the benefits and concerns trade-offs over the standards to be applied and approved, and the final official role is the approver, the working group members who we will meet in a few minutes and hear from them the maps their considerations about the current map that we're talking the net process on a high level looks in the following way. You you can see there are certain stages, but today we will specifically talk about this transition from review to voting, and this is how the process will evolve from from here.

A

Basically, and the final step of the decentralization is also gain. Support which is important. Support could be in form of all sorts of resources. It could be money, it could be connections, it could be integration with some Partners. So all sorts of things that you can request and expect people to also share with you and some companies will join against the board to find their Champions. So they can sponsor or just help with some expertise in the area. So that's basically the first overview of the the vulgar Gardens in general. It's very focused and narrow.

A

The only goal here is to make developer contributions successful. So, let's.

C

A

Introductions and meet those who joined us today. The first group of people that they want to bring to Stage are our lovely working group members who for who are forming our tooling working group right now. So let me hand it over to Sergey to introduce himself thank.

D

You a lot yeah hello. My name is Sergey like hiking, like cycling, bike buying ultimates and for the last two plus years, I'm in a new ecosystem. Working right now, at Pagoda on tooling, mostly like near aphs, near CLI, create new rap other stuff, like in 2022. We were working on on the SDK, JavaScript, SDK and yeah happy to be here thanks.

A

uh David, you can go next, hi.

B

Everyone I'm uh David I'm, the engineering manager on the tools, team um and I've, been with coming up to five months now. um Yeah really excited to um do the first one of these um slightly overdude votes.

B

uh Thanks for organizing this Vlad.

A

C

um So I'm Paul I have been working in your ecosystem for three years and uh I know. I worked in both course group and in um developer. Governors team and my recent work is in USD kgs and I'm, still uh working on releasing to 1.0 and I, also like hiking and camping.

A

Nice, uh so the next Brew people are moderators and I'm. Today, here joining us from the European Time Zone helping to navigate this call, uh Max and Ori are help helping me out as well for other working groups.

B

A

Let me introduce myself I'm Vlad I work for Pagoda for three years as well, and we I've been excited too exciting to work on all sorts of uh projects across the ecosystem, ranging from the airport south and then index service, Explorer, tooling, helping to shape developer, Gardens and working groups.

A

So this is where I'm staying right now and let's introduce our author of the map that we're going to discuss today, Austin Abel, who is former employee of pagoda, Inc and now, is a Community member and helping us to move any trade forward and shape the Naps.

A

Unfortunately, due to the time zone, we he couldn't attend the call today, but we synced beforehand and confirmed that everything is up to date in regards with the nap, and he believes that all their concerns that are listed on GitHub are already more or less addressed and he's happy to update PR. If anything needs to be added there. So I believe Paul will take the presentation of the nap for for hosting today, yeah, so, finally we're getting to the nap itself and the today we have uh one nap to review.

A

uh It's not for 418 objective is to allow attached deposit, in view context of a function called execution on here. So I'd like to invite Bo to speak to it. Yeah.

C

Thanks voila, um so this map is about the lower tax deposit.

C

In view context, um as uh Poland has introduced before, uh Austin cannot make this meeting so I would be uh represent him to to the other summary and on behalf of him, um so Austin was previously I want to add in a feature to the SDK that um to automatically adding like attached deposits for certain functions um because for the security reason like those um contract functions, should either accept the deposit or does does not allow deposit at all um further because we do not allow attachment deposit in view context, that is when the contract method is being built.

C

um So this cannot be added to.

C

By contact functions in the SDK level, so posting come up with this snap to propose to return the error for the test deposit in view context, and this will quickly enhance the dev developer. Experience 200 attack deposits for those not allowed deposit functions and, regardless of this function, being called or being viewed uh next slide. Please.

B

C

um So we I have briefly in uh describe how this will benefit. uh It will allow like, in SDK level, to adding another to all contract methods that shouldn't uh um shouldn't, accept and deposit, and this this will be measuring the behavior of ethereum and solidity contract with without a payable modifiers, and so this will be uh close to those who familiar with solidity and is intuitive to um we're.

C

Writing the contract that, without a payable modifier, this method won't be accidentally taken uh payments anymore, and this has to be done in as a nap instead of in the contract level, because there is no way to check in the function call is in, but it's facing a real context, so you cannot be like checking conditionally.

C

This is a view context and the attention deposit shouldn't be um shouldn't be caught, so in this snap it just make it both accessible, acceptable in real context and in call context and in for view context if this snap makes it to return zero uh yeah. So this this is all benefits um provided by this now.

A

Should we move to the interns.

C

Awesome um and uh I think so he made this slide um and he can give a better intro introduce to this.

B

C

Concerns please.

A

D

Okay, okay I'll do that uh yeah. So, as Bob mentioned, there is a lot of benefits, but there were concerns. Well, I'll briefly describe them. So the first one is that this proposal can trigger a protocol version change and we Market Market as resolved, because it appeared that it happens like on a client level, and it will not um affect things that will require protocol change so that shouldn't be a problem. The next one I think it's the biggest one that the the contract can assume that attached deposit will panic in view context.

D

So it's a it's a real breaking change, but the change the chance that it will uh actually be triggered is really really low. Like the and I would say that, if somebody was doing this, then it was not a great design of their contract yeah. So we decided that we, we can live with that and we will like not not fix it and we will not do something about it and the third one was not actually discussed.

D

I saw it in the nap itself from Austin, uh so the question is: can we assume that in all vehicles that H deposit in the VM context always zero, so I guess we can briefly discuss it right now, uh let's make a decision if it can affect our decision yeah.

D

So my my vision is on this is I I like I I, want to hear an opinion from somebody who works closer to to the core, but I guess that it should just Panic with attached deposit in new context, but yeah I'm happy to hear other opinions, foreign.

C

It initialized some VM contacts with uh default to zero if it's a integer type, that's the case for the context deposit, but we can always check if, if that's like, the default has been um set other eyes um and uh yeah I think we need to double check the source code to ensure that this this is always set to zero. For for view contacts um I should be able to. It should be enforceable and won't be. A problem in the implementation from may have more knowledge in the core.

C

A

Yes, as far as as I remember, the current limitation near core basically has two implementations for writing a function. So when the function is executed in regular, like transaction function call context, it has full um old implementations for all the host methods.

A

While when we are running the view function, there is a special host function, implementations and most of them are actually kind of panicking. Returning in error and attached deposit is currently panicking this way, so it aborts the bus, execution and I believe it's totally fine to re like replace that implementation to return zero, um and then there shouldn't be any expectations about non-zero value.

B

A

It doesn't make any sense to me to have non-zero early years, I.

D

I just know that, for example, in your CLI we're preventing that, like you, are not able to attach the positive you call, but it just you know, lists the logic on the client side. So I was wondering like is there? Is there any possibility to set deposits in some other way, not.

A

Right now like previously, it was not even allowed to be called so it, and it was the RPC level they that you would communicate with, and there is no Planters over there. Okay.

D

So then, I I think we can say that this concern is resolved as well and we can.

A

D

With the NFP.

A

C

A

All right, yeah, thank you, Sergey! uh Thank you both for presenting it and now that we've heard all the benefits and concerns. uh I would like to hear from each of the working group, member um and their opinion and how they are leaning towards the approval or rejection of the snap. uh So this basically brings us to the voting stage uh as per the map process and who wants to start first to communicate their opinion.

B

uh German seems to be a relatively minor change to have a decent amount of benefits. uh Instead of making it easier to write, simple view, function calls so it'd be simply thought about potential downsides. So it's a yes for me. Yay.

C

A

C

No I can go now well. I'm all I saw working group member I also lean forward to approve this IEP uh based on my knowledge on protocol and the polling. I think the proposed solution is a good addition to the trolling and the ways a very.

D

C

Case in in like breaking certain contracts, as we said in the concerns and other concerns are resolved so um overall, this is a very big net, a very good, nap and I think so. I'm approving it.

A

Yay second, yes, here, Sergey.

D

But not much to add benefits are clear. Concerns are like not really big and result so I'm watching yes, as well.

A

Yes, so we have unanimous guesses here, which brings us to the uh decision to approve the snap and we are ready to discuss next steps. It seems so, let's see our next slide. Okay,.

D

I can present it yeah.

A

D

So uh the person who will actually implement this is not uh decided yet not formed yet um and any implementation is not started. So if you're interested uh check the gigsport, it could be there and uh yeah. Maybe you will want to do that or we will find somebody inside of of our team So. The plan is to post all the results of today's call in the nap itself on GitHub, uh approve it, merge it and then make this call for for Champions on a geeksport yeah.

D

So it's a it's, not it's an it's, not a big nap. So if you feel like you're interested, please apply yeah.

A

Yeah in, in my view, it's a perfect uh starting uh first contribution type of nap that could be easily approved because we already have a nap uh supporting it. So it's almost a no-brainer for anybody to join and try it out to contribute to near core, and you don't need to even wait for the gigs board posting given that or the nap is there and they pull request.

A

You can just reference this net pull request when you're submitting a pull requesting your core, and we strongly encourage you to to try it out and yeah definitely would be great to see more people contribute in the near core all right. Thanks everybody uh for presenting it. We are ready for Q a I, don't see any questions. So, let's move forward with some close enough notes that I believe is important to understand better the future ahead of us and how to get involved into devgov in general.

A

uh So, once again, just to reiterate and the devgov gigs that near that social is where you can submit and search for ideas and collaborate there, um then they naps is another very important way to contribute on a more formal level. When you want to scale Beyond, just one application and you want to bring all the wallets up to up to speed or all the tooling up to speed, this is the best way to influence the direction. We also have the board on GitHub.

A

That is uh each year that makes it easier to follow along all like all the Naps. uh Currently, the tooling uh working group is has just started, and we only have a single um nap over there. But if you will follow this link, uh you will find all the Naps that are currently at different stages in different work groups. So you can contribute there and who knows? Maybe your view will help to shape the better security aspect of some naps or just bring some fresh ideas that are out to improve without trade-offs.

A

So we strongly encourage you to give a look. There is also a telegram channel for to don't miss the announcements and yeah in general. If you want to learn more, go to near devgolf.org and followed our Twitter Instagram account I'd like to thank you uh all: the community, the author of The Snap or sample the working group members, both Sergi and David who's, who helped a lot to move it forward and provide their expertise, also Marcelo to service.

A

Subject matter, experts for for this snap and the community who participated and joined us today and will watch this recording later on YouTube, it's uh team effort and I'm excited to see that we are shaping more and more dedicated working groups around experts and I hope to see more in the future of New York System thanks. Everybody.