NEAR Explorer Community Meeting (APRIL 2022)

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

1. 0:10

   welcome welcome everybody uh to the first dev console slash explorer webinar um my name is josh ford i work on the developer relations team here at near protocol uh joining me is josh quintal vlad froloff and sharif i you're gonna have to pronounce your last name because i'm uh very yeah sorry it's just it's just way too many letters but you guys can call me reese though cool cool um yeah you want to do quick quick introductions real quick josh quintel

2. 0:42

   yeah definitely um so yeah hey everyone i'm josh quintel i am the product manager of dev console and explorer uh which explorer was kind of a recent transition so you'll be seeing more of me around channels and on meetings like this and i will uh pass it to you vladimir yay i'm glad you also may have noticed my myself referenced as troll uh i i started explore project back in the days and i'm still here with you guys i'm happy to

3. 1:19

   uh to be here and follow you through all the history and how it will bring the future riff hey everybody thanks for joining my name is sharif al-shinawi i'm a leading design on the explorer product our design process has been internal for a little bit and now we're opening things up and we're really excited to involve the community since you are the users and so uh this is this is the first of many

4. 1:50

   uh hopefully events uh like this where we can gather your feedback and collaborate with you on the evolution of the explorer product yeah absolutely thanks everyone um yeah like we mentioned in the announcement um that i tweeted out and posted in our community channels it's going to be a monthly meeting we're going to talk about the progress made with devconsole and explorer uh we'll talk about the features that we're currently working on and then discuss uh kind of like the future of these tools and um yeah again

5. 2:20

   because the community is the ones that you guys are the ones that are actually using this tool it only makes sense that you should help shape the development process for that um so this is like a really good way for us to get um instant feedback from you um and have like live discussion as far as what you like what you think about the features that that we're rolling out and um yeah help help us uh in this process as we move forward um this month we're actually just going to be focusing on the explorer we're not

6. 2:45

   uh going to be going over dev console just yet um so next a month again this will be every first thursday of the month and um yeah next month we'll be talking more about dev console but today we'll just be going over explore um last month's uh if you guys were a part of the protocol meeting we had kind of an async question and answer format um but we'd also like to invite anybody

7. 3:08

   that wants to kind of come up on stage and ask question live absolutely um that's totally an option for you so um ask a question and like there's a question and answer portion at the bottom of your screen uh if you'd like to ask um a question and not um come up on stage and do it that's totally fine but yeah drop a message in the chat if later during the question and answer process portion of this if you'd like to come up

8. 3:32

   and ask a live question please feel free to do so and with that i think i'll pass it off to either josh or vlad i'm not sure who's going to be presenting um but yeah take it away i think i will take it from here uh josh will definitely need it on the dev console and all the subsequent uh calls for explorer but since i've been involved with the whole history of explorer uh i'm i think this first meeting i will take it uh on me and then updates

9. 4:05

   will be much easier to conduct from josh's side uh so let me uh share the screen just to so we are not you know staring at that empty screen or like just looking at myself um i'd like to uh say that explorer went through a lot of iterations and it's still an ongoing project uh we started with a very small uh tool that could only follow the very latest changes on the network and as of today we can have we have the whole history of

10. 4:44

    the blockchain sitting specifically for explorer needs out there and explore ui lets you to explore whatever you find interesting about the changes history um or basically the the sky's the limit basically anything you want you can have on the network so anything that has happened uh should be uh navigateable uh through explorer and uh just to remind you here's how this ui looks like today

11. 5:24

    it's quite uh quite clean and nice but i still still want to improve and may and communicate even more and more to this uh referral provider about the future uh uh in in a couple of minutes uh i want us to to work through what we currently have and what they basically um the focus uh of our work uh lays in so this is landing page you for sure have seen it um the changes here yet to uh to be visible in the future as you

12. 6:10

    can see it's uh quite um quite interactive and immediately updates all the values but what i we want to focus on right as of today is on the pages that you usually want to explore uh rather than just eyeballing the main page usually go to the account page and uh start digging into the history of your account or somebody else's account um and currently the what we uh did uh was all um around very raw

13. 6:56

    representation of what's in in the network and the evolution of explorer ui led us as to this quite overloaded ui uh with a lot of numbers uh in here we experimented with adding even more of those we actually want to add more data and more and make it more readable and to to do so um we started to explore the space another poor part of this page is this list of transactions and

14. 7:36

    you may actually notice when you open some somebody's eldest accounts they are actually not that easy to understand my account is as a regular users is not that complicated but if you go to uh foundation.here you can start noticing that it's uh it's not actually helping you uh much because it just says that this the only thing that is happening on this account is confirming something where foundations send in a transaction to foundation confirming something uh not very helpful

15. 8:17

    uh and this uh what uh will present you in just a bit of like what what what's in there um and then if you go to some transaction page you can also um see it's bloated with all sorts of metrics that are super useful but at the same time not very readable so uh from here i want uh to invite riff to jump in and walk us through about the future um yeah rip sure um hey josh is saying it's disabled um let me try it again yeah maybe there's a setting you can switch

16. 9:06

    on i just promoted you to co-host congratulations you should be able to you should be able to mark to share now there you go this is a dream okay uh we can all see the screen yep right fantastic so what i want to do before anything is talk about how we're all going to collaborate together um we're using figma i'm not sure if everybody has a figma account but what we're after this meeting and you know uh we're we're going to be sharing this link out we want people to give us

17. 9:47

    inline comments and feedback on these screens in specific locations so the only thing that i'm that that i'm asking of you is to please create a free figma account if you don't have one we really value your feedback and want you to engage uh on this next phase of our design process so within the figma file that we're going to share out after the meeting this will always be there some instructions on on how to leave the

18. 10:19

    feedback so today we're going to look at our account details page uh and then we're going to go all the way through to transactions and talk about a few concepts and things on the horizon uh that we're thinking about before we start uh and when when you are looking at this later we wanted to sort of annotate the experience a little bit to remind ourselves to remind you guys of some of the the

19. 10:49

    elements of the explorer the new evolution of it um so i'm not going to go through uh every single detail but i do want to talk about the structure and the reasoning behind things so as you saw with trolls uh with the the presentation of where we are today we took a step back and we tried to build principles before touching anything in terms of design and those principles were hierarchy clarity brevity

20. 11:22

    and some guidance along the way so we want everyone no matter what level user they are to be able to explore to be able to understand where they are what they're able to do and what's going on so at the very top here we're not going to be talking too much about navigation today so let's leave those comments until the next meeting uh where we'll have a much more uh focused uh effort on navigation let's do everything from from the header down

21. 11:55

    so we we start with some identicons and the reason that we're proposing this is to break some of the text heaviness of explore and add some visual uh language to kind of separate and make things easier to scan up here is basically the high level uh metadata for that user like we said we want to create some hierarchy so things like balance amount stink if there is any state tokens

22. 12:25

    the number of transactions and then i'll link out to the wallet so a lot of this stuff is available on explorer we're just redesigning it to add again pointing back to that principle of hierarchy and clarity you'll see a label here and that will differentiate so that you can understand whether this is a user a app or a down right coming down to the list we're using a tabbed pattern

23. 12:54

    uh for again pointing back to some clarity we want uh and hierarchy we want simple ways to organize all this information so some of the ideas that uh are on the horizon are being able to display assets and access keys and lock-ups associated with the contract the activity is literally every event that happens for that account and i'll go through uh the the table here and we can take a look at

24. 13:26

    some of the elements that were that we're bringing forward so we are prioritizing the people first the the accounts uh that are uh the accounts for each transaction so from and two we are using a new labeling system for transaction type so that again we have an easy way to scan and understand what's happening we're bringing in some iconography for tokens to understand what tokens have been transacted we're

25. 14:02

    using color to indicate balance change and we've we're using a very short abbreviated version of the idea and this has sort of been a point of contention our first initial concept we removed them we didn't see a reason for them to be there we got some feedback that from some people and some use cases where they needed those things so again these these are some of the things that we'd love your feedback on and not really so much i like this or i

26. 14:34

    don't like this but the reasoning behind it and maybe a use case indicating why you feel the way you do this stuff will really help us understand some user stories and and maybe some journeys that we haven't uh uh we haven't worked into here another thing that we're doing that a lot of explorers aren't doing is where and this is sort of the focus principle is we're not making everything on this screen clickable um we believe at least our assumption our hypothesis is that people are here

27. 15:06

    to navigate the explorer itself and not so much bounce around something to think so as you hover over these this is one element that will allow you to click anywhere into a transaction instead of uh clicking on separate accounts or other things of that nature right down here since we do have tons of batch transactions and they they can range from two to a hundred that really blows up this list it makes it sort of unusable right so what we're

28. 15:40

    trying to do here again with that brevity principle is condense things but also allow people to understand what's what's uh uh how many trends or events within that transaction there are and once you click into them you will obviously see all of those things all right now because of the velocity of the network it's really hard to add pagination so simple load more is what we're uh our approach is for that so again all of this was done so that

29. 16:12

    you can come back here if you forget any of the things that i've mentioned um they're they're they're annotated here for for you to do a little refresh a very small sort of concept that we're uh conceptualizing here is the auto search the auto suggests the type ahead uh we want people to uh be able to search quickly find uh where where where who they're trying to go to um and that sort of points back to the guidance principle

30. 16:46

    so these things you'll see that little people icon which will indicate accounts uh you'll see other icons for other types of accounts as well so that you have a visual organization okay so we mentioned we went through this stuff when i click into a transaction now we're going to go into our transaction detail um i'm sorry first we're going to go into a new feature that we're exploring which is filtering

31. 17:19

    we see our assumption is that we see a need especially when you're at an account with thousands of transactions and you're looking for specific things we want where our hypothesis is that users may need to filter uh by the accounts from and two transaction types the amounts range of of near tokens and the date range as well again this is a really great place for you guys to comment and tell us either

32. 17:50

    why or why not you would use a feature like this that's really valuable to us and you can also add things that maybe we haven't uh included here different types of filters you would love to see and again please give us the why the why is the most important thing we're looking for here so you can filter this list find what i'm looking for and now when we're clicking into the transaction detail we're using the same sort of header bar pattern to add that hierarchy so all the high level

33. 18:23

    uh details um labels for the state of that transaction which there could be many um the high level up here of this of this data the fees attached the t gas these are up for um this is these these things are are are up to you guys right we want to understand what metadata is most important to you right we have our assumptions and we'd like to hear from you as to what you'd like to see up there what's helpful and

34. 18:53

    what's useful so down here we're basically bringing the pieces of that that transaction that you saw on the list making them bigger and adding some hierarchy there and then we're using that same tabbed pattern to organize the information to see the arguments the result the logs the balance change once we go to and these names again the naming conventions we've heard a lot from people about these things sound confusing or that we need to better name things again this is a place and a time

35. 19:30

    for you to suggest such names uh naming conventions okay so once we go in to this inspect tab now we see the rest of this data of that transaction there are things that will be clickable here and because i i mentioned before that on the actual list of transactions we don't we're not allowing uh for people to click on accounts and other things but once you get into the transaction detail all of those things are equippable

36. 20:02

    okay now we're moving on to what what a batch would look like right um so once we get these really complex transactions we're using an expansion pattern so that we don't have as we have today this long list of things now you might say i'm used to that and i like that we'd like to hear why or why not and whether this organization of the information is actually much more helpful or useful to you

37. 20:35

    use cases are really important to us so if you're a developer with specific use case and reasoning behind your comment please please please include that that's the most valuable thing for us other ideas as i had mentioned before are what would it look like if i could go and check out the assets or the access keys of a specific account and so these are things that we're working on they aren't fully fleshed out and so your comments again are very

38. 21:07

    valuable in these uh in these last couple screens as well as as we haven't focused uh as much as we have on the screens that you previously saw so that's that that's the uh these are the screens that we wanted to present to you guys and again i want to sort of zoom out here and go back and remind people um it's really easy you don't have a figma account once we share this link the first thing you'll see up top

39. 21:38

    is a bar that says sign up right um you have the choice whether to sign up or not if you want to engage and leave comments you need a figma account if you just want to look around you don't so thank you for listening thank you for showing up and uh thank you in advance for all the comments and help uh and use cases that you guys are about to give us that's all for me sharif do you have a link to the figma

40. 22:10

    that we could drop in the chat um we could share with everyone so they could uh sign up sign up for it that'd be awesome absolutely i'll do that right now all right just saw a comment uh it says we don't get to see other people's chance or answers uh actually it's open everyone um the check should be open uh to everyone i haven't actually gotten any questions in the question portion um yet um does that um just to check in

41. 22:42

    with troll and um sharif is does that conclude um the the presentation part are we ready to open it up for any questions okay cool cool cool yeah so yeah anybody that um that uh would like to ah okay i see i see a question uh that popped up real quick but yeah so what we'll do now is we will take any kind of questions or um comments that you guys have you can do it either in the chat um the q a portion um it should be a little tool at the bottom of the zoom window or

42. 23:16

    if you'd like to join uh and yeah just ask a question with your voice come up on stage and do that absolutely it can do that so just drop a message in chat that you'd like to join and i'll add you i'll add you in the chat um the first question um is on explorer like ethereum we can see whether particular address is eoa account or contract account and from there if it is a contract account we can see the complete code of the contract can we expect the statement near explorer and upcoming features

43. 23:48

    probably let me take this question then um there are a few actually questions in this single one uh first uh on the ui on the figma you will already see that each account is tagged with a specific category uh right now we went with a simple one um distinction between a user and the account with the contract on it so basically you will see either user or contract label um but what's uh indeed more important is to see the source code of the contract and

44. 24:28

    that's going to be a separate tab on the on that page account details page where we will pull in all the available information about the contracts i just want to bring the attention that by design near allows to submit any bottom executable as a contract meaning that we cannot really uh enforce and like easily show the end users what the source code was because it's compiled binary

45. 25:01

    but we are looking to to have a facility to integrate it with dev console and potentially other services uh just in decentralized way to uh that will allow you to sign your applications and provide metadata through some ui and then explorer will just pull it in the same way explore currently posing information about the validators validating nodes uh on the validation notes page you can

46. 25:34

    see there is a metadata with a home page description and a few other and uh and like country uh all of them are pulled from on chain from the contracts uh from a contract called uh named here if i don't remember uh don't um uh misremember it um so yeah that's uh that's definitely on our rather um though there is no um timeline uh yet for that feature but yeah we'll definitely uh prioritize it once we finish with the

47. 26:13

    first steps that we presented today thanks for a question yeah i think the little follow-up was you can only see the contract if the owner uh has submitted it and that's actually i think we'll touch on that a little bit um you can see the compiled wasm that's there but it's kind of hard to parse exactly what the contract code is so you can't really view it and then i notice that you mentioned stuff like stat stack gallery um and you think that um they're able to see those methods based on transactions made

48. 26:44

    to the contract it's actually not um correct the individual by jacob on the education team is the one behind stat stock gallery and he created a tool it's like a near contract parser that allows you to actually look at the wasm and it can show the methods right now that you can call on that contract so it's actually not um from the indexer but it's actually looking at the wasm

49. 27:08

    and seeing oh these are the the methods that you can call uh on that individual contract but yeah definitely um uh yeah if you want to ping me on discord um i'm josh pipener um i can forward you that repo and you can take a look at the source code and see how he did that uh yeah it's really really really cool tool for sure yeah if if we will dive into it a little bit more we'll actually

50. 27:31

    notice that wasm doesn't have a way to expose the data like all in in all details we can only learn about the method names we can't even learn about the arguments that it expects so therefore rust tooling team uh who who are working on nearest dkrs uh are building the standard which will allow uh us and other explorers uh other tooling uh to extract information about the methods

51. 28:05

    and arguments uh from the wasm file uh just by near sdkrs providing that facility by compiling that info into the binary itself uh so they yeah that would definitely unblock us and many other projects out there yeah and uh just to have a shameless plug on that so next week we're having the protocol meeting on thursday and the following week we'll be having the tooling team uh on on board so yeah if you want to talk about rus sdk

52. 28:38

    assembly script sdk like anything in our tooling portion the third thursday of the month we're going to be having a public protocol meeting and basically yeah every week of the month we're going to have this on thursdays where you're going to be talking to a different team um and asking any kind of questions and participating in the development process of the entire uh protocol so yeah just want to want to plug that out and i'll be sending out

53. 29:02

    watch discord um for for perfect timing in our tweets yeah perfect timing yeah cool cool um the next uh question i see is um can i ask how the indexer is used in the explorer sure yeah absolutely i i will take this one as well uh so in initially so let's start from a bit of a high level overview uh starting from the blockchain itself blockchain is a piece of technology that only cares

54. 29:34

    about how to reach the consensus about the changes and how to move forward it doesn't um optimize for querying the data and optimize for um like use from the external uh world it only cares about how to not get stuck and how to make sure there is no centralization point and in order to serve explorer needs we need some tool that would be able to follow what's happening on the network

55. 30:09

    and put it into a storage that is easily it can be easily queried and you know in the ways that explore needs so indexer is is it is this tool that um follows network block by block and stores it into right now into a postgres database so currently we have a positive database uh that sits in between from the like in between the blockchain and the explorer ui and uh serves all sorts of types of

56. 30:44

    requests and you can find them on in excel for explorer project uh there's even an um public shared access to that positive database read-only obviously where you can um yeah play with the data as well if you need and on the explorer side what we do we just query and make sql queries um to that storage to podcast instance and if we need information about transactions and stuff like that like give me 10 recent transactions by this account id

57. 31:22

    blockchain does not have that facility to serve such requests to you but when you store it in a regular database you can do it and that's this is exactly what indexer does for us so as you may have uh if you've been following um near for a bit you may have noticed i posted sometimes um announcements like there is a downtime of explore due to indexer issues and that actually means that indexer got stuck for some for one

58. 31:57

    reason or another and it could not put the data into the database and therefore explorer wouldn't be able to display that latest data while the the whole consistency and availability is there it just lags behind a bit but then it catches up and everything is all good hope does it answer your question i think so uh it was mario that i asked that question mario please uh ask any

59. 32:28

    follow-up questions if you do um an individual's asking if you could provide a link to the postgres database what are we talking about if you drop that in the chat that'd be awesome and yeah mario let me know or let us know if you uh that answered your question or if you have any follow-ups uh and well shameless plug here again uh the indexer is a separate team which will have a separate

60. 33:01

    call later this month probably we'll see and it actually as i mentioned it it follows the network with the latest data and uh you can do whatever you want so there is index of framework uh that allows you to implement your own indexer and do whatever you want with those blocks you can put them on postgres you can put them on bigquery you can put it you can ignore 99 of the data and put only certain items and

61. 33:35

    call webhooks originally we had indexer framework tightly coupled sorry with near core with the blockchain itself um the benefit is that it follows it it's part of the peer-to-peer network the same blockchain network as all the other nodes the downside that it needs to sync with the latest data on the network it needs to store uh five recent epochs in year which means like two and

62. 34:06

    a half days of data and it requires you to to have a half a terabyte uh storage ssd drive to to have it running and recently we actually launched a new uh project called near lake uh nearly a system uh which significantly loads down lowers down the requirements and allows you to start in just a matter of seconds actually with your own indexer uh just because the data is stored on s3 as intermediate uh storage and once you build your indexer you can read from s3 immediately

63. 34:47

    get the stream of blocks uh right from from it and yeah i will share the link to the announcement post post on god.near.org forum where you will find all the like tutorial overview intro and from there we can start the conversation i don't want to take any more time from this call today sorry it already took a long time yeah no thanks for that plug yeah um the indexer data rpc all that conversations will

64. 35:19

    happen at the last thursday of the month uh so yeah first thursday explorer second thursday protocol third thursday tooling and then the last one will be indexer and data and rpc endpoints um mario had a follow-up um and was just asking uh i also meant if indexer exposes an api so queries are done to this api and the indexer node is an rpc node can we also access it from some dap i think i already touched on it basically indexer itself

65. 35:53

    indeed is a near coordinate you can have the same rpc communication with it but it doesn't provide any extra benefits whatsoever the only reason indexers leaves is that you can implement the logic which will put which will react to the incoming blocks and do something with them uh indexer for explorer so there is index of framework which allows you to build such indexers and there are plenty of them actually mean base build their own um

66. 36:25

    fire and blend their own and i know like a dozen of those already i just don't remember all the names from top i had um and um and after you store those events in some storage you can do whatever you want with indexer for explorer implementation uh we put the data into postgres and then you can create the podgus database i do not recommend to be honest to run the your own indexer for explorer foundation unless you know what you're doing because it will require you to run

67. 37:02

    a few nodes it will require you to have postgres instance so and each each node will require archival node not a regular one archival mode is over seven terabyte data right now and then you will need a storage for postgre database which is now roughly 1.5 terabyte uh rarely you actually need to do that more more mostly you will you want to react to your own few events and near lake is what i recommend you to explore

68. 37:33

    and use cool awesome thanks for all let's move on um next question would be how are sub-accounts shown in the ui uh and a second question would be how would the ui show deployed smart contract code and callable functions um so yeah it's a little bit of a two-part question yeah let's mis let me start from the first one then uh how super sub accounts shown in this ui so each each account is uh indiv like independent from all the rest of the accounts even if it's a sub

69. 38:13

    account the only relation they had initially is that their parents account created the sub account after it is created there is no um relation left except the naming so we actually didn't explore that part of uh providing some specific handling for sub accounts just like like near is is an account yeah if you haven't noticed that near is just a regular account with the contract deployed to it it's a link drop um

70. 38:51

    contract which allows you to um which which can create new accounts underneath so whenever when i went to create for all.near i actually used wallet which uh submitted a transaction in in on my behalf subsidizing the cost of creation of an account um to the near contract uh with request to create fraud.near with the public key that was provided by from my browser and uh therefore i i don't think there is a need to to treat all the near

71. 39:34

    asterisk uh dot near accounts as something you you want to see on near account um but maybe there are some use cases where some accounts could could be a reasonable thing to list um let us know about your use case and we'll definitely explore maybe we miss some of the use cases there awesome thanks and yeah the second part i think we touched on a little bit more but uh how we're going to deploy smart contract code and callable functions

72. 40:08

    um indeed there will be a tab on the account it heals page where we will try to collect all the valuable um information about the contracts so currently as you may have seen on the current version of the explorer um it only has like four um data points uh about the contract if it's deployed whether it's when was it deployed with which transaction it was deployed or like recently updated and whether it's locked or not locked meaning uh there are no access keys on the account

73. 40:50

    left full access keys on the account left which means there is no way to upgrade the service code unless the contract itself implements this uh logic of self upgrade which uh well well we cannot tell when it's uh with the binary uh from the bottom binary itself um but this again uh getting a little bit back to the conversation we had about the vason files and like viewing the code of the deployed contract um given that you

74. 41:36

    only observe the binary the compiled binary on chain for the contract um and you cannot revert the process of compilation back to the source code the thing that you can do is if somebody provides you with a link to the source code and you can compile it you can compare the checksum of the compiled result with the checksum of the uh code that is on chain and if it matches it means that basically the source code is equivalent to

75. 42:16

    the contract that is deployed on chain and this is a facility we want to um explore and i know that there are some projects out there who may uh um try to solve this um like outside of explorer uh first because we don't want to provide uh like all the like extensions out there uh we want to be decentralized and ideally we want to rely on some other sources which will be able to compile source code and compare the result with the one that is on chain for you automatically

76. 42:57

    so we'll see how that goes um and uh yeah i hope that that answers the question awesome thanks vlad um that's all the questions that we had that was in the q a portion are queued up so far so please feel free to drop any more if you have them but i do have uh looks like guillermo's joined did you have a question hive no no okay oh it looks like he doesn't have any questions cool um yeah and yeah if anyone else has any

77. 43:38

    other questions feel free to drop them in the chat or or the q a section otherwise potentially wrap it up a little bit earlier yeah well it was all fruitful conversations and i i think all the questions were super in intense and like in depth uh thanks for asking them i i think whoever will later check out this video we'll also find them very insightful thanks a lot absolutely thanks everyone and again

78. 44:18

    we'll do this every month um first thursday of the month be talking uh next month we'll be focusing more on dev council but definitely uh talk a little bit more about explorer feedback as well and kind of be a shared meeting uh and again yeah every thursday we're gonna be having these community feedback sessions and meetings uh next week thursday will be the protocol so if you have anything um for the core team bowen's team feel free to jump on and chat with us and

79. 44:43

    again third thursday is the tooling and last one is going to be indexer and database stuff so yeah feel free to uh um yeah feel free to join and uh yeah we'll see in the future thanks everybody appreciate it thanks a lot yeah thanks everyone just to answer uh june yes um the links for the meetings are in discord announcements um i i'm announcing them in the telegram channels um and uh yeah i'm working on a landing page uh on

80. 45:18

    near.org so that way they can all be listed there as well so yeah keep keep an eye out and discord um josh there is one open question in q a if you want to take it oh not related to denier but want to hear josh talking about pagoda something seems very interesting i'll assume this is me josh since i have the pagoda shirt on yeah let me uh i hope uh i didn't leave yet okay cool guess you're still here awesome yes so pagoda

81. 45:48

    um actually is a rebrand of near inc so uh everything we've been talking about on here um explore dev console or tooling uh things built on top of near um actually are now going to be not necessarily branded pagoda but the company that develops those is now pagoda and so what will we mention this at the top of the meeting but you might not have been here um this is actually going to be a combined

82. 46:14

    dev console and explorer meeting and so in the future actually the very next meeting i will be talking more about what exactly that is but if you go to pagoda.com you can check it out it's a tool that manages the operational side of your dap so once you've got it deployed you know you want to see some metrics you want to see a combined view focused view of your contracts things of that nature alerts and triggers i will be talking about next

83. 46:39

    month so yes that and thank you vlad for posting the link in there um there's also uh you know what before we go i can post you a link to the presentation i gave at east denver uh about it as well which is a nice like succinct intro uh to it and there is another question what's the difference between your ink and near foundation that probably yeah worse clarifying josh okay that was great i thought i heard someone else speak yes um and you guys correct me if i'm wrong here but the difference between near ink and near

84. 47:18

    foundation is that um much like a pattern you've probably seen elsewhere in the blockchain space like near foundation is a non-profit that you know handles the community is meant to like advance the protocol uh things like that uh actually uh josh you can correct me if i'm wrong here near foundation handles like grants as well yeah that's correct okay yep whereas like near inc pagoda we are

85. 47:44

    uh we do kind of two main things we build tools and services on top of near protocol and we also are one of the main contributors to the protocol itself any follow-up questions we'll give it one more okay cool she says thanks or heath says thanks he or she um cool i think that's it i think i think we did it i think we did our first our first explorer dev console meeting yeah again feel free to drop us any questions in chat and yeah

86. 48:24

    if we didn't answer any questions that you have today um shameless plug for office hours deborah we have them every single day um if you go to office hours yeah i'll drop it in chat near.org forward slash office hours we do twice a day one in europe and one in the americas time zone uh we'll hang out for an hour talk about anything you want to talk about development related feel free to jump in one of those on

87. 48:49

    daily cadence and then we also have uh weekly chinese and vietnamese and ukrainian and russian speaking meetings as well so feel free to join any one of those chats and head over to near.workforce office hours to find out more about how you can get involved but yeah anything else i think i think we're good to go think thanks thanks everyone appreciate it thanks for joining bye-bye next time bye-bye yeah thanks everyone