NEAR DevConsole / Explorer Community, 23 May 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: DevConsole Community Meeting (May '22)

Description

Progress on the Developer Console & AMA session!

Join the next session:
👉 https://near.ai/devconsole-explorer-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
#nft #dao

A

All right well welcome everyone. We are going to have our second meeting of the dev console explorer uh monthly community meetups this week. We're going to be talking all things, dev console with josh quintal uh josh. You want to introduce yourself and take it away.

B

Yes, thank you. So hey everyone, I'm josh quintel. I am the product manager on the dev console and explore teams here at pagoda, uh and today I'm really excited to we'll kind of walk through really all of it. With you, I'm going to talk about you know what dev console is how it fits in with the rest of the pagoda products and the new ecosystem.

B

We're going to go through a little demo of what's available today and then I'm going to talk to you about what we're working on this quarter and then in the more distant future as well. I'm.

A

B

Excited to get your feedback on those things, cool and.

A

uh But yeah just before josh gets started um just as a reminder. If you have any questions, please please feel free to drop them in the q, a section in the bottom uh post them as we go and uh yeah we'll we'll try to answer them. As uh as the presentation moves, we'll find a spot to address all of your questions or comments so yeah take it away.

B

B

All right, good stuff, so developer console what what is it? What is this thing that we're talking about um so before? I actually dive into that I'll plug right away, that if you go to console.pagoda.com you'll, be able to try this out at any point during this um so the place. I always like to start. This discussion is the development life cycle, and so you know there's various different versions of this, but I like this very simplified one just for talking through this.

B

um So of course, if you're going to develop any kind of you know, dap or even software application generally you're going to need to start. You know coding, and this is of course, assuming that you know you have requirements, you've done user research, all that good stuff. So it's time to develop, you need to actually code your application.

B

You know we've got many great tools to help with that right. You know. You've got near cli. You've got in your api.js for developing on the front end uh things of that nature. Then after that point, of course you need to test what you've done up to this point.

B

So, of course, in your sandbox, uh various workspaces, libraries for javascript or rust are great candidates for that, and so, once you've got your code, you know written and tested it's time to actually deploy it to a network oops accidentally clicked there, of course doing that through near cli, is going to be how that's going to get done and then once it's on the live network, you know where do we? Where do we go from here? We've created our dap.

B

Now it's in the wild people are using it uh it's time to actually monitor and operate this dab and that's really uh where dev console comes into play, so your adapts made it to production, and now it's time to you know, start observing, what's happening with it right in the sense of analytics monitoring happenings to your smart contracts in the uh as the app is live uh things of that nature really like said, managing operating and monitoring the application, it's really kind of where it fits in, but even more broadly than that.

B

So if you do go to the pagoda webpage- and I don't want to belabor this too much- because we're not really here yet like kind of looking at the future- so currently we're focused on this monitoring and operations aspect. But if you go to the pagoda website, you know you're going to see this tagline that you know pagoda is the first ever web3 startup platform and so you're going to hear me use the word integrate a lot later on in this presentation.

B

When we talk about the the future of dev console and that's because it is going to really broaden out into being this web 3 startup platform. So currently it's very much focused on development and even more narrowly on that monitoring piece, but eventually you're going to see integrations with other departments in pagoda.

B

So things like having your dow manage aspects of the app um you know, that'll be hooked into, of course, funding and things that the doubt generates so really hooking up really the development life cycle to really the broader business lifecycle as well um like. I don't want to go too deep on that, yet because that's still very much in development, but just give you sort of a sneak peek of what's happening there.

B

So I definitely don't want to belabor you with a bunch of slides and reading right away.

B

So let's hop right into a demo, uh and so I'm going to go over a portion of an nft marketplace tutorial that we have integrated into the developer console, which is really great for onboarding, because in addition to the tutorial that you would get if you went to the docs, there are some interactive aspects that we're able to add with the power of dev console and then we'll also take a look at the analytics and contract screens that devconsole offers as well.

B

So I will hop into that and actually, let's test windows out here, okay cool did that uh josh or someone can you confirm? Did that actually switch my desktop or do I need to.

A

No, I just see, I just see the demo.

B

Yeah, okay, yeah. I will stop and restart that then.

B

Oh interesting, okay, maybe it's a windows thing um hold on one moment, I'm just going to drag these windows back from my one of my desktops back into this main one.

B

B

Nice yeah note for anyone watching yeah. If you use multiple desktops and windows, zoom is not going to it's not going to share anything other than the main one, okay cool. So, on the left hand, side here we've got dev console on the right hand side. I have my actual uh cli over here. Let me zoom in on this, so you can see it a little better. I'm sure it's not great.

A

Yeah, that's better.

B

Yeah, I can do the same here. No promises on the dev console interface scaling politely for zooming, uh okay cool, so I've already logged in in this case, but I will mention that you know you can log in with either your email, github or google, um but yeah so either way I've created an account here. uh This is the list of projects. You know projects are kind of the main organizational unit within dev console uh for lack of a better word, uh and so you know I've got a couple here.

B

You can, of course, create a new one. I'll briefly show you a look at that, so we're going to make a new project here. um You could of course, start a blank one if you maybe have an existing dap or you know, you already know what you're doing you're going to be.

B

Writing a new dapp and you're familiar with near, but then there's also this tutorial option here, uh which we'll take a look at, and this is where you can select this nft marketplace tutorial uh that we're going to go through right now, and so this is like. I said this already exists uh in the documentation. It's a great tutorial, you know, takes you fully zero to hero from nothing to a system of contracts for an nft marketplace, um but with some extra interactivity here in dev console and then other options.

B

Yeah would be like our crossword tutorial, which is on near sdk dot io, if you're interested in that.

B

So in this case I'll click into this existing project and actually, when you initially create it here, you'll land on this tutorial page, which is actually the tutorial itself. um And so you know we're not going to like read through the whole thing, but I'm going to I'll kind of hit the highlights. So you can see exactly like what you're getting here. Benefits was.

B

So you won't see, you know, you're on the documentation is actually this card uh over here in the lower left-hand side. This live contract data card.

B

uh So you can see here that you know we have my account name that I'm using for this contract and then we can actually see the status of that as I was moving through the tutorial. So we can see that the account exists, the contract is deployed to it and it's been initialized and also down. Here we get a list of the tokens that have been minted. um You know the nfts rather that have been minted throughout the course of this tutorial.

B

uh So let me actually back out here and I'll. I will start a new one, so you can see it just kind of from the ground up.

B

Cool uh and so going through here, you can see that yeah you'd have an opportunity to, of course uh input your account here. uh In this case, I won't use denver.

B

Let me just use my testnet account, so this account exists. Yes, but there is not a contract deployed to it or anything and, of course, without it being deployed, it hasn't been initialized, so just kind of a little overview. I'm not going to go too far into this.

B

We're really just going to go to upgrading the contract, so you can kind of see that everything responds live, but what you start out with in this tutorial, like I said, zero to hero, so you start out with this pre-deployed contract um you can then nfts with, and then we start to go through and break down like exactly how that contracts composed and then once the nft itself is built. We then move on to like the on like marketplace system uh from there.

B

So in this case I'm actually just gonna hop right into uh the minting step, because that has the full that has the full code that we're gonna need to deploy here.

B

Tutorial, on my left hand, side make sure the right branch.

B

Actually, sorry minting.

B

Okay, it's because it's not yet cool all right. So in this case, um yeah we've gone through, we've described, you know, sort of what uh we looked at the contract itself um as far as the structure of the nft contract. This is really nice. You know this is a standard on here, of course, like you would expect on other ledgers, so really we're at the stage here where we're going to deploy the full-fledged nft contract, we're actually going to mince uh an nft.

B

So I'm going to come over here, I'm just going to literally follow along.

B

And so this build step here for those actually, this would be an interesting exercise in the chat. If you're, really quick put, you know, put in your experience level of developing with near that'll kind of help me with how much I should be describing exactly what I'm doing so for now I'll kind of default to uh just describing it in like mid-level detail.

B

So here this build step. We have you know in here: you can write smart contracts in rust or an assembly script and coming soon javascript.

B

This particular contract is written in rust, so we're going to run yarn build here because that's going to compile it into webassembly, which is what we can actually deploy to the network.

B

You can see here this is running cargo, build in the background and then it put that output in a res folder. um I need to log in here real quick.

B

uh Actually, I want to import a different account.

B

Let me bring in my josh q account here that I added to the card earlier.

B

B

Cool this is connecting uh this is connecting my oops.testnet. uh This is connecting my wallet account with or my near account, rather through the near web wallet with near cli. So there you go see the action completed there in the console. Now I'm logged in we can close that window uh and then from here we're just going to for convenience throughout the rest of the tutorial uh export our contract name as a variable.

B

A

B

Be really helpful throughout the rest of it. We won't have to continually retype that, echoing that, just to confirm you can see yep joshq.testnet is there, and so now, throughout the rest, when we like copy paste these commands, you know you can see. We just have the the token for nft contract id. There that'll make this much easier.

A

And just for those that aren't familiar you, what you just did was did random near login, which saves a key, a full access, key to your local machine that way, you're enab you're able to perform all these transactions like launching the contracts and everything moving forward by using that full access. Key that you just saved.

B

A

B

You uh and cool, so you can see here. No, so if you remember correctly, the uh account you know check mark was done, of course, because joshua.testnet existed, but you can see there actually live and once the contract was deployed that it is yeah.

A

B

Actually was reflected here within the console a little little blurb on the quick info card itself, uh and so, let's actually mint an nft. Now.

B

Cool and yeah quickly for reference we show here, you know the the token metadata um that you'll want to include for this. So here I'll, just kind of quickly note we're just filling in the id here we're giving it a title, a description and actually uh we've got a media url here that's uh this is an image hosted on ipfs uh you'll, see here in a bit.

B

In this case the receiver is the nft contract.

B

Itself, ah but that didn't work right because it's not initialized as we can see here, so let's actually go back and.

A

B

In this case, initialization for the nft standard sets the owner.

B

And look at that there we go so it is initialized, but we don't have any nfts minted yet so let's actually go back and do that.

B

And now that it's initialized, this transaction should succeed here in a moment, and it did. uh We didn't get anything back because it was a success, but we don't see any tokens. Oh man, I'm just full of errors during this presentation, uh but it's because we actually don't have this total supply method, implemented or nft tokens for that matter, so we're not able to enumerate uh the nfts that have been minted by this contract or even to show the total supply so on other protocols. Right like this would be potentially a panic moment.

B

If you didn't have a proxy router implemented or something like that, you would be unable to upgrade this. You would just have to you know kind of deal with it potentially alert your users or something like that. If this were in production, but on near you are able to upgrade in place, which I will demonstrate here.

B

All right- and so you know you know, tv magic, I'm just skipping ahead into the end of the enumeration step here, since I know that that's we want to enumerate the tokens uh and show the total supply.

B

But you know if you were going through this you'd want to definitely read through the enumeration section, um because we break down. You know the methods in more detail there, and so from here. It's actually going to be just as simple as repeating what we did previously I'll talk more about upgrades in a second here. There are some constraints, so we build the new uh the new contract we're good. It's done. In fact, it was even happened even more quickly that time.

B

That's thanks to rust or thanks to cargo, I should say, uh and then we will actually just redeploy. It oops come down here, and so you can see it's noted in the tutorial, but we're going to get a warning. First, yes, and it notes you already have in a contract deployed here. Do you want to proceed, and you do want to think a little bit well, preferably before this point, but this is at least a little reminder, so in this case we're upgrading the contract. We do want to replace it.

B

That's fine, but you do need to make sure when you upgrade a contract, that the serialization of your data is the same. So basically the data structure is the same.

B

um There are ways you can translate it there's a lot more detail like I'll drop, some links uh in the chat after this, um but in this case we don't have to deal with that, we're actually just adding methods to access the data that already exists in this contract, specifically once again the nft total supply. So we want to get that total number and then a function to actually enumerate uh the tokens. So since we're just adding accessor functions, this will be totally fine.

B

I will proceed and like magic, look at that now we also get the total supply and, of course, we minted that one earlier that I showed as an example and there it is, we've got the go team. Gif that's hosted on ipfs. You can see all the metadata down here um so yeah that super exciting. To me, I came from ethereum a little bit about my background.

B

I've yeah worked at truffle for five years before this, so that kind of blew my mind uh when I came over to near initially, uh so I really love showing that off.

B

And so that's really all I'll cover now just kind of like highlight some cool features of near and also show like the benefits of seeing this you know live as you're going through the tutorial. You know you get that kind of like nice moment of like yeah. I did something without having to like query back and forth uh in the cli.

B

So let's take a look at some of those other screens I was talking about. You can see, there's analytics and contracts over here on the left, so I'm actually going to switch projects.

B

And so first you've got this contracts screen right here. So this is eventually like we'll talk more about the expanding feature set of this, um but for now you know the contract screen at this point allows you to add your various contracts for your dap in here. um Since this is you know to the point of monitoring and operations like what you'll mainly be managing as the components of your project are, of course, the contracts that compose your dap, and so currently you add these contracts to this screen.

B

You see some quick stats that you could get here without necessarily having to go to the explorer, and you get a nice merged up transaction list down here. So you can see here that yeah this is actually coming from both contracts.

B

So just a nice quick place to kind of at a glance view recent activity from your dap.

B

In the future, this is going to expand to have much greater integration with the explorer, in the sense that this will be a full like paginated scrolling list of transactions. You could break them down individually by contract. um There will even be forms to interact with your contracts. Things like that, but we'll talk more about that uh in a little bit and then there is also an analytics page over here, uh and so I don't have any. Let's see, maybe I fired them off on magnet.

B

Okay, perhaps we haven't picked them up yet I did fire them off only like a second ago, um so either way: oh yeah, it's fetched. Okay, that's right! It's fetched once per hour um so either way, but on this screen, um so you actually, when you sign up for dev console, I need to take a step back.

B

You get some api keys for our rpc service. So currently you know the new rpc you could just use it logged out it's a free service at the moment, but in this case you know you get these keys, and this is nice because then you can actually track your usage and get some usage analytics on that. So this is things like calls over time, breakdowns by method call. You know your total number of calls things like that, so collecting some basic usage stats uh around your use of the rpc.

B

Eventually, that's going to expand into full, like kind of build your own dashboard type of setup around smart contracts, uh but yeah we'll talk about that in a little bit as well.

B

So let me come back down here, switch over to the presentation again.

B

Back to dark mode, so that's really kind of the in dark modes on the way, as well, actually for dev console on that note, um but uh so that's kind of long and short of what's available now you know we're in a very like kind of foundational state right now I would say, um but if you're starting out definitely check out that nft tutorial uh and you know interactive features there.

B

That should be very helpful and, of course, like I said getting some metrics around your rpc activity uh very useful as well, especially you know, when you're making calls from the front end now you're, actually getting some basic user data as well. You know not necessarily just your own cli usage.

B

But where is this going right? I mean I mentioned monitoring. I mentioned operations, all these big things um and yeah, so we those are in the works. So as far as the infrastructure management piece right, we talked a little bit about rpc as a service, so you know that's there, um but there's also, if you've been uh following near lately. uh We also came out with something recently called near lake, which is essentially a kind of the next iteration or replacement of our near indexer framework that you might be familiar with.

B

So now we just have a nice like unstructured data lake, uh it's actually s3 on aws. You can just pull down uh data from that with your own writing, your own indexers, it's much easier to use than the previous indexer framework was, um and so using that service and managing that is going to be surfaced through the dev console as well kind of the point of integration.

B

Another thing we're working on also contract forms, so this is, if you're familiar on the near ecosystem, with like stats gallery, for example, you know you know that that site can list out the methods for a contract that you give it, but we're going to take that a step further and actually implement a full interactive form so really great for, like quick demos, quick integration tests, things like that you'd be on that contract screen you drill into your contract.

B

You can execute a method and then, with that additional explorer integration, you can then see the result of that call, including the full. You know execution path and all that without even having to leave dev console. So it makes this really nice um kind of like integration, testing life cycle happen there all in one place next up alerts for sure. So this is um anything that happens.

B

You know on chain, so things like if a transaction succeeds or fails uh if a certain method is called on a contract with certain parameters or a certain output, um if certain like actual event, events like your smart contract events that you've coded are fired things of that nature. We want to let you know about those things, whether you're in the console or not, um and so this is where I'd love to hear where people would like to be alerted.

B

So our first instinct was email, of course, right when you're on the go when you're anywhere, you know you get an email you're going to want to be able to see that, but then also providing web hooks so that you could potentially hook up. uh You know whatever service you'd like, um but you know to that end. We do want to provide convenience. So if there's any other services, people would like to see definitely drop them in chat.

B

You know something like telegram sms things of that nature any destination you can think of that you'd want alerts to go to another great thing about this in the future as well. Is that eventually, we'd like to be able to trigger uh mitigation functions in the case of you know potentially negative alerts right like let's say your balance is draining. um You may want to trigger something to stop that, but we'll take a look at that in a second and then, finally, uh you know greater analytics or actually building your own dashboard.

B

So we didn't get a chance to look at the charts today, um but the rpc usage. You know, usage data, guys get pre-configured and it's limited to the rpc, but where we really want to go with that analytics screen is the ability for you to build your own dashboard based on metrics around your smart contract. So let's say your astro dao. You might want to actually see like number of dows created or a breakdown of dao's by type things of that nature. So really visualizing your smart contract data, not just usage of the network itself,.

B

So, to kind of go into a deeper on the alerts and then also on the building. Your own dashboard features um kind of like to present these. You know a little more stories rather than just dry descriptions, uh and so here are around alerts. I sort of uh preempted myself here, but uh we'll go through a scenario here, so our d5 smart contract's been hacked. Oh no.

B

What can we do, or at least in this case, how can developer console, have prevented this scenario or can prevent it in the future, uh so you'll be able to configure alerts here, like I mentioned, and so this is just a very, very bare mock-up of what this might look like, and you can actually just read it left to right. So you know our defi dap here has a vault contract and we want this alert to trigger on certain conditions.

B

In this case, if the balance change is 20 by 20 percent uh and, of course, in this case we're kind of looking for negative 20 uh in a sense and then also not from our allowed list. So you know, potentially we, as you know, the owners of d5dap would want to be able to move that balance around without triggering any mitigation, or things like that. So you know we uh put ourselves on the allowed list there and then this one's definitely a little in the further out future.

B

We're not gonna have actions right away, um so you'll definitely get alerted, but in the in the more distant future, it'd be nice to have actions, um so in this case to mitigate this negative event right this balance changing by 20. um We could automatically call the pause method uh on this vault contract, so stopping uh any transactions going in or out thereafter and in this case we're going to get alerted via email and a text message.

B

So right here you can see an example of what this might look like. You know we get an email from alerts at pagoda that says: oh the balance drained 20 in this contract. We note when it happened.

B

uh We give you some quick links here to view this contract or your allowed list just to make sure of what's going on and then down here we note uh the actions that have been taken, and so in this case we called the pause method on this contract and then over here you know a link out to actually see that transaction status.

B

So it's an interesting interim step um we could do here is since we are alerting you anyway. uh We may provide, like a quick link uh for you to actually trigger this uh trigger this action or call this pause contract um as a you know, kind of a middle step to actually all the key management and um necessary things that would have to be taken for us to trigger that automatically.

B

uh And then, actually before, moving on from alerts, another thing to drop in chat. Definitely if you have any alerts that you'd like to see of any complexity, really I mean we're going to have to start out simple, but um anything that you thought you've wanted to be alerted on uh definitely drop that in chat. We'd love to hear more about that.

B

So second scenario here I mentioned analytics um this one's. You know a little less dire here, but an nft marketplace right wants to see their best performing collections and artists. How can we do this?

B

Well with access to near lake, we're able to query all kinds of different on-chain data, and so, in this case it's as simple as adding a tile to our analytics dashboard. In this case, we want to see our top 10 artists by revenue, and in this case I displayed it here as a sql query.

B

This isn't really decided yet you know maybe it'll be sql, maybe it'll be graphql, maybe it'll be a form builder, uh something of that nature, but either way just representing that, we are in a fully custom way like gathering the data that we're looking for uh and, of course, we're gonna visualize this in some way- and in this case it's gonna be a bar chart, but you know, maybe you want a table if it's over time a line graph. You know things of that nature, so all the visualizations you would expect would be included here.

B

And so just to make it even more concrete what this might look like. We've got a dashboard. We built here called artist revenue and we can see you know that we clicked this add a tile earlier and here's the other results of what we did. We've got our top 10 artists by revenue here and then just kind of as an example of some other things.

B

Maybe you just want even a single number so like our highest and lowest selling uh pieces are also represented on here, just to kind of give you an idea of exactly where that's going.

B

Cool um so, and what's next was perhaps not a great name for this slide. So as far as what's immediately next are the things we already talked about alerts. Contract forms build your own dashboard when I just went over, but this is really more like the more distant future right. So things like dow integration right like now that we have useful alerts triggers contract forms uh things of that nature. You know, maybe we want to expand the scope of this beyond a single developer. Right, like dao's, are going to want to manage these dapps.

B

um Of course, we'll do this with astro dao. There are a lot of interesting possibilities there. If you're, a member of a dao, we're thinking of starting a dao, definitely drop that in chat as well. I would love to have a conversation around that we've already been kind of investigating some ways. uh This integration could take place and uh they are very interesting uh deployment management as another area there so kind of expanding out uh into the rest of the development life cycle.

B

Currently you know you kind of have to deploy via the cli it'd be nice. If that could be a little more organized visualized, you track the status of multiple deployments within the same network. Things of that nature, of course github integration. uh Currently you know it's separated in the sense that you code in one place, then you're managing it in dev console, but as we're kind of like coming around the development life cycle, uh it'd be nice to you know, have your uh have access.

B

You know to your repository within dev console for various reasons, uh including, like I mentioned version deployments things like that and then finally, you know really there's a lot of places. This could go so I'm curious what you'd like to see and to make that a little less vague, I kind of added two little like seed questions for thought down there like what's preventing you from building a dap right now, if you haven't built one or what's you know, perhaps a pain point or holding you up and then.

B

Secondly, if you have adapt in production, um what's holding back your existing dap? Is there something like you don't want to have to build your own indexer? You need better visualization tools, things of that nature. Definitely would love to hear what you're looking for in that sense, and with that I will turn it over to questions, because I did see that there were some actually there's.

A

B

A

Yeah yeah, we gotta gotta, get a few questions and I think so much uh josh for that presentation. uh Yeah we'll just uh go through some of the questions that have been posted throughout the um uh throughout the presentation, but yeah. If you, if any more, come up or um if we don't completely answer your question, please feel free to follow up uh yeah, we'll keep taking questions until we run out so uh the first one. Actually you went over.

A

Is there any plant uh um yeah to import uh github repositories um so yeah we kind of have that um in the works and um or at least it's road mapped out or uh you guys are thinking about it. um So yeah, that's definitely uh going to be something that they'll work on um next question is the last meeting there was a mention of the near equivalent of an abi coming out. Are there plans to integrate into dev console? So we know what methods are contained within an account or contract.

A

Should one have some code deploy to it.

B

Yes, so yep there is an equivalent of the of the abi coming out. We call it an aci uh in near the ethereum another change, that's like abi's application, binary interface. As far as we call it abstract contract interface, which is where aci comes from, and that's actually what's going to power. Those contract forms uh that I mentioned so we'll be able to generate that aci and that's going to include things like the methods in the contract, along with their inputs.

B

The function signatures uh things of that nature, so that'll lead to those interactive contract forms where you'll actually be able to just like, within your browser, like fire off a method uh against a contract and then, um as I mentioned, to kind of close that loop with the greater explorer integration, you'll actually be able to then see the result of that transaction within dev console. So, like a nice nice like integration, test life cycle kind of living in one place, there awesome.

A

Cool um this is really really cool. Super awesome to get the live data uh while doing the tutorial. Are there any plans to release more tutorials or migrating uh existing ones into death? Council.

B

uh Definitely plans for more to integrate with that live data card, so that I mentioned the crossword tutorial, which actually, if I can pull it up, real quick I'll I'll drop that in the dropped it in the chat, because it's a good one um that one definitely uh will be part of it, I'm sorry for everyone's benefit. Let me pop this in here crossword tutorial and.

A

For those of you that are watching this on youtube after the fact we'll we'll put this in the comments and description below.

B

ah Nice, yes, so it'll persist yeah! Thank you! um Yes, so, but in addition to tutorials, actually one area we're interested in expanding this um is actually templates. So you know. Tutorials, of course, are great um when you are getting started and you want to learn more, but perhaps living in dev console is not the best option, uh even though it's helpful for to borrow features from it. um So we're thinking more of going this direction of having templated projects uh within dev console, so you'd start it up rather than a blank project.

B

You'd have these two other options, one being you would select a template. So in this case, if it is an nft marketplace again, you'd actually just get the results of that that system of contracts and then be able to build on top of it. um You know, potentially that potentially get d5 template uh things of that nature, and then the other option would be uh if anyone's familiar with, create near app.

B

It's kind of like been getting phased out recently, but it's going to have new life, um not only in the cli but in the sense of potentially in dev console, allowing you to then build your own um kind of create your own template uh from selecting various contracts. A certain type of front end uh things of that nature to sort of start out with a bit of a starter project of your own design.

A

Cool that sounds awesome. uh Is there any simple way to add the api keys in your api js.

B

uh Yes, there is, and let me I don't think I closed that window. I can just show you real, quick.

A

B

Share this cool, so actually let me show you how I got here so once you've logged in and created a project uh when you're in that project on the settings screen here. In addition to actually showing your api keys, we have various uh instructions down here for how to add them to the libraries so near cli and your api.js, and we even went one step further and actually um you're.

B

Well, I'm not going to use this api key for anything you know, but if you were doing a real presentation, don't show people your full key, but either way uh you can actually just copy paste this and it already has uh the necessary information filled in. So you can see up here. I have the test net environment selected, so we've already filled in testnet as the endpoint and we've even helpfully filled in the api key for you.

B

So it would just be as easy as copy pasting this into your project, where you're implementing near api js.

A

Awesome um will you somehow be able to send the analytics to your dap from dev console.

B

Send to your tab, uh can you describe more, you might send the analytics to your dap. Maybe.

A

Like rendering or rendering them on your front end, like maybe there's some sort of api, where uh I don't know, I'm just guessing what the what the individual's uh um asking but yeah, maybe yeah, there's some sort of api that you can see like some live interact. Interactivity! That's going on with your contract. As you go to the dap, you can see those stats.

B

Yes, okay, so we definitely do want to have a concept of public pages. uh The dashboards will probably be the first thing to get that feature actually so yeah you'll be able to. If, if we're interpreting that question correctly, there will be a way to like share that a certain dashboard publicly. um So yes,.

A

In that sense, let me know if we answer that question correctly. If we interpret that correctly uh cool uh hi there alerts are good, just curious, how are the alerts implemented? I suppose you have a near lake or indexer listening to the blockchain events, or is there some sort of alternative.

B

uh Yes, it is, uh it is near lake and indexer. Currently listening to the events, you have it exactly right.

A

Cool so like the it's listening for events and then when it notices, there's some sort of logic that we implement where it starts. Seeing certain events happen over like a frequency like um like too many calls or like how is it set up? I guess a user could configure it that if it's, if certain things are happening, you know yeah. I guess like what are the configurations that you guys are thinking of um when it comes to alerts?

A

Yeah, definitely.

B

um So things like at the most basic right, just whether a transaction against a certain contractor account, has succeeded or failed um getting a little more complex, like whether a method has been called on a contract and of um actually being alerted based on certain parameters in that method call or potentially in results, resulting data. From that method call there is on. I literally have a design doc here that I was discussing in a meeting previous test.

B

So I will I will enumerate everything to you. um I mentioned methods called, of course, events right, because events now are a first-class uh citizen in contracts and near so if a certain event uh has been logged and then, of course, for accounts really just balances right.

B

So if the balance has changed uh by a certain number or a certain percentage, um initially that'll be momentary kind of block by block like whether a single transaction has changed uh that balance, but over time uh we will be combining like the subscription to near, like with indexed data, so that you could do more advanced things.

B

Like you know, a balanced change like in that vault example like a balance change over time so, like maybe in the last you know, eight hours has the balance drained x, percentage uh things of that nature that are a little more useful for detecting like a sophisticated attack. Things like that.

A

Cool um when upgrading contracts that have already been deployed uh will redeploying also work when the data has been generated. uh Example like if nft has been minted, uh if not on what um on what would it depend for an upgrade to corrupt or how this mark how the smart contract works? Where can I learn more about upgrading smart contracts? I could actually um answer a little bit yeah when you upgrade a smart contract, you're actually replacing the contract code, not the state itself.

A

So sometimes um you may you may notice um when you're trying, you know, you're just a testing phase and you're. You know deleting a smart contract and re uploading things and then something's not working um yeah. The state is persisting. So usually you have to either clear out the the state of the contract itself like by having a method in your smart contract. uh That does that um or you know, sometimes you you have to delete the count entirely uh and then recreate it in uh in testnet but yeah. I wouldn't.

A

I wouldn't advise on doing that uh on mainnet, but yeah. So when you are upgrading your contract, you want to make sure that you are migrating. Your data, um in a certain way that is compatible uh moving forward. um There is documentation on that in near sdk to io. um I can find a link and drop it in the chat um but yeah I got you okay, you got me cool cool cool. Is there anything that you want to? uh uh Oh yeah, it looks, looks like uh uh ben also um yeah yeah.

A

I think thank you very much um anything else. You wanted to add to that. Josh.

B

uh No, I actually think you gave a more succinct description than I did initially during the demo, so yeah cool, cool cool.

A

um Will dev console provide some guided gui for the developer or up for on upgrading uh deployed smart contracts? How will it look like and where can I add, ideas.

B

Yeah, um okay, a bunch of good questions there. Yes, would definitely love to see that, because that's that's something we get questions around us and like dev tools. I get questions all the time around like upgrading contracts. How do they work? How do I get more confidence in how it works?

B

Yeah yeah so definitely we'll be building some sort of ui or helpers around that um that's very early, though we're not exactly sure like what that'll look like, but it's going to be relevant actually also just as a little insight here in the sense of the dao integration, because sputnik dao v3 is going to v3 or v4.

B

It's one of the two, the either the next or or one after uh version of sputnik dow is going to allow for upgrades like dow managed, uh contract upgrades and so surfacing that in the console is going to necessitate us like thinking a lot more about this, um so it'll definitely definitely be in there. Both apart from the dow portion and as part of that.

A

Cool so dow integration or sputnik, dao or astro dao integration of jump console uh is definitely coming uh to the to the tool.

B

Yes, yep and don't have a timeline on that, yet though, but it's definitely like yeah, we definitely do want to do it, though cool.

A

Yeah, no and and to that question yeah that would definitely make for a good user experience of okay, I'm upgrading my contract. Now I have like checklists on the side. Did you migrate your state? Here's? What your state looks like here's, what you're? You know. uh Yes, certain ways in which we can guide you through the process. So that way you can have a successful uh upgrade or migration of your contract, uh good feedback for sure um yeah and as far as like, where we can add ideas too.

A

I know we're we're doing a little bit of uh kind of posting in chat and that's what these meetings are for, but yeah as we're doing this presentation, I'm thinking, oh yeah, there's gonna be a lot more individuals that are gonna. Watch this on youtube and yeah. Definitely having links where we can have people give feedback, direct feedback and have discussions. Maybe have a poll of what you like what you don't like yeah josh, and I will talk more about that after this call and then when we upload this video.

A

Hopefully, we can have uh some sort of place where you can go and leave that direct feedback for us and have a conversation.

B

A

That would be ideal.

B

For now I I will preface this we're testing out product board right now. We're really not sure that we're going to use it, but at least for the purpose of this meeting to capture uh any ideas that anyone has and then we can always like manually, migrate them I'll put this link in here. So you can go on this product.

A

Board and this.

B

Will allow you to yeah, add suggestions um and then yeah. We can kind of chat about them in there.

A

Cool um will dove can't will dev console, allow devs to monitor gas costs for smart contract calls.

B

uh Yes, that will definitely be part of it. um We have not gone too deep on that.

B

Yet, though um I mean I'd love to even see like full on um not to mention a competitor here, but they don't they're not on the air, so it doesn't matter the tool called tenderly actually has a really cool thing: a gas profiler, I think yeah they'll show like yeah, really nice, like flame graph drill down uh into the gas usage, even if, like each individual function and operation, um so would love to even like get there at some point.

A

Yeah that'd be really cool, deploying a contract and then yeah being able to visualize and see you know where gas is going and yeah being able to profile. It definitely something yeah we've heard before I would love to. You know, love to see that cool um will dove console, create the project files on my local machine or are they created in github by default or someplace I'll? Send some server.

B

A

B

A question we're still kind of thinking through, like when I mentioned the template projects. For example, um the initial thought was probably just to keep that within the scope of github. For now so we'd either like like clone like. If it were a pre-configured template, we would just clone it uh into your account um potentially similar thing for the um the building.

B

Your own system, like not exactly sure how that would work yet, um but for now yeah it could be the path we'd probably go would be doing github just because of the additional like security concerns and things like that of accessing your local machine, um but that's not to say that that wouldn't potentially be a thing in the future. um I know like as one example and I'm totally spitballing here.

B

This is not on the roadmap, but you know, given that we have near sandbox now it would be pretty cool if you could like integrate near sandbox with uh like your local instance of it with dev console. So you could get those same benefits of like the contract forums and, seeing you know, activity and things like that. um So yeah there's definitely possibilities for local interaction.

A

Cool awesome um well we're getting just about to time, and I don't see any questions. I think we answered them all uh if you have. If anybody has any last-minute questions before we conduct the meeting or conclude the meeting, uh please feel free to post them. Otherwise, yeah we can. We could probably wrap up I'll, give a just a minute or so for anybody to post any final questions if they do have them, um but yeah. No awesome thanks.

A

So much for the presentation, josh um yeah a lot of really cool things, uh exciting things coming down with dev console, I'm excited to see it uh grow and and and develop as we're going um and yeah we'll definitely leave these calls to action uh links uh on the youtube site once we post this up, um but uh but yeah anything that you'd like to add uh before we conclude.

B

uh Just to stay tuned, I mean I know today we went through a lot of like slides and you know, um what's the word of looking for mock-ups and things like that, um but you're gonna see here at a much more rapid pace. um Yeah we'll be definitely demoing a lot of these features here uh in future meetings, so cool.

A

Awesome awesome: well, yeah! I don't see anything else coming through. So thanks so much everyone for joining thanks, josh for uh a wonderful presentation and uh update and dev console and uh yeah. We'll see you next month uh same time, uh the first thursday of the month and um yeah talk to you then yeah.

B

A