NEAR Data Platform Community, 30 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Data Platform Community Meeting (June '22)

Description

This week we discuss Enhanced API Suit (all kinds of balances accessed via simple API endpoint), Alerts on your transactions, events, function calls, balance changes, RPC Stats Page, Contract Analytics, and Product Landscape on data side at NEAR.

Take the survey mentioned in this meeting:
👉 https://bit.ly/3OVqTC0

Engage with us on how we shape our product offerings:
👉 https://miro.com/app/board/uXjVOpfszDI=/?share_link_id=576919844819

Information mentioned:
👉 Enhanced API repo: https://github.com/near/near-enhanced-api-server

RPC Stats Page Wireframe:
👉 https://www.figma.com/community/file/1124105967655856167

On-chain Contract Analytics:
👉 https://console.pagoda.co/project-analytics

Join our next Data Platform Community Call:
👉 https://near.ai/data-platform-meetings

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

A

Cool um welcome everyone to another community meeting this month with data platform. uh We are going to be talking about enhanced apis alerts, chain, analytics near lake and our pc as a service uh give updates, and then I think we have some more agendas. I kind of got a packed uh hour today, so uh yeah without any further ado, I think uh tiffany, are you gonna be sharing some slides? Are you gonna be leading this awesome cool? uh Thank you very much and yeah.

A

If you have any questions, please post them in the chat below or in the q and a section uh at the bottom of your screen, um but yeah go go ahead. uh Take it away, take it away, tiffany and, as you can know, it's it's hat day today at near so okay.

B

Cool awesome, uh so for this week um we have a lot packed uh we'll start with our very new product, enhanced api suites and we're looking to have a much more more powerful offering um in this product too- and um this is, you know- we're very excited about this- so really looking forward to release the public and get as much feedback as we can and help. All of you guys easy as easy as possible in terms of getting the data. That's the first set item. Second item will be alerts.

B

Finally, alerts is going to be almost live and show it to public, but uh this week after um you know long and very, very awesome work from our team, uh we're ready to demo it to the public and really let you guys know and see what we're offering you guys and get pumped and get excited and um yeah. So that's the second item. Third item: we have our pc stats page um ready, uh it's not not ready yet, but the wireframe almost wireframe is ready.

B

So we want to show it and let you guys know that we're preparing for it um we're very likely to erase it out roll it out, and so for the first time you will be able to get your rpc data and you understand your rpc usage.

B

So looking forward to that and the next one is analytics feature on console, I'm not sure if you guys logged in already into console or starting live, but just taking this opportunity to show you that we have this awesome feature available for you to get your contracts, data analytics everything happen with your contract and can help you get a lot of helpful information like your user information, and uh hopefully they can give you better ways to make your decisions in in your operations.

B

And, last but not least, we have leg session on console. So for anyone who are not aware of lake here's a great entry point for you and console to know what it is to use the tool um and to understand how it can benefit you.

B

So without further ado, I'll move it to our first item in his apis.

C

Yeah, so speaking about your enhanced cpi, we definitely received a lot of questions like why? Should it actually be so complicated to you account, balances or ft nft lists um history of that, and why should I use indexer or rpc, and when should you use it? So there is definitely no need to hit your head around and instead you can just use the enhanced api as the one offering so and I'd like to pass it to orla, to talk about the specifics and hopefully we'll have some live demo.

D

Yeah, hey uh yeah, so uh I want to start from uh memology. So, as you all know, uh we have bogdan in the team, uh our absolute expert in entomology and I'm always trying to to learn something to be as great as him yeah. So uh as I knew uh this week, this meme is known only on post-soviet countries, so uh this is the guy who wait for something and uh all of you, I I hope so you were waiting for our enhanced uh api yeah. So let's go uh next slide. Please.

D

Yeah, so I want to say you asked we delivered, but we haven't delivered it yet, uh let's go further yeah. So what is it? So? This is a rest api. uh We decided uh to to concentrate at first uh on the balance side. uh We can go further.

D

Actually I can.

D

Don't worry I I will just continue. Do that uh so yeah we have many different endpoints. uh Most of them uh covered some information about the balances, so we decided to start from native balance, fts, maybe multi-tokens. We are thinking about that. Of course. Some information about nfts, so hopefully next slide random wallet, developer or the developer of application should be really happy about that next slide.

D

So I really hope you will be happy about this yeah. So uh we have, uh we will send you a link to our repository, so it's open source and you can uh create any issues you want. Please share any feedback with with us and I want to share some technical details with you. So we use open api specifications so what it means to you. So you will have all the perks from uh from our implementation that you actually could. So you have all all the beautiful documentation.

D

You have typed responses. uh You have anything you want from from the rest api exactly.

D

um Yeah about technical details, uh so we are using our indexer database. uh I hope you are familiar with that. We also use rpc to to get all the data that we want to serve, combine it and serve in the best way that we could uh yeah. uh We will add some new. uh I don't know it's fast.

D

um We will add some new tables to to our database to serve all the data we want. uh So, as you already seen version one is all about balances and we have some things that we want to support later.

D

We will ask you about that: let's go further yeah, let's try our live demo, um but second, it's too hard.

D

This is only only one big green button and I can't find it yeah. um So let's go through some of the endpoints just to test it and see how it goes. So, as you can see uh yeah, we have many different information here. We can send the request from for a random user um yeah, it's so it uh he or she. So they have uh some uh balance, some native balance. Also they have some uh tokens. So this is so. This is ft contract uh with the metadata and so on and so forth.

D

Yeah. We also can uh try to ask so, um for example, about history, uh so for that we need to copy the contract name.

D

Let's try to take it here.

D

Let's try to find some history cool, so yeah. We have some information about deltas and actions that were done with this account by this fungible token contract uh cool. We also can ask for some nft information.

D

uh We can find yeah, so this guy uh has uh one nft uh at boras, so yeah. So this is a heavy underdevelopment and we are still working on on the types on the pagination stuff on the all the structures, but you can have like a good overview of what we are doing and if you have any thoughts about that, please share um yeah, and so this is all from my side.

D

Yeah, so let me just.

C

Bring a little bit uh more um highlight on on the on this api. So, as I mentioned, we actually follow the open api spec, and this is why you can actually have the nice playground and we'll integrate it even further and extend it with more examples in the same ui.

C

You can also have the snippets of the code uh that you can just copy paste and run uh in a number of languages out there, uh and also in curl, hdpi, python and and stuff yeah thanks olaf for sharing the link in the chat uh and you um um yeah and one one crucial thing is this:.

B

C

Actually, as simple as as it looks like, and it should be it's this way, so I hope uh everybody really love it and let us know what's I, what are you uh hoping for the next steps here? uh Will we launch the poll now or will we launch it later.

B

B

Sorry, uh I think we can. We have questions that are about everything, so maybe a little bit later, yeah.

C

Yeah then, without further ado, let's jump on to the alerts and the dev console uh integration of alerts.

E

Yeah, it's my turn: hey everyone uh I'll start with the trick. Oh much better thanks, uh I'm gonna share my screen and try to perform some demo of alerts.

E

I hope you can see it well. At least I can see it well so we're looking at the alerts module in the dev console and we're gonna gonna create a new alert. uh I wanna mention that I have connected a telegram bot uh as like a destination option to get the notification through.

E

uh So in the nice fancy form, we can put the account I'm working with the testnet, but main net is also available and which is a condition currently we're working on all like to cover all of these possible conditions and extended with the more but currently fully functioning is any successful transaction related to the account or contract address we put in in the first point, uh or only failed transaction.

E

We will go with the successful ones, I'm enabling the telegram destination, and just I want to show you that uh email sms uh is gonna, be here soon. I don't know why telegram is soon because it's already working and we are like we have implemented the vape destination. So you can like name it like anything and put your own url and just like ready to get the answers just for an.

D

E

Sorry, my bad uh once we create a webhook destination, uh the dev console will say that we're gonna authorized uh all our requests. Were this beer token we generate for you, so uh you can catch it on your site to be sure that it was uh dev console who is sending you messages to your web book, but uh we're not gonna go with the web hook only with the telegram right now uh here on the screen.

E

I hope you can see it. You can see my telegram. I have connected deaf console bot with this nice pretty logo. So let's do it create alert. Yep alert is created. We can check all the settings here and, let's uh trigger some events, for example, transfer on the test net, I'm sending some tokens from another account to the account I'm watching for.

C

E

And it is sent.

E

Don't pay attention to the repetitive message about something have triggered your event, because it's all under avid development, uh so here you can see that uh bot telegram bot has sent you about the name of your triggered alert. We can see right here uh and it built for us a link to explorer.

E

I just copy it from here be sure it is opening in the proper browser.

E

This link points us to the transaction where the event actually happened and to the specific receipt, but like it's not many overseas here, so we can see both of them yeah, it's pretty nice working demo, I'm getting even more transactions. I believe someone is sending something to me. Thank you. I really regret that. It's not main net account right now. In the moment. uh Okay- and let's uh look over here uh like it's, not something you're gonna see during the usage of alerts feature on the dev console.

E

uh It is an indexer built on top of near lake, uh which is actually serving all the stuff. We call it internally alert exterior. As you can see, and here we can see all those triggered events uh that was sent were sent to the telegram through all this complex stuff, and I'm like right here, I'm stop sharing asked if I need to resume the presentation with my second slide.

E

Yeah, I'm spammed by the way in the telegram. uh Okay uh here is like a little bit internals. I want to talk about the architecture behind the alerts feature, because what I was showing you. It was a demo of the user interface, uh which has been built by a dev console team, uh we're fortunately not doing a front-end at least for now. uh All we did. uh It was uh the back end or like using uh with the heavier rust usage.

E

So I want to represent our architecture as like rust as a plant keeping the earth and stuff. So everything is working uh thanks to alertix error behind the scenes uh yeah, uh we actually use uh near lake framework for that and uh really happy actually to uh use the stuff we have built. uh We use it. Also, that's why we encourage all of you to use near lake instead of near indexer framework, because it's much cheaper and it's more smoothly uh like it works more smoothly. So please uh reach us out.

E

If you want to build your own indexer, and that was like an example what you can build with an indexer by the way yeah. So I guess I'm done, I'm ready for questions. uh If there any.

E

Yeah, I see, I don't have any questions, so we can continue and then answer questions later. What do you think.

A

Sounds like a good idea. Awesome thanks. So much.

C

Yeah, let's uh tiffany do you, you have other updates. So uh do you think we? We should answer the the question right now and have a pause or do do we keep going.

B

Yeah, I think we can answer some questions about the major products we have and you know, and before before going to other ones. So any.

C

B

C

Yeah josh, may I ask you to to read the questions uh yeah absolutely.

A

Yeah yeah no problem, no problem, um yeah one individual just asked about. I I believe they're referring to the api, um the restful api that we created, and they just want to know. If there's a rate limit or should you should we be using it lightly for now, uh is that available for them to use, or is that like a temporary.

C

Yeah, so it's it's there for very early preview, so we can share with community in terms of like trying it out, maybe just uh providing early feedback, but it's definitely not ready for any production use or advertisement as a.

C

Product primary release will integrate it into dev console and at that point, once it's launched with dev console that will be the official release date and we plan to have it quite soon. uh There are now specific dates at the moment that we can share, uh but stay tuned to. We are, we believe that it's quite uh close uh and we'll definitely show how the integration could look like in the console of other services during our next uh updates. The definitive brain.

A

Awesome cool yeah jack also just mentioned that yeah, like daily balances, are really hard to get, uh um especially for evm chains, but so useful for analytics um yeah. I know this is gonna, be super helpful um for a lot of folks uh in office hours that we get daily people oftentimes, it's rpc endpoints, which endpoints can I use to query accounts and give me information about it, and then we have to go okay.

A

Well, I actually gotta go into indexing and then yeah it's it's it's a common thing that we that we um talk about and yeah to have something that's very familiar to especially web2dubs to have this like restful api where they can easily, you know, send get requests and post requests. Are there posts? Is it just right now, just querying data? Will there be like um like post requests, where you can actually modify blockchain data using this api uh advanced api feature.

C

There are no no touch plans just yet because there are plenty of laughing fruits in terms of like getting the data first and later on. Yeah we'll explore the space of how we can simplify and address the problem of submitting transactions through api, because uh it's a bit more complicated and involves key management and and signing the introduction.

C

So it might not be as simple as just rest api. That's why we we're not uh yet exploring the space cool awesome. Of course,.

A

Cool um someone just says uh disease and enhance api. Allow requests similar to uh near cli view state. um I would I would imagine yes, it's it's. It's similar like um in that uh in cli, under the hood, it's using uh near api js, which is making rpc uh calls that's just viewing state um and you're just kind of pretty much using the same thing. You're using rpc endpoints to or are you using are no you're, not you're, not using our pc, endpoints you're, using.

C

The indexer you do.

A

Both both okay.

C

uh The the questions people would have before, like whether I should use indexer or should I use indexed database or should I use rpc and usually the answers would be like you would need to use both so instead, what we actually offer right now, instead of you needing to worry about all those different sorts of data, we actually combine it together in a best, meaningful way um and yeah you, as like.

C

I'm trying I'm still trying to understand how um like whether the question, the original question was about like the very specific type of response, um shape and structure, or it was just about the general um approach, but the apis that we provide right now they are similar to what the json rpc reply is, but we actually restructured for a better um alignment with fungible tokens and also to provide more meaningful information in one reply. So you have all the necessary metadata cool so.

D

C

D

Sometimes we add some information from the database that we can share if it's useful in the context. Sometimes we omit some fields if we think that so, for example, if you want uh detailed metadata, you can ask about this, but in general uh our guess is that you need just some kills from it and that's why we simplify the interface a bit so yeah.

A

Cool awesome. Thank you thanks. So much for the clarification and context um yeah, and hopefully that answered um some of your questions. If not or if you have follow-up questions, please feel free to drop them in chat or the q a button at the bottom of your screen, but yeah it looks like that was all the questions I had so far.

A

um Yeah. If you'd like to proceed, you can and then uh yeah again keep keep posting away questions if you guys have them.

B

Sounds good yep, okay, moving on is the rpc stash page wireframe I put almost because you will see what I mean by almost it's not really a wireframe as much but um yeah. So uh I will also share this link in the chat. So we also have it it's. It is actually a public link, so it is available for everyone to see um and to comment, if you guys want to so I'll post this in the chat.

B

Where is that? Okay, I don't know where the chat is here cool um so going over the call, barely a wireframe, because it just it's. Basically, I'm not a designer, I'm just using ways to try to visualize what I meant by having the stats page ready um most like so high level.

B

There will be a couple of very important metrics, which are the total volume of your rpc request or request success rates of your rpc request and number of invalid requests, and, last but not least, the latency on the top of that and those from our brief user research are the most important data that we see developers care about. Just by a glance they want to understand. You know how many of my requests are passing through.

B

What are the problem with my request or overall, how fast are the responses um following after that is the time series of the total request volume uh chart. So you can see all of your requests by time and you are able to sort of get an understanding of either how many requests you're making or you know, if you're, not using bots or any it's based on your implementation. Sometimes from this, we hope to give you an understanding of how active is your dab or is your contract at a certain amount of time?

B

um So that's the second chart. Third, one is the method breakdown of your rpc request, so for our rpc request, you all have a lot of different methods that you're using, and hopefully this will give you an understanding of how many of each star you're using and if you want to do optimization or you know any any things that you want to get from this. Hopefully this can yell some helpful insight. Next, one is the request status so under similar to what I mentioned above understanding.

B

How many of your requests has passed, hopefully with a good rpc service that will provide? All of this should be success right, um so it should be expecting a very huge grain high instead of a huge instead of a breakdown of all of all the rest. Next one will be a list of requests, status and errors. So in this list we hope to just ignore.

B

What's actually here um in this list, we hope to give you a list of all the requests you made, including all the status and the arrows that you can potentially click on click in and understand. Why is this failed? Why it's not running as you wish. This is very this. Hopefully, at the end of the day, will be helpful in debugging and in maintaining stability.

B

All the efforts around making rpc requests and going after um is the geographic distribution, so we're actually able to uh grab the geographic distribution or geographic information of where the rpc requests are coming from also depending on implementation, but most most likely most of the dabs or contracts or projects out there are able to utilize. This to understand, where are the rpc requests?

B

Are getting made, meaning, where are your users are coming from right, so um we'll provide you with a map that shows uh the overall distribution and we'll also provide you with a short list of the top countries that you should. You know really focus on and taken care of in terms of your overall users.

B

uh That's that's it for the first mvp phase of the stats page, we're still passing it through the design phase. So it's not definitely not going to look like this, but uh as a wireframe, it just shows you what we want to provide, and this is really. This is something that I really want to get feedbacks from. All you guys on. Is this helpful enough? It is you.

B

Are we missing something that you guys are interested in um and um and yeah, and hopefully once we really release this, it's going to be put in use and- um and you guys will be able to you- know fully utilize this, so that is that um the rpc stats page, um like I mentioned there- are two questions that we want to ask is what are the metrics? Do you need and does the current visualization make sense?

B

So really looking forward for that answer, um even though it's not in this call, we can also have it um at the offline when we share it to the public, but overall yeah. This is really helpful feedback if anyone can be sharing any of their feedbacks, so cool moving on to the next one we have analytics on console and I will share my screen by having this ready for now. So I'm not sure if all of you guys are familiar with the console.

B

um I hope sorry, if not, I can just log out and re-log in again, but for the sake of this particular demo, then console team will be able to double the actual onboarding flow, but for the sake of this demo, we'll go through the analytics page.

B

So, in order usually in order to add contracts into analytics page, you need to have contracts in contracts page first, and uh I have actually already added the near crowd contracts here um and what it will do is it will automatically just fetch that contract, you, you add it in your contracts page and it will show an analytics page, we're still working on making it actually color matching right now. So so this is actually a service, that's created by the wamby team, and they have created this service for us that we're embedding into console.

B

um So thanks to wambi team, but as a result, we're still working on the color schema and design to make it more aligned, and it's coming it's in place, but uh yeah so just to go ahead and really you know show you guys uh what is the analytics page is having here. um You have a date filter that you can ultimately filter any time after or before previous.

B

We have a lot of options here, so you can really define the time that you wanna you care about, and you wanna look through um and we have contract tab that you can add. Actually, multiple contracts, so this works really well. If you have a lot of um subcontracts uh within your contract right, so you have a lot of sub-accounts. You want to see as a whole, then you can actually, you know, use the filter here to see like all your contract and all of that information.

B

um So from this we have a couple of high-level data. The total number of transactions, total volumes, uh liquid balances of your account uh total users, which is you know, very, very unique and very helpful from my previous experiences and user medium lifetime. So how much? How much time is your user? Currently spending on your dabs right and the total gas spent something you care about in terms of the cost and further going further?

B

We have daily transactions and user count, so it's a daily breakdown of your transactions and your users, and it will have user retention, which we actually did some calculations in terms of the amount, the num, the monthly number of your new users use a retention rate, so we actually took that data did a lot of calculation and give you that retention rate that you will care about. Of how many people are actually using your d app moving along is the active user, so monthly, active user, weekly, active user and daily active user.

B

We also have a calculation ratio for you so similar to any of your web 2 experience or the most important marketing data usually will give you this number, which will very helpfully uh inform you on how active is your user? um How you know the the the actual overall health of your user engagement of your d app and moving along? Is the volume and balances so how much volume are transacted in your dapp, um how much your balances are and what are the total top users by total of all the transactions?

B

So who are the users that spend the most money in your dap right? That's should be something that's.

B

You know it's very important for you and if you want to target these users for your eardrop events, campaigns or any specific marketing campaigns, this is where you can look for them, and last but not least, is the gas price, the total amount of spending and the daily amount spent, um and that said for the analytics screen and last but not least on this, you will also be able to see an indexer tab, which is the like section on console yay, and we have carefully designed this page and has the little pagoda slashed uh boat here and a little lake seems like it should be uh clear.

B

uh If not, please share your feedback on. uh It doesn't look like a lake, it is hideous, we'll change it, but overall yeah we, um we concluded four major reasons that you should use like. We think it is productive, it is resilient and you have immediate access to all the full stories histories of uh the new blockchain and is very familiar. We are providing you with as much of the languages that you can use to easily create your indexer and more to come, and we also added the most helpful.

B

Very jump start uh examples here in tutorials, so you can have you know you can look at the printer account watcher and if you are already a little bit advanced, go to the nfd index or one that blocked in his demo last time. So that's all the demo. I have in terms of the um the things that I have demo here, a couple of things. There are multiple things and I think it's the time that we launch the polls.

A

Awesome thanks so much tiffany.

B

E

I beat all of you in the head game.

A

The pol the poll blocked you on my screen, so I couldn't see. I can't see, oh so great, so good.

A

Cool yeah for everyone uh watching after the fact we just lost a poll uh we'll be dropping a link to that in the bottom of your screen and actually yeah under the description. uh There will be a link to probably like a google form that you can fill out. uh Yeah we're just kind of getting a little bit of feedback on what was presented today, whether or not you would be you'd find these things useful and what exactly you would find useful and feedback as well. I imagine yeah.

A

There also be areas in which people can provide feedback.

A

I know in the beginning we talked about the rest api and like a link to the repo where people could probably have discussions in there or you know, make suggestions submit issues, but for some of these other um things that we presented today is there where's the best place for people to get in touch with you uh and uh leave feedback on these products?.

B

Yep, so uh I think, as always, we have this. We have the screen of all the feedbacks that uh the you know. Usually, uh we would like to just uh direct people to stag overflow, but we also have all these free posts here that you can actually interact and talk to us about um and I'll also create a google form that will include the information on the on the polls um and we'll likely add more information on you know we will have my calendar link, uh you know like any.

B

We will have the we have to do a weekly updates, that's blocked and uh help crafting every week. So that's also a great place to follow. What's come next and interact with us share feedbacks there um you know, comment anything there, so that is also a great place for us to um and also it's a good place to keep track on all the teams uh work, because I think all the teams also uh share feedbacks there. Oh so sorry share updates there too.

A

A

Awesome awesome.

B

Yeah uh for the polls yeah, I don't. I don't think I need to clarify, but uh I added a payment method question. um I'm not sure if people are aware, but um one day in the future, we will start. uh You know charging a little bit of our products, and this is a quick question on understanding what what you guys prefer in terms of the payment method, and we really hope to at least provide that as easy as possible.

B

If you know usn or near or any other stable coins uh works the best for for all our community members. That's that question. That's where that question is coming from, not not that you guys need to pay us for, uh for this show.

A

Cool well yeah. If anybody has any questions or comments, please feel free to again drop them in the chat or in the q and a button at the bottom of your screen. um We'll give a few moments for anybody to ask um ask any, but um is there anything else uh to present or is that the the uh does that conclude the presentation for for today.

B

Yeah, so I actually have another board: that's about the data product landscape.

D

B

But it is very much a brainstorming mirror board, as you can see, it's very messy, um but overall what we want to get from this is as we are offering more and more. You know products um we just introduced enhanced api and uh for the beginning I also mentioned you know there are confusions around. Where should I go with xyz right? Do I do I go rpc? Do I go index or do I go?

B

You know somewhere else, so we hope to really think about the data usage and data information, curry needs and all of those in one setting. um So, and so this is, this is a board that we use to to brainstorm ourselves, um but we also hope to you know, go through this with all of you guys um to share what we're thinking and uh either you know, synchronous, hero or asynchronous.

B

You know when we publish to youtube or having discussion with the lovely deferral team on on more on this is, um is that we really want to understand how people are currently using all of these products and how people are currently thinking about using this product, or you know what they're thinking of or what you know when they're making decisions on where to get information where to get data? Why are they making that information?

B

Why aren't they making that choice um so overall I'll go through each by each, which I think we we all know what it is, um but just for the sake of you know, sharing or making this brainstorm easier um for everyone who's watching. um We have the whole lake system over here, which boston did a demo before, which is very awesome.

B

uh Lake itself is the you know the data pool where the data lake recurring forum is a huge data machine and the framework is what we're you know, creating to help people easily use um the lake powerful machine and from our our brainstorm, we're thinking it is very you know it is.

B

It is a very powerful tool that really gives a lot of flexibility, and uh it should be also familiar and easy to use um with our you know, with our with our work on having multiple language offering and a lot of different tutorials and examples offered and going after there is the enhanced api we just announced, so we really hope to lower the barrier of entry um for people to get the data on top of our blockchain by offering this by offering this api and it's the rest api.

B

So it's very standardized um you know like, although just mentioned we're using open api, so there a lot of you know a lot of great benefit. You can get from that um and we really want to understand. You know who are the people who mainly want to use this, and uh where are the cases where you guys think uh it is most helpful in your day-to-day development to use to utilize this? And what is the combination right? You may not only use one of this. You may also use it. You know pick and choose.

B

You may also use like, in addition to api and we're wondering you know how. How is that? You know why.

B

Why are you making such choices and what drives you make those choices and the next one is warehouse, so we're calling in indexer explorer, which is the name that everyone is more familiar with the postgres database, um we're changing the name to warehouse, because it is just you know it's more generic and it describes what it actually is um and um we're we're also wondering so right now we're offering that as only public access to a lot of uh people out there to the community, we're also offering that one-on-one to a lot of our partners and we're really curious to know who other people who are using who are using this indexer for explorer the warehouse database.

B

We offer what are the major needs there? What are the careers that you guys are using most likely and most often- and why is this a better choice than you know, than lake comparatively to your specific needs and moving on?

B

We have alerts which would just announced- and this should not be adding a confusion into this mix because we're thinking that it should be mostly around monitoring- and we just wanted to also validate this with you guys on making sure that this is why we want uh why you guys are interested and wanted to use alerts, and if that is the case, um are we doing a good enough job in terms of helping you monitor your your the app's performance and, last but not least, we have the archival rpc and regular rpc, so this team um also we're thinking about providing a unified data or query information feed that you know that really should not bother you.

B

The users on choosing. Am I using rpc? Am I using the archival rpc? Am I using the indexer, so we hope to really you know, really figure out a way to really ease that burden on you. So what you only need to care about is I want to get an information.

B

This is the place I can go to. It's either link it's either api, and then I use the regular rpc in my day-to-day interaction with the blockchain. um So this is the goal that we're aiming at we're thinking about ways that we can actually optimize archive rpc and provide that um information to you without you know, without the need of choosing- and uh you know asking uh where, where should I use? What should I use? Why should I use xyz?

B

So this is the overall landscape that we're thinking and we welcome any feedbacks ideas, and um you know just tell us why you're using what you're using tell us the combination that you are using right now, the problem that you're facing when you're onboarding and um you know, and the problem you're facing in any of your experience.

A

Cool thanks thanks so much.

C

This landscape and yeah- I I I hope it makes certain sense uh to to people- and I I like to highlight that basically they are the very different type of offerings for different needs for different audiences. So, if you're a data scientist, you would probably go with data warehouse and just interact with and build your machine learning.

C

Products and analyze the data this that sits in the history of the blockchain. um If you are the app developer, you would probably be more interested in either data api. If you are building mostly front end or if you you're, building something more advanced, then you know lake would be your uh probably choice and monitoring is a boring thing.

C

I I definitely don't recommend going there any anybody uh in terms of like implementing yourself, so I think we we should take care of uh this uh part for you guys, and uh hopefully my intern will be just a brief for you and you just click a button and you're all set. So that's basically uh sum it up uh version of this landscape.

C

uh Sorry josh, I uh I interrupted you.

A

No, no! No! No! That's that's perfect! No! I was just gonna. um The only thing I was gonna ask is: uh is there a link to this miro board um that individuals can take a look at? Is this like an interactive thing? Do you want individuals to make comments or or.

B

A

With uh you on this board,.

B

Yeah, I will, I will create a public picture of all boards um so that yeah so throw sticky notes, as we do.

A

Cool sounds good. Well, I don't see any uh further questions uh but yeah. Thank you. Thank you. So much uh again uh I really appreciate yeah. No. This is all really awesome. Stuff, um yeah lots of unpacking lots to think about, um but yeah uh yeah really awesome, seeing the progress that's being made uh with the rest, api server and then yeah all the dev console uh features that are that are getting uh implemented yeah and I'm really I'm really stoked for the next couple months and uh yeah and near con.

A

I think it's kind of going to be like a launch for for probably all these uh products and services as far as like a time frame, but we shall see um yeah.

C

Definitely it will be a lot of uh new stuff to talk about during neocon, so I'm not sure uh josh. Are you making more and more like announcements about when the airport is getting.

A

uh Went well I mean the near near con is, is announced, isn't it it's like officially.

C

But I you know it doesn't. I think it's worth to mention the retreat over in oregon.

A

Yeah absolutely near org check it out come to portugal hang out with the these uh fabulous people on this call and other community calls meet us in real life uh september 11th through the 14th in lisbon, uh near khan.org, um check it out, apply to to hack sign up. um There will be side events, all sorts of fun stuff, so yeah, no, I'm looking forward to seeing all of you guys cool.

A

Thank you. Thank you. So much uh appreciate it um have yourself a great rest of your day. Oh and next week we will be off um we're having a near-wide uh wellness week for everyone to take vacation off and rest and recuperate and not focus on work. Hopefully, you'll walk away from your computer screens and not uh worry about pushing code or working on planning all these new features, but yeah.

A

So we won't have a community meeting next week, but we'll have two community meetings the following week and I will be sending emails out uh as a reminders um and uh make an update uh for for next week's meeting but uh cool until next time chat with you guys later, thanks again and um yeah, we'll see we'll see you in a couple weeks. Yeah.

C

A

Ya. Thank you. Everybody.

C