NEAR Protocol Community Group Call – March 29, 2023

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

1. 0:05

   to our third protocol community group calls I believe is the third one time flies if you haven't been in the group if you haven't been to any of the calls before just to give you a sort of overview so first of all this is the community group The protocol community group is a place where people who are interested in participating in discussions around how to change and improve the near protocol and this is where this is a place for people to come and discuss their ideas and get

2. 0:51

   feedback on their ideas or propose suggestions and uh and so on and be able to see what are the upcoming changes that are being proposed and uh get feedback on them and so on so forth um we do these regular calls for people to come get together and discuss different ideas different projects uh different topics so usually people will Pro so it's like the format is very open you know it's a free format discussion

3. 1:31

   people can come and say you know get speak their minds um everybody's encouraged to uh introduce themselves in the chat uh just so people know where you're coming from what what your role is and and so on um Ori and I will function as moderators so we will take notes and ensure decorum but we will not be we're not eager to make any decisions or any uh um we don't have any kind of authority here

4. 2:10

   um and finally we are recording this meeting and the meeting will eventually be posted on YouTube and a summary of the meeting will be posted on Twitter so please be mindful of that um when you are discussing topics uh uh so does anybody have any questions comments before we jump in all right if nobody does then we can um start with the proposed topics uh so these are the topics that we collected

5. 2:47

   from some of the topics that we couldn't get to from the last call and some of the ones that have been proposed since the last call um uh Ori do you want to take the first one the housekeeping one just so it's not only me who's speaking the entire time yeah so we had a couple topics the first one is about a recurring um meeting uh proposal so it seems like we've we've had quite a bit of topics in the last three meetings that we've had and a good turnout and so we wanted to

6. 3:17

   know if to make this just a regular ongoing thing and you know it seems to me like maybe a monthly uh proposal is something that maybe would be more doable for most people but if anyone is interested in doing a more frequent Cadence I'd love to find out so does anyone have any immediate thoughts or suggestions on that okay I guess silence is acceptance uh here's what I will suggest I will post

7. 3:49

   um a poll in the telegram Community uh group basically saying hey we propose doing this monthly option here a couple hear a couple of things and people can vote or propose Alternatives uh and then the other thing I wanted to ask was that even though currently Ikea and myself are the ones talking this is meant to be a community call for for anyone so the question is will there be any volunteers who would want to maybe help facilitate

8. 4:16

   the the next call and and by facilitates really it's just doing this it's kind of like starting welcoming everyone trying to keep everyone on on the topics so yeah if anyone is willing to please reach out or let us know in the chats um but uh yeah with that I'm happy to turn it over to the first topic that we have which is I believe a continuation from the last topic we had in our last call with uh Joe right yeah

9. 4:49

   yeah hey guys yeah no we started kind of we don't have much time we started getting into some of the uh developer experience um I'll give a quick recap of anyone who wasn't here last time uh so I just kind of was going into a little bit of where my Approach was I came come from a heavy web 2 background um I'm a software architect and engineer by trade worked in mostly uh platform based and API based type of software products for uh all different size

10. 5:20

    companies startups large uh large corporations things like that uh moved to uh crypto a few years back near specifically over a year ago now and really you know one of the things I was starting to highlight is that the transition you know near versus other chains moving from especially you know a heavy web 2 background has really been that the emphasis on usability for the end user

11. 5:49

    also really applies to the developer um I felt very comfortable with a lot of the concepts coming out of that of like what you know writing smart contracts yeah like rust has its own like uh you know learning curve I didn't know Russ before I didn't really use it but to put that aside of that learning curve the concepts that went into how near worked in everything else felt fairly uh fairly straightforward I didn't you know there are obviously Parts where I would get

12. 6:21

    stuck here and there but that felt more natural to me I didn't like I was going into something that was scary and completely unknown and so that was a really nice condition where with other chains um you know and it's gotten better over the years but you know it just you sometimes felt like this was this whole new technology that really seemed like uh you had to rethink everything where it's

13. 6:46

    not really true like it's you know it's a lot of the same programming Concepts we're just now doing it in different states and things like that uh one of the things that I'll say though that I really appreciated is that the near documentation is really good and it's gotten even better over time uh the one area I think so that for me could use some improvement is because everything is new and moving fast and as protocol changes is how do we better surface those protocol changes that are

14. 7:17

    going to affect current contracts and current work is being done because I could see where as we're moving you know things like the best example right now is like the um you know zero balance accounts like you know does that affect anything that I'm doing you know what do I have to go back and check you know as we start to look at those different things being able to surface those better for both people who have existing work and then then those

15. 7:42

    who are building new stuff of where that kind of comes into play um you know but again I think the tooling is strong um and I really I've always felt very comfortable recommending people to try building on here who are not necessarily crypto native because that transition especially with all of the JavaScript tools especially um you know of like making that transition but I know I think overall it's really been uh a pretty enjoyable

16. 8:12

    experience that is awesome to hear I guess I'll jump in because I'm actually pretty involved with uh uh facilitating the net process and I think the thing you're touching on directly relates to kind of you know basically new nips and how to communicate about them and I would love to hear from you or anyone on the call what would be your preferred way to learn about uh those changes like you know is it like through a newsletter that comes out is it

17. 8:46

    getting updates on the community on the telegram channel is it creating better information on how to subscribe to specific naps uh you know uh we right now we're trying a few different things but we haven't found like the one thing that uh that seems to hold and I'm just curious you know how you all find out about you know changes in maybe other uh technologies that you work in and how you what you would like to see when it comes to changes that are happening here

18. 9:14

    I mean I'll just you know so I think this is kind of something that's always difficult in software um you know uh most the time you know if you're working with an API of some sort right and basic kind of like rest with you know API maybe you subscribe to some kind of newsletter or something but like you still kind of run into those challenges of like am I up to date you know um you know there's things like right now obviously like in you know GitHub with like their dependency bot like they're kind of pinging you saying hey

19. 9:46

    you can update and things like that you should move up but it is a challenge that you know how do you get this information out there and I think that the disconnect that I do see or I think Improvement could really be is that you know some of this stuff is very technical and some of the stuff is really kind of in the weeds and maybe it's not even relevant for certain types of developers right like maybe I don't need to know every minute detail of a different change in an NEP or something

20. 10:16

    else with a protocol but you know I how do I also make that determination and so I don't necessarily know what the correct answer really is but I think as you start to we start to think about like how we continue to onboard developers of is it at least centralized which I think it is a little bit better than new NEP board on GitHub is a lot easier to go through and like see what

21. 10:41

    going on but it is a little bit hard to still kind of follow like I'm I'm a commenter on some of them and I find myself getting lost in where the conversation is and what is the actual status of this and those are the things where uh as we look at the ecosystem growing and bringing more people on board and more people getting involved because I think we could all agree like it's a lot of the same two dozen voices in a lot of these things too of you know how do we

22. 11:12

    start to open up that two larger Community for both informational only and then also to to then contribute so um I guess I'm probably posing more questions and answers but that's kind of where I see a potential hiccup in the future as we kind of grow that's really yeah go ahead okay thank you for your thoughts Joe I I think I just wanted to mention one one aspect that um uh you'd mentioned something about existing workflows existing contracts and so on yeah uh so one thing that uh

23. 11:53

    all protocol changes try to take into account is to always be backwards compatible so um there have been times when we when changes could not have been backwards compatible and that point a lot of effort went into reaching out to the specific con smart contract developers and so on to make sure that whichever ones were impacted that they knew what didn't practice and then they they were prepared for it and so on uh but moving

24. 12:25

    for but these are extremely rare occurrences where just no other solution is we cannot think of any other solution I guess yeah yeah but uh in general we expect we hope to always be backwards compatible so I think uh that is but having said that right I mean all of the feedback that you're raising is absolutely on point and totally uh very good for us to receive that if I if if I've added a new feature if if the protocol contains a new feature that makes it easier for you to do something that

25. 13:03

    was very complicated or very fragile for you to do before it'd be great for you to know about it so that you can improve your smart contract or if you if you if there's a new feature that lets you do something for half the fees then you're paying because of some complicated workflow you have to set up because that didn't exist before it will be great for you to learn about that and so on

26. 13:26

    and yes absolutely uh totally on point yeah yeah it's definitely a challenge I think I mean every chain is probably dealing with right and you know um again like I've I've done work you know on eth on Aptos on Solana and so I see some stuff and I I think near is better positioned in a lot of ways for some of that just of the way that you General usability is um but you know I think it's as the focus is on developer tools and

27. 14:00

    especially with boss and everything else the more that as a chain that we can kind of focus on those points of making that um as straightforward as possible you know because like I don't you know I don't work for the near Foundation or Pagoda but I get asked a ton of questions because of my role in the community like you know because of the podcast and the work software I work on I get questions so being able to make sure I can always point someone in the

28. 14:25

    right direction and be that liaison um is super helpful as well because it just makes everyone's life easier yeah thank you this is great uh feedback Joe and I think um just to I guess uh share a couple things also uh well first of all Michael I saw posted an example from the from rust which we've seen before the the newsletter and yeah I think that might be something that we can start experimenting with doing so I'll definitely bring that back to the team and see if we can um get started with that and follow up but in the

29. 14:57

    meantime I also wanted to show what does exist today in terms of us trying to communicate updates I don't know if we're doing it perfectly but at least just uh oh can I take over this screen share for a second absolutely I think I so I I'm curious if you all just uh curiosity maybe if people can like thumbs up or not are you all familiar with this view this kanban that we've created on on nips

30. 15:20

    have you has anyone seen this before yeah Okay cool so this is really meant to be sort of like a high level based on the net life cycle where things are at and you can actually filter it by different sort of uh working groups or or Focus areas so that is one place that you know if you want to know like what's this instead of seeing like one giant list that's unorganized like where

31. 15:45

    things are at uh what's coming up to voting Etc this is a good place to find out the other thing I wanted to mention is that uh Vlad and I who are currently net moderators work experimenting with actually adding like a master status to the the first comment on a nap uh we've been experiencing with this on some recent maps and basically what we're trying to do here is basically you know show what what are the things that need to happen to the network it needs to

32. 16:10

    have subject matter expert reviews it needs to go through the working group voting Etc so maybe there are other pieces of information that we could add to here to make the status you know uh easier to follow instead of having to go through all the discussions uh and then lastly the other thing that we introduced with the recent nep001 is a section at the bottom of each neck which is called decision context and this is really meant to help people who are just coming in and trying to catch up let's say on 300 comments understand

33. 16:43

    what happened that led to the decision of the neck and so this is meant to be like a summary of the benefits that were raised some of the concerns and the decision so these are some ways that we're trying to kind of address a little bit of what you're talking about Joe but I but I don't but I think we still have definitely a lot of room to to continue to improve yeah yeah that definitely helps uh you know

34. 17:07

    and I've been using this a little bit more now to go through that um but yeah it's just it's sometimes still too it's right like you're dealing with like two learning curves of like I'm learning about the protocol and then I'm learning about the workflow that everything is going in and then hopefully once you catch up to everything then it's kind of great going forward it's just that initial part of making sure people don't get too discouraged early on

35. 17:32

    that that is actually a perfect segue I feel like into one of the next topics that was on the list like how do you encourage uh people that are coming and helping them and I feel like you know Jacob I think I'm uh pointing to you for that topic then um yeah so I've I'm myself I'm working for Pagoda for more than a year now so I'm in the protocol team and obviously I had plenty of time to work on specific

36. 18:09

    technical problems within the code base and I'm getting quite familiar with it um and I've posted this link before so I assume most people were able to read it I will only give the very brief context here and then kind of hope to open a discussion um the problem I kind of want to solve is only Pagoda employees are currently really advancing the protocol itself so the community itself is large there are many different technical areas to work on

37. 18:41

    so I'm specifically talking about the protocol and that protocol itself I think we have like two naps that I was able to find that were um authored by people outside of pagoda and even those two are kind of um not independent of pagoda because at least to some degree there was collaboration going on and that's kind of uh expected for such a deeply technical challenging topic like the protocol right so I was just kind of thinking is

38. 19:16

    there a way for us to open up because what I would love to see my kind of mission here is that we have people from many after places like maybe they're working at a different company maybe they're students learning just people who are want to make a change in the protocol how could they do it let's say they are working on the smart contracts they really see that something isn't working as they want to they have an idea how they could improve

39. 19:41

    it on the protocol but like how where do you start that's really difficult to get in and the IDF on the kind of the open source spirit is well we have sulip we we're always there we have open ear people can come to us ask questions you can open GitHub issues we can have discussions there but I feel there's still something missing and one possible way could be maybe through some mentorship where

40. 20:10

    people can say I want to work on this but I like that type of information and then we as the community group The protocol community group who meets here we could try to have a process where we assign these uh potential contributors to more experienced people that will give them some shallow onboarding maybe that's the right word so it's not like a full-time job to Mentor someone else but to at least give some

41. 20:43

    brief introduction into how do you get started here Point them to documentation have a brief discussion on is their idea even viable how would it have to be done and then we can kind of slowly transition transition into this general idea of working in the open source community and just kind of working collaboratively but I feel like making this first step in I want to reduce the overhead of that and open it up in this way that's how I'm thinking about it

42. 21:14

    already talked a bunch with people inside Pagoda like we can't just promise anything yet but before I give more context on what our viewers of what we can even offer and whatnot I'm just curious to hear from people here like do you think that makes sense what would you be interested in would it be but from a mentor side or from a mentee site anyone please speak up raise your hand write in the chat

43. 21:51

    you know I I just think that the perfect uh in the perfect world we would expect Rising hands from you know really people from the outside of the of this yeah because you know people from here are kinda already um inside of this red so this work not sure whether you expect any ideas here oh I liked it I liked it okay oh no go ahead sorry yeah I just wanted to say that I like the uh I like the comment

44. 22:36

    from some persons in your discussion threat you know seems like this is a guy from uh from the outside how I say it if already scroll down here we can see you know we need more such replies maybe we need advertisements of this of this post so I think that person is even in the call right now just kind of comparing names um so these type of people who maybe not very familiar with the protocol itself I want them to join these discussions here

45. 23:13

    right and and contribute like be put as much part as they want to and then slowly get into a contribute role um but why not using those can you elaborate a bit more please uh why not try to use uh Dows for this I mean for contributions and votings like this so just a random question I mean there's probably room for exploring here I have to admit I haven't explored this option too much but I also don't quite see what specific problem a dial would solve right now

46. 24:01

    because the problem I want to solve is I want to make it easier for people from the outside to get into our world of Open Source contributing which is currently living on solip on GitHub kind of this General workspace and I want to get people in there and ideally in my opinion we would have a process that kind of already starts there unless we want to start somewhere else where we think there are more people

47. 24:32

    but at that would maybe help to make a process fair or decentralized but is that a specific problem we have here that we try to solve so if if you can elaborate a bit more why what the benefit of it that would be then I think I can understand better uh do we do we really have that problem is the point so I mean it was a general question like not really like a problem or something just just an idea and then

48. 25:07

    my uh share my experience with open sourcing is near Cork and uh actually the problem wasn't that I couldn't find a person who was responsible for this particle or is this because uh come on if you go to hackathon you have a lot of relationships with a team and you can just try to in the telegram it's not a problem the problem was that for example for an era PJs Library it's like 28 uh

49. 25:33

    pull requests opened right now and I try to I do I do pull requests and uh I wait for I I have an approval and then I wait for a immersion and then if the random guy comes to me and say okay so you can be approved because this part of code already was modified in is this PR as it was created like months ago and so maybe we should focus more on this part so maybe it will be easier to write a quote when we will understand like a

50. 26:07

    road map of immersion or stuff like that thank you okay so in your case the problem was getting uh the pr approved or just generally understanding you know it was already approved by the person but uh after we have like more and more pull requests uh some guys already like working on the same file and they change it by you know it's it's when it's open source and a lot of people who modify your codes uh uh it's really hard to keep track on

51. 26:42

    what's more important what's less and I think in your protocol it's some sense it wasn't resolved you know yeah absolutely and like the way we do it within our team within people that are working at Pagoda we have all these discussions in Zulu and when we have a PR that's not getting merged we ask like hey we have this PR what can we do about it and we try to have all the conversation in public there

52. 27:07

    and what I want to be able to do is like pull in contributors maybe they're already familiar with GitHub but they don't know specifically how we're using the pull requests flow and they don't know where to ask in sulip so combining all of this I think a mentor could help maybe hi good afternoon everyone can I speak yes please yeah my name is Faith okafomba I'm the founder of Sony G data Technologies I'm actually building

53. 27:40

    um a research um decentralization platform or I would say protocol on on near um I have actually started initially because um I got access to Nia Foundation or grants of of course is the grant is still ongoing because I haven't been able to complete my Milestone initially when I started this project I was um told I was I was going to I should be able to um deploy the project on Aurora because Aurora is already um is an evm compatible for near but

54. 28:20

    however when I actually progressed um when I wanted to go live I was told I have to build natively on air protocol and that actually brought a kind of set back to my project launch and bring the fact that rust um is is basically I would say from my own um experience is actually very new it's actually a language that a lot of people do not really have much of the skills as compared to solidity so

55. 28:53

    um I had to go looking for a rust developer I'm actually speaking from Africa from Nigeria though so finding a rust developer over here is really quite um difficult I went to the near the development um I mean developer telegram group asking for help for support I wasn't able to find support even the developers that I found inside the telegram group some of them were asking for pay of course um

56. 29:26

    you should one should be able to you know compensate someone's of skills but you know when you look for support you're asking for developers support from near protocol or the foundation it's very hard to find developers in there so you know just to buttress what you're doing I which I really appreciate calling for people to be able to Mentor them in knowing how to use the protocol I am I I think um you really have to you

57. 29:56

    know put more effort by doing most of those calls and calling people interested developers and finding ways to you know teach them the skills it shouldn't just be about doubt it's not everybody that knows how to use Dao and voting we have a lot of people who are interested in learning how to to you know to write programs to learn different uh programmable languages but they don't really know how to navigate through the ecosystem so by making calls like this and putting everybody body together it could be it may be in a way

58. 30:28

    of hackathon you know you train people even if it's uh maybe for a month you know you train them but a lot of people may not really know how to learn by themselves in the near University they need somebody that would be showing them the screen online and teach them you know take them from one point to the other to learn to really understand the near protocol itself and you know um

59. 30:54

    knowing how to integrate rust or deploying different programs I mean um projects in the um yeah that's it so it's it's it's um it's very very challenging we you need people that really learn how to um understand the rust language you know and be able to learn how to integrate different projects and deploy them on near that way you know it's really I'll bring about a lot of growth you know and

60. 31:31

    you know successes in um the near expansion and and it's going to really benefit the foundation and everybody yeah I don't know if with what I've said you know have made sense yeah that makes perfectly easy ways there would be ways to kind of have some solution for making this a little bit more easier for people to develop like on uh any rust chain and that's called like it's a little bit

61. 32:10

    let's say uh technical but it's like a simple abstraction yeah there are possibilities of having like let's say some typescript or or like python type of language or maybe even something similar like salinity which then creates with ASD abstraction syntax trees and uh transpilar methods then spits out like near or cousin wasn't or whatever rust code for example I saw some some people working on on these things and uh it's

62. 32:53

    like or for example I saw another project that was making like Json files that simply described this is my state these are my messages this is what uh my contract wants to do and from this Json file it was creating and bootstrapping like 90 of the smart contract kind of now okay things like this exist and uh should be explored more so yeah that's that's fine the typescript um I actually tried using the

63. 33:24

    typescripts but our studies in um beta test and um it's if I have to go on using the typescript I I'm going to have some security of challenges and I had to stop and as I said assembly script yeah the typescript that is um is it I think is more of JavaScript yeah but it is it's not um a full um program I would say you know for one to leverage so I was told if I continue with that I'm going to run into some security challenges so I have to leave

64. 34:04

    it I have to go looking for someone in um I think in Japan that would not be for for smart contracts right so rather for the students yeah I think we're getting quite a bit off topic here can I maybe so yeah thanks for raising all these points this is really valid rust developer but we are here specifically talking about the protocol and the client of the blockchain so smart contract developers are a completely different uh set of

65. 34:37

    developers we're targeting and we have different Community groups for that and we have daily office hours where smart contract developers can communicate and like ask questions and there is support for JavaScript VM inside near and everything but I I want to give area of our time because I have more topics after mine um sure go ahead it's just the first time that I like uh look at near and that's why I'm just asking you some

66. 35:09

    questions and giving feedback and we're really happy that that you engaged and asking what is the what is this what is this protocol I mean like in one two sentences what is this protocol so are you asking for a definition of protocol I'm using this call or this work group here okay so thank you the blockchain that is underlying of of the smart contracts execution that is uh the thing that actually produces the block so there's a consensus protocol

67. 35:47

    and validators run a node and the software that these valid edges are running is uh in the repository near core on GitHub and then there's a binary called nerdy and we're talking about the development of that specific binary making changes to the protocol means things like changing how Gas Works changing what types of transactions are even possible like meta transactions Was A New Concept um okay okay okay I understand so or like

68. 36:22

    changing how the webassembly runtime works so this is really like changing the operating system versus writing an app that is running on the operator it's like the the SDK or like the basis and then the modules and the how the governance works are staking yeah yeah uh sorry we can have maybe one more thought uh from uh a leap and then we should really move on to another topic and uh we can continue a discussion on

69. 36:55

    telegram so I'll uh please go ahead yeah yeah I wanted to continue the idea of uh Jacob right hello yes so uh I heard that Vlad fell off started like uh first feature on GitHub or kind of that so it's like a first feature for developers who want to engage into open source development for near core near pgs what is the status of this uh of this feature uh how it's going because I think your problem could be solved by involved like engage developers through things like

70. 37:30

    that so you should give developers like small things with kind of small payments right and people will engage more and more and by these more features they will engage in the product itself and then write to some core developer person to ask questions and learn more and more about but the question is about engagement not about how to get the information as I understand from my opinion thanks

71. 37:57

    yeah let's uh thank you thank you for uh about uh let's continue that on telegram I think so we can move on to the next topic um so the next topic is improvements to user onboarding uh I'm not sure if we have someone I don't remember who actually proposed this topic uh uh do you remember story or yeah let me let me look it up in one of our old Twitter threads I think it was actually somebody suggested it for last time and

72. 38:30

    we ended up yeah again but I guess yeah this we don't necessarily have to go into this example I guess like does does anybody have anything to say on that topic or any of the topics here uh which topic would people like to talk about maybe like how is this a BOS front end I think that I saw it it was like this kind of uh app builder or something right kind of visual uh thing how's it working like under the hood like

73. 39:15

    you call it operating system that's a good question uh do we have someone on the call who has a good understanding of how the boss works because it looks freaking awesome but yeah it does indeed yeah I mean uh it's not a protocol feature right so boss is completely built on top of the protocol so uh uh the people who generally work with the protocol like Jacob and I who don't work with boss on a regular basis so

74. 39:49

    it's uh I'm not sure how much we can help answer this question uh there's a workshop okay boss uh the other day that Ilya gave it was recorded let me see if I can find a link can if I can I'll drop it in the chat information um yeah so boss is basically a Gateway so think about it as um like an app server or whatever you have to um outside over there like um underscore list like one Gateway both is

75. 40:30

    another Gateway um the alpha nearest yet another one it happens that they use the same structure so like using the near social database but think about it that basically like you load the code from a blockchain uh and then like that Gateway is we'll put it up together with um with a frame or like you know the basic UI linked familiar additional indexers and everything else needed to make it

76. 41:01

    functional so like in this case for example yes that and you could be a an app engine right or an app server um also like providing the uh the front-end code right or adapt code and then various projects can also be included in the areas that the backend itself and and the HTTP server yes is basically the Gateway and um boss is one of the gateways thank you for that context Robert

77. 41:50

    um does that help people understand what the pause front end is supposed to be can I see that Michael has also found the the recording of the workshop that Elia did some time ago yeah test tooling is the absolute super important also for beginners and it's really really interesting to see there's also a component that Luis ferment base made on how to deploy your own Gateway which is like a click of the button and automatically like yeah configures that to resell so

78. 42:33

    there's that resource if you just look up on the featured like well in on and then the component you can just click that button and then you can have your own giveaway and you can play around with the front um thank you I think he's so can you repeat please for me he was cutting out suddenly yeah for me too yeah I think are there any other comments just on this topic or maybe not to the BOS but in general

79. 43:40

    regarding uh IBC and the connectivity there on the state status of this would be quite interesting to know how things are going there or if if there's something stuck that would enable this interoperability between these two ecosystems we do yeah so is there someone on the call to help give update on this it's inter blockchain communication protocol of the cosmos SDK or the tenement consensus and there's efforts to have this

80. 44:28

    connected to near substrate um it would be amazing I think they are pretty far I'm just curious what the blockers are at the moment uh if anyone has more context please raise your hand but I think one of the potential blockers here is one nap that's kind of hanging regarding block hashes access from within the smart contract and that is actually one of the motivations of my topic earlier I don't

81. 45:07

    want to go back but I can give some context here so we have a developers working on ideas to improve the protocol making changes to allow um intro blockchain communication and they realize they need some specific change to the protocol because we don't have the information they need and they have a proposal and the initial proposal just doesn't work the way they think it works because they don't have to understand yes that's the one I think this is one of the dependencies for

82. 45:40

    this to work 384 okay so here we have this problem where it um Agoda doesn't have an effort in actually working on this to mind the best of my knowledge but their Community wants it but the community sort of lacks the expertise to do it and we've had a couple of calls kind of ad hoc with people there we try to get the exposure I think we've we're in a good process of solving the problems but at some point

83. 46:14

    it kind of got stuck I'm not sure if there's any active work on it right now um maybe to kind of um bring back my topic from before maybe if you had a mentor helping them and push through and have a ongoing communication with them maybe it would have moved forward does that give some context to your question yeah it's really happening before before I saw like there was like some some cryptographic things to be solved

84. 46:46

    but I think that was already fixed like Ed 25519 like everyone has been that one has been merged nice interesting interesting yeah so there are yeah so there are is additional features needed in the protocol that are that need to be implemented and uh the community that started working on it but uh for various reasons the efforts have uh stopped and uh so if you or someone's interested in

85. 47:26

    picking it up that would be great thank you thank you um so we have about 10 minutes left um I'm wondering if this is if John is still on the call if uh if he wants to talk about the Moon based Tau uh John are you there I don't see him on the participants list anymore uh or maybe I think it was you Alexander who had proposed the improving project management for protocol development do

86. 48:12

    you want to talk a little bit about that then maybe didn't you bring up the project management Topic in the last one or oh it was like no I'm not afraid I think it was like two meetings ago okay yeah yeah hi do you have any more thoughts on it or do you want to describe what uh you were thinking of or from just real quick from what I remember my my question or call was about making more

87. 49:10

    transparent the overall project management I don't believe like I I feel it's still not transparent and posting on the GitHub doesn't mean making project management more transparent I mean you know Warden means I mean the proper Warden actually makes difference proper presentation makes difference and um all of that you know like a proper introducing the proper point of uh you know where can I look at the projects uh usually I start with near org or

88. 49:53

    somewhere maybe you know blog dots near work or something like you just imagine and the person from the outside even if I'm the developer with experience so yeah I just uh recalled to our discussion um a few weeks ago and I raised that question uh in the context of nap development again about medicine it was about many transactions which is quite delayed and I see other naps which are delayed I see that they

89. 50:31

    started in September of the last year and so on um then I remember that Bowen said that he might introduce a gap how's it going like grants diagram against diagram chart yeah yeah so yeah again charts something like that um yeah so that's that how we finish the discussion um I feel like a goal that I have you still have to make some proactive actions in that direction um as you have the resource yeah and it

90. 51:20

    probably would be helpful to understand overall development through different labs and the overall and by the way uh why I erased that question um just imagine you're the person from like the average person and you try to figure out where is the near in this world I mean what the status the size of the different um like pipe topics or different like you know like boss okay we have boss right so but

91. 52:02

    what what makes near um more so I want to make sure that cost of near Rises right I mean like near coin it should have higher price so why how near is improving how naps introduce the value in the protocol how it combines together so that was my my question like my interest and if anything helps to rise this awareness uh rise this confidence in the near protocol you know anything would be helpful

92. 52:56

    absolutely right yeah you know we would all love to see the coin price go up you know um and I but I mean the it's it's it's a it's an ecosystem that we're building there's lots of moving Parts there's lots of people who are involved and they all need to do their part to improve the ecosystem and a healthy strong ecosystem which has a lot of that attracts a lot of smart contract developers and interesting smart contracts and interesting applications this is

93. 53:35

    what these are the kind of things that can improve you know yeah but this is like a layer two and uh I mean you know layer one I mean all of these things are built on layer one and you know what what we can at layer one what we can make sure is that we're building the right thing right that we are putting our limited resources behind the features that are absolutely crucial uh and that we're not

94. 54:10

    uh you know what is the yeah yeah so so and just imagine like this is fully you you say me it's now and now like you mentioned I I open near.org and I see like your words like we're building crucial things off crucial features in the protocol and here are their uh the the these teachers one two three four and this is the uh roadmap we see the chart and haircut here is how you can join the development probably and here's Jacob he can help you maybe with mentorship and this is all on the

95. 54:56

    roadmap and maybe I don't know I feel it would be beneficial to the community that is that is very good feedback I agree with that yeah thanks does anybody have any more thoughts oh so we actually only have a couple of minutes left so I don't know if we should close out uh uh sorry any last minute uh thoughts or comments to share no I I think the only thing that comes to my mind is it seems like we had quite a few

96. 55:30

    uh new people to the to me and the protocol on this call which is I guess an assumption that we didn't consider before like we're kind of assuming that a lot of people are already very involved in the protocol so I think maybe just thinking about how to articulate like what this meeting is more clearly folks and also maybe building in if you're new here is a resource for you to check out yeah it was really great to hear all these new voices but I want to make sure that you

97. 55:55

    know we're finding the right balance between people that have specific things they want to talk about and people that are new and making sure that uh yeah we're we're just we're making it a good use of time for everyone so if you have ideas please let us know but I will follow up as I mentioned with the proposed monthly Cadence and then we can continue some of these conversations async So yeah thank you all so much and

98. 56:19

    it's it's so nice to see some familiar names and faces and really appreciate each and every one of you for all that you're doing too to make our ecosystem better so so thank you and thank you for hosting yeah thank you thank you everyone