NEAR Developer Tooling Community, 5 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: DevTools Community Meeting (May '22) - JavaScript SDK

Description

This month we discuss writing smart contracts using the new JavaScript SDK (under development) and ask the community for initial feedback.

Check out an early release of the SDK:
👉 https://github.com/near/near-sdk-js

Give us your feedback and help us shape this library's future:
👉 https://github.com/near/near-sdk-js/discussions

Join the DevTools Community Meeting next month!
👉 https://near.ai/tooling-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

Welcome to the second developer tools: community update uh meeting um yeah, I'm josh from devrel. I got a couple other individuals on the call as well from the tooling team, uh yeah yeah fong. You want to introduce yourself.

B

Sure hi there guys I'm fong, I'm on the dev tools team, mostly working rust, but this time I'll be showing off a javascript cli tooling. In this presentation, awesome siri.

C

My name is sergey. I work in a deltoo teams2 and my focus for the last few months was workspaces.js and nearest dkjs yeah, and I will talk about it today too.

A

Awesome and then austin, you want to give a quick intro.

D

Yeah for sure I'm I'm austin, I'm a product manager, I'm here at pagoda on the the dev tools team as well, um and actually should I just segue right into what we're going to talk about yeah.

A

Yeah just yeah segway right in I just want to let everyone know if at any time you have any questions or comments or any ideas. Anything you want to talk about, go ahead and post it in the q a button at the bottom of your screen. Click on that throw a question out there. We will answer them as we go and then, after the presentation we'll do like an ama where you can ask anything so at any time.

A

If you want to ask a question about what we're talking about or anything tooling related, please feel free to drop it and we'll we'll do our best to answer your questions um so yeah go ahead. Take it away awesome.

D

Awesome: sweet thanks josh, so um so today, yeah we're I'm just going to quickly cover the agenda that we're going to go through. So one I'd just like to talk about what we've done since the last time. Just like a super quick uh super, quick um smattering of what we've shipped um reiterate on just what the uh the tools team vision is.

D

We had an offsite where we set that um talk about what our focus is going to be over the next uh a couple of months and then most of the time is actually going to be sergie and and fong talking about the javascript sdk, which we're obviously fired up to chat about. So um I'm gonna jump right in so since, since the last time we've shipped quite a bit- um and we we've touched almost all of the projects that our our teams take care of um so yeah.

D

Just a few highlights the sdk rs um austin, abel is, is working on um getting the 4.0 release ready to go. Hopefully that'll be next week. um So super excited um for that to go, live workspaces, rs shift a new version there 0.3 following a lot of teams working on working on that um miraculous, has been making a ton of changes to the json rpc client. A lot of cleanup a lot of ergonomic improvements.

D

um Workspaces, js you'll, see a little bit of that today, in conjunction with the sdk um just getting the workspace's js close to feature parity with rs um and making it super useful to uh to make testing um uh as easy as possible and then another one that we're really excited to share soon is has just been laying some of the groundwork around our api. um We know that that's table stakes.

D

A lot of the other chains have that already and and um we've been able to spend quite a bit of time, scoping what that would look like and just working through some of the implementation details that we're uh we're gonna take to the community so that we can make sure that we're uh we're solving the right problems. um So we've been we've been extremely busy since the last time we chatted and the other thing we did was set our vision and the way we did.

D

This was basically starting with the pagoda vision, so um just a world where today's startups and tomorrow's unicorns succeed in realizing the limitless opportunities of web3 and delivering its value to uh billions of people, and we just kind of picked this apart. We put notes on it.

D

We talked about what we liked, what we didn't like what we could actually contribute to, and we laid out on a board just the life cycle of our products, everything that we could possibly work on um all how all the tools fit together and what we ended up arriving at is a pretty simple vision of just deliver. The intuitive productive and reliable tools needed for web3 development, so the reason why I just wanted to share this is if you're wondering what our team takes care of, who we are, what we care about.

D

What we hope to achieve. This is sort of our guiding principle and our our vision cool. So um what we're actually going to be focusing on tangibly to try and make that vision come true, um the same three things that I talked about the last time we were here making near the most successful blockchain for web 2 developers, uh streamlining and improving the developer, experience for creating full stack, apps and just enabling better product uh based decision making for our tools products.

D

So um the first piece is really what we're going to spend almost the entire time today talking about- and this is our javascript sdk and workspaces js. So um I think I just might stop talking and I'm going to pass it over to sergi who's done all of the work uh with the team and beau who's who's, not here, uh because I think it's like 2 a.m.

D

For him right now, so um they're gonna, walk through um uh our series, is gonna, walk through a couple of examples and just point us to where some of the discussions are um in uh in github, so that we can get as much feedback as possible, um but yeah uh sarah's gonna walk us through some examples and really just taking a step back. This is gonna unlock a ton of brand new developers to get started, building smart contracts, so we're really excited about it huge huge priority and yeah.

D

I promise I'm actually going to stop talking now and pass it to sergi. um Let me try and share the right tab. Let me know if you can see a uh this is gonna be a little bit imperfect, but we're gonna roll with it. um Actually, let me try can. Can everyone see that screen? Okay.

A

Yes, let's create and build smart contracts with js sdk. The discussion right.

D

Amazing, and how does that you can, can everyone read that or is it.

C

A smaller text.

A

If you could bump it a little bit.

C

It's already bumped.

A

Well, that's a little bit better.

C

Okay, okay, so uh now we will try like together to understand what it takes to build a smart contract with the use of near sdk javascript. uh What you should expect like what developer experience you you should expect today and what you should expect in a month or two.

C

So right now everything is pretty simple. You can start your project just like any other javascript based project with npm with npm in it add near sdk js as a dependency.

C

And then write your code and add the build script to the packet json. We will talk about it a bit later. Also, you will need to add this config npm install yarn, build and you're done as a result of execution of this command yarn build. You will get the contract.base64 file, which is a smart contract.

C

Usually yes, if you try to develop with near, you know that the smart contract is awesome file, but not this time. This time we have like a unique enclaved architecture, so this file is actually will be deployed to another smart contract and it will be, it will work inside of that smart contract.

C

So something that you need to know is that this build process. Is it it? It consists this project like this project. It consists of two separate parts, so the first part is the sdk itself. It's uh something that you will import and use in your javascript files, and the second thing is the contract builder.

C

It's a it's a separate cli, but it's integrated inside of this dependency. So that's why you're able to do something like this yeah you you're able to execute yar near sdk, build and it will. It will convert your javascript code into the base, 64 encoded, a smart contract um also about this bible file, uh this one that you need to add. We are like doing our best to delete this step so make it a bit easier, but for now just don't forget to edit, because we are using uh babel inside of the roll up to.

C

Expand uh the decorators and yeah, so this is the experience that you will have now. Please leave a comment like this. Is the discussion on github? It's it lives in sardo inside of the near sdk, jazz discussions. Please leave your comments. If you can suggest us a better way to create projects to build projects to maybe expand adds new helper store sdk.

C

We are really happy to hear that one of the things that we are considering is that we can initialize a project with a cli command, something like near project init and it will generate you a standard npm project with dependencies with all the config files, etc, etc.

C

So the downside of this is that people will not understand what they're doing at some extent and they will get the result faster, but they can struggle later like when they will develop and build and deploy the their smart contract.

C

uh Okay. So any any comments, questions like one one.

A

Quick question someone had is: uh is there a reason that you're switching from npm to yarn when installing dependencies in building.

C

uh So there's no, you can use both npm and yarn, like uh you can instant instead of npm here you can do uh yarn, add near sdkjs and you can initialize project vdr and you can use yarn everywhere. It's not a problem, I'm personally using yarn so yeah. It should be fine.

A

Cool other than that, I don't think. Oh wait a minute. We got two questions. um Will the deployed javascript contract behave similar to wasa ones,.

C

Yeah they they are. There is some differences, so probably the main difference, and the main advantage in behavior is that since this smart contract, javascript javascript smart contract will live inside of another smart contract. All the calls uh contract uh cross-contract calls will be synchronous yeah. You know that if you try to build a contract with assembly, script or rust, you know that it's a bit hard and to make a cross-contract hole here. It will be easier.

C

I will show an example a bit later how that can be achieved and yeah so synchronous, execution of uh storage updates. This is probably the uh main, uh the the main difference, yeah. Also, of course, you will have differences on how you call these contracts, how you deploy, but we will explain it a bit later.

A

Cool uh another question is: do: is there an option to also uh deploy a wasm.

C

It is yeah, so this is. We made a decision to use this in cloud design, because if you want to deploy a javascript runtime together with the contract, it weighs a lot and you will need to pay like several dollars for each deployment and since we want to make it as easy and as cheap as possible, we are using this design, but theoretically it is possible and if you want to try it try it uh in our rip or you can check the branch that is called standalone and standalone branch is producing.

C

That was some file, so it's converting. Basically, it's converting javascript smart contracts into that awesome files, but they are like huge yeah.

A

uh One more question: is there any gas trade-off for executing inside of another contract.

C

uh Yeah yeah, of course, like you, will spend gas the same way also, if your call, for example, is increasing a number of space that your contract is using, you should attach deposit to each call, so in terms of gas and gas deposits, it will work in a similar fashion.

A

Cool, I think, that's all the questions right now. Oh someone said um this is a similar to the aurora structure. When you have a.

C

A

Executing a code in one chart correct, oh one more, it will cost. Will it cost the same amount of gas as if it was a rust contract.

C

uh To be honest, I cannot guarantee you this, but it will be similar like not much tradeoffs, no big tradeoffs.

A

um Another question came in if the keys of a javascript or jsvm account are compromised, will all the dapps that have been deployed to it also be compromised.

C

um I mean, if you're losing a key to account that you used to deploy a smart contract. Yes, you will lose the access to this smart contract. Of course, this is your only way to update it and sometimes to call it if you made such a design so yeah, you need to keep your keys safe, always.

A

Cool, I think that's uh all for right now, but yeah. um Please continue to drop questions. We will continue to answer them throughout the presentation. um What are the plans to secure, javascript, key or jsbm key? I'm not sure.

C

There's, like uh maybe the person just got it wrong a bit, so there is no such thing as the key for a smart contract.

C

uh We are using the standard keys that you used before, with your account to deploy to.

C

To jsvm to javascript virtual machine, smart contract, you need standard key from your account and you will use it for. Basically everything.

C

Other accounts will never have access to your state or to your contract, and they will be able only to call it as uh wasn't based uh smart contracts.

D

Hey siri, I think I think specifically um they're asking about the like the the account like dot near um so the what would happen.

C

D

um Do you want to go.

C

Ahead, yeah, I I I got it yeah. I got it so uh yes to be able to deploy the contract, you will need javascript contract. Yes, you can have your own contract, you can deploy it and then deploy like 10 javascript contracts to it and they will be able to interact.

C

Everything will be fine, but our idea and the design that we have in our mind on our minds is that we will have just one main gsvm, smart contracts and everybody will deploy.

C

Their smart contracts javascript smart contracts like to this contract. uh We are still trying to figure out how we will manage this key. So there is mainly there's two options, so we either deploy jsv on contract and delete all full access keys. So we will guarantee that it will be. It will never change. Yeah.

D

C

We will keep it safely, yeah, let's put it this way.

C

Probably we will move from option two to option one with time.

D

And this is a prime example of a discussion that needs to happen. um So if there, I think, is there already a github discussion for this specific topic? If not it, we should just create it asap, but obviously something we're thinking about.

C

D

Then yeah like a clear action, is um actually ben. If you don't mind creating that discussion to kickstart, us that would be fantastic.

C

Yeah, okay, any any other questions.

A

I don't see any right now, but yeah continue to drop them uh either in the chat or the q. A section and uh yeah we'll continue to answer them as we go, but yeah. If you want to continue.

C

Okay, okay, yeah! uh So now, when you have a contract, basically the result of our work is uh the contract base64 file.

C

The next thing that you probably want to do is to test it to write unit tests, integration tests to make sure that everything works, and for that we have a beautiful workspaces, jazz library that will help you to do that easily or relatively easily.

C

So workspace is just is built to be able to test all the smarter contracts for near it can test smart contra, smart contracts, written in rust in assembly script, and it can test smart contracts written in javascript, but with a few tweaks that I will talk about right now, so to be able to set up workspaces.js, you need to follow next steps like, of course, you need to install the dependency.

C

We will also install ava. We are using testrunner, eva together, we're workspaces.js and yeah. You need to create a test file, modify your package.json, you can add, you should basically add a test. Ava script, install dependencies and yeah and hit yarn test. Yeah you're done so the test file itself looks the same way. uh Looks the next way uh if you use testrunners before probably it will be not a surprise for you that there is like a before function uh where you prepare the environment.

C

There is, after where you clean the environment, and there is a your tests so to prepare the environment. What do you need to do? You need to start a local blockchain? We call it a sandbox.

C

So and you will use it, it's like your personal blockchain, it clean from the start and you can use it to deploy and hold your contracts and test test them this way.

C

So the first thing that you should understand that you need you must to deploy js vm contract if you're using base64 contracts, yeah.

D

C

This base contract this further contract uh to keep all your basics to four contracts. It's available in the nearest dkjs, so just install dependencies and deploy it.

C

Take it from this path should shouldn't be easy check our examples. If you got lost, um then you can create a few accounts. This is just standard accounts and call functions, because this is basically what you what you want to want to do.

C

Yeah so let's check some tests.

C

So here we're checking we're calling we're we're doing a view call and it looks a bit different from standard workspaces, setup, ugs contract, and then you need to encode your call with the function with the helper function b that we have up here, you can just copy it and probably will move it to some sdk or api library later uh yeah. So you need to encode these parameters, and after that, this is just a standard call to jsvm smart contract.

C

That will do all the work for you and execute your base64 javascript contract inside of it. uh So same goes for view and call functions. They're pretty similar. Try like try to read the code after this presentation and like understand how it works.

C

Yeah, so any any questions.

A

I don't think we've had any yet, but I will definitely you know.

C

If there's no questions, I will, I will think that this design is perfect and I will not work on it anymore.

C

Okay, then, maybe.

A

Someone's asking about near apijs is that updated as well.

C

No, no, it's not, unfortunately, uh so just for you to understand that near sdk just was released today three hours ago, so we're still catching up. We are adding helpers to. We will add helpers to near vhs. We already added something to near cli and we will like step by step, improve this design, because we understand this that, since it works a bit different, we need to add additional, like additional helpers, additional functions to our libraries.

A

Cool, um if we deploy a full wasm, can we use it the same as a rust contract.

C

um Not sure what what is the same as the rust but yeah.

A

There's like interaction with interacting with that automation,.

C

A

C

Yeah, it's no there's, no difference like if you're creating a contract that is bundled together with a javascript runtime, so it's a wasson contract, you're deploying it, and after this this is just a standard contract for you yeah. So the interface is the same. The possibilities is the same, uh no limitations you can track transaction and explorer et cetera, et cetera. You can do cross-contract calls to other contracts that are written in rust, which is not possible from a base64 contract. For now,.

A

Cool, um how are you going to be able to call other contracts and other shards.

C

Good question good question: we will not call other contracts on other shirts because all the smart contracts are deployed to one smart contract and this smart contract always in one chart, maybe not the same chart, but it doesn't matter like it means that all your enclaved smart contracts are always inside of the this main smart contract. So sharding will not stop us here but, as I said, we cannot right now make calls to rust-based contracts from enclave to contract.

A

So once you're inside that enclave, once you're deployed inside there you're in your own little universe, and you cannot communicate with.

C

This world yeah yeah- I mean you can but not not the same way. You cannot make cross-contract calls. So this is the rule for now gotcha.

A

um Can you use oracles.

C

If they're deployed to I mean oracle, suggests a smart contract right, so if these smart contracts are js-based smart contracts that will be deployed in this enclave, then yes, cool, yeah,.

B

C

My my recommendation will be like if you don't want to learn rust. If you don't know rest and you don't want to learn it, and you want to just start quick.

C

This is what you it should do like javascript you can, but you should keep in mind that probably you will need to write all the smart contracts in javascript, so you will need to write all the logic and just check that everything everything you need is available inside of the enclaved smart contract as an oracle, for example,.

A

A couple questions about workspaces: um are there utils for workspaces.

C

Deals not sure like there is no it's a single package now uh I know that we are trying to extend it, but basically, what you can see here is the utils is utils uh like these functions. It's not in your api.js functions right now, at least this is the utils that workspaces jazz is providing for you to make these test files small and like easy to write.

A

Cool um will epoch skipping be introduced in workspaces.

C

A

Epoch skipping so like skipping forward. I would imagine like a fast forward.

C

uh I'm not sure, I'm not sure, maybe somewhat if somebody knows answer or we can do that after the call.

D

The goal is to definitely have feature parity between workspaces, js and rs. um It's just a like a resource question right like um just our. We have so many priorities. As everyone knows, um it just may not be the the next most immediate thing that we work on, but it's definitely on the roadmap.

A

Oh another question: is there any negative side effects to using the standalone version of the sdk rather than uh the price, I'm assuming they're saying what? What aside from the size of the contract when you deploy it, you know wasm directly is.

C

There any other.

A

Yeah is there any other uh downfall or negative okay, so yeah the.

C

Size is the first one, the inability to call contracts outside of uh just virtual machine smart contract also, no.

A

I I think what they're saying is, if you, if you, if you uh compile it to wasm and you just deploy.

D

A

D

Yeah yeah yeah.

A

Well, you know, aside from the size of being huge, you got to pay for that storage. What other I mean at.

C

That point it's just a regular.

C

There is no limitation limitations, so I guess that the main limitations right now will be the fact that uh this javascript sdk is not mature, we're just releasing it so right now it lacks some functionality that rust sdk, for example, has so during development. You can face some limitations, but after you've deployed it. I don't think so.

D

Can I just even ask like sarah for, like clarification on that so like for someone that does want to um use an oracle, have cross-contract calls if they just uh generate a wasm file from a contract they build using the javascript sdk, they would still be able to do that. But what you are suggesting is that um the not every single tool or every um like all the bells and whistles from the russ sdk, are available to the developer. To make that as easy as possible. Right.

C

Now, yes, right now there are some limitations, but, yes, you will be able to use oracle's. Do the cross-contract calls everything that rust? Smart control can do yeah, so maybe we will with time we will have both that you will be able to.

C

Build a dot, base64 contract and that wasn't contract and decide like what? What what kind of experience you need, what kind of functionality you need yeah, and I will remind I- will tell it one more time that it's already available. If you will go to the repo check out the standalone branch.

C

It can it can do it, it can make that awesome. Smart contract.

A

um How do you know what contracts or apis are available in the enclave.

C

All the apis, like we have all the apis that are available for javascript for sorry for rust, smart contract, basically we're using everything that is available on our blockchain.

B

When I'm saying.

C

That there's, when I'm saying that there are some limitations in apis, it means not the low-level apis. I mean the high-level apis, some helpers that, like making your life easier.

A

Cool and then um I I think the second part to that question- is um there's no like list of all of the smart contracts that have been deployed to the enclave that you can interact with correct or concurrently, correct.

C

uh There is, there is okay.

C

You can do that, okay, so just a something. You need to understand that this is a jsvm smart contract account is a standard account gs, vm contract is a standard contract and it has its state, and this state is divided between the contracts that are deployed to it.

C

So you can get with the view function of this jsvm smart contract. You could get a list of all the smart contracts that are deployed and you can check the state and right now the state is in json, so you can even view this state.

A

Okay, cool, okay! Let me let yeah let us know if that uh clarifies or answers your question or if you have any clarifi clarifying follow-ups. um Another question: are there any limitations to using external npm packages, I.e random numbers uh in russ? You can only use crates that support the wasm 32 unknown unknown.

C

Yeah yeah, so you can use external packages no problem, but they should not depend on something that is browser specific or note specific.

C

So, basically, everything that is pure js should be able to work in your smart contract, which is a huge advantage because in assembly script you do not have a lot of options a lot of dependencies. You don't have like a million packages in npmjs that you can use so yeah. It's a big advantage and try to use it. There is an example in examples: folder near sdkjs, examples folder, that is using an external dependency.

A

Well, they followed up with just making sure that this is the same between the standalone uh and the enclave version. Correct.

C

The same, what do you mean the same.

A

The the mpm packages you can use them in the enclave as well.

C

Yeah, no, no limitations, no difference, no difference.

A

How does this javascript sdk compare to the assembly script, sdk pros and cons.

C

Okay, so I'll yeah so pros and cons, I've told I've already told that in assembly scripts, basically, the situation is the same. You can use external dependency, but only if they are written in assembly script. There's no, not that much such libraries in javascript. You have everything you need.

C

Assembly script is a language that is still in development, that that is why, uh next to like in our documentation, we are saying that assembly script is not ready for financial applications and javascript theoretically can be yeah like if we will pass some security checks. I guess that it's theoretically possible, because this is a mature language that is used widely used.

C

Also javascript is probably easier and it's just more spreads. Yeah more people know js. This is the reason why they will want to use it. I hope so.

A

Cool, I have one clarifying question.

A

What I meant is, for example, being you can't call ref finance from the contract. You would probably need to deploy a dex to this javascript smart contract. Is there going to be a list of contract deployed there that you can call in sync.

C

So if I understand this right- yes, yes, you will not be able to do that, but.

C

You can you will be able to do that if you will package it as that awesome.

C

Yeah by the way, we really want to hear your thoughts on what's the best design and which one we should develop more intensively like the standalone design, where you have that was on contract that is big and expensive to deploy, but it's more functional or they're, just a smart contract that is li-fi cheap, but has some limitations.

C

Please leave comments in these discussions that we are showing here uh in near sdk, jazz, repo.

D

Cool awesome, I'm just conscious of time. We've got 15 minutes left. Should we take.

C

D

C

Yeah yeah: let's, uh let's check the example and.

C

Yeah and after that, we'll do it okay, so I have a few projects here. So the first one is the status message project project now we'll explore it briefly, because basically I've told everything, but maybe you will want to see it in like in real real life.

C

Okay, can you can you see the text, the code.

A

Yep, oh, I can only see I can see your uh nav on the left, but I can't see any code on the right.

C

Oh, never because there is no any code: okay, no yeah! There we go there we go now. It should be really good okay. So this is the project. It's pretty simple! It's a standard. As I said, it's standard.js project in package.json.

C

All we've done is: we've added the dependency for near sdkjs dependency, dev dependencies for our testing libraries near workspaces, of course, and we've added two scripts near sdk, build and ava for testing our smart smart contract is pretty small and easy. So all you need here is a nearby engine hole and few decorators, and basically everything else is a plain javascript code. Maybe there is also an environment to do logs and maybe some other low-level stuff.

C

If you need, if you will need it, so this smart contract is pretty simple, it has records records, are I can be set by the caller and basically every caller can set a message status message for itself and read this message. Of course you can read this message by with get status function and the account id so yeah looks pretty simple to me.

C

Any any questions about code.

A

Someone asks so there's no more signed, unsigned integers. I need to import.

C

uh If I'm not mistaken, no, no, this is like all you need. Okay, um yeah and uh okay. Here is a yeah. Here is a sorry yeah, here's a build, folder right and after after you execute yarn and your sdk build, uh you will get these files, so this base 64 file is your smart contract ready for deployment, and this file is basically expanded version of it expanded version of what we saw. Sometimes you need it to just. You know to understand better what you wrote yeah, so we will know where to check it.

C

Okay, any other questions.

A

Yeah someone asked if they can write their contracts and typescript and then precompile to js.

C

uh Now, theoretically, no limitations- we do not have examples yet, but we are planning to add typescript support yeah, but you you can try if you, basically, if you will be able to convert, compile. Basically your typescript file to this, like no limitations.

A

And then I think some someone was asking if there's any smart contract examples with logging and nested con cross-contract calls.

C

Okay, yes, yes, there is, I will show it right now, because this is the plan.

C

So we have an example like the simplest example possible of the smart contract across smart, smart controller poll.

C

It has the same structure, nothing like really.

C

Different, we added a ready status message: base64 contract from previous example, so we will use it and we have our on-call contract here. So the idea is that on call contract, we'll check the status of the status contract for the person and then, if this person is available, so it's it's done here like we are doing a call to a status message test that here.

C

If the status is available, then we're setting this person on call. If it's not we're, not we're not setting this person on call and also we can check who's in a call right now. So this is the example. The simplest example of the cross contract call inside of the js smart contract.

C

It's also available in examples. Folder there you can, you can check it there and you can play with it, improve it. Write, pull requests. Add new examples, write your awesome projects, everything you want.

A

Cool looks clean, someone says.

C

Yeah yeah, javascript, simple and hopefully reliable.

C

Okay. So that's it from me the next that the next thing that we want to talk about is how you can interact with enclaved javascript, smart contracts from the cli and fong who's. The author of this functionality will tell more.

B

Yeah sure, um let me steal your screen first for now,.

B

All right, can you guys see my screen, yeah yeah, all right so yeah, so this will just be. This. Is the discussion board for um how you interact with the js smart contract through the cli? uh We currently have like five um commands that you can use that are specific to just js itself.

B

um Yeah like uh I'll, go through an example later with this, too, with uh what sir he did with like the status message, but uh yeah these will be just like uh regular calls into the jsbm and they will have some. I mean these are just like helper stuff on the cli itself, so you don't have to make some raw calls um that you normally have to do.

B

So. Let me show you how that all looks like in a workflow like manner for deploying to deploying a uh status message contract to the jsbm, so uh normally you just have near um when you're.

A

Actually trying to get larger phone larger, okay, yeah! Thank you all right. Let me see perfect things.

B

Yeah there we go so normally you just have near, and that would just be your entryway to go through every single sub command, but for the javascript one we need to specifically go into js, because it has a bunch of other parameters that need to be specified than what you normally have in the regular near cli.

B

So to deploy the status message contract we just do deploy and then specify the account we want to associate the contract to on in the enclave, and we just specify that with account id, uh then we should specify the path to the file it's or to the contract bytes itself, which is the status message. Dot base64.

B

uh one additional thing with deploy is that you do need to allocate a certain amount of balance to the enclave so that it could store this contract itself. So you have to do deposit and then specify 0.1 near it's not going to take up 0.1 here.

B

It will refund the difference that it ends up using so that, let's run that, and it will also give you back the transaction- and you can view that in the explorer um then we'll make a call into a net itself, and this is my account and it's and and it doesn't take any arguments so we'll just call that let's specify the signer, which is just give me a test and test user test net again um calls also modify state.

B

So that means that we also need to specify a deposit so that if it ends up taking more state on the enclave itself, you can actually allocate it properly.

B

So that should run and afterwards we should be able to set a status onto the contract itself and yeah okay. So, let's set hello world to it. So let's specify contract and then set status, then we'll want to specify our signer yet again.

B

Then the arguments to it- this is just gonna, be a json um arguments like you'd normally get with hello with um with near cli call so we're just gonna specify uh hello world and yet again, since we're modifying state, we need a specified deposit.

B

Cool cool and once that done well, we should be able to view it and get back hello world.

A

One thing I noticed that's a little different in this- is that you're passing an array instead of an object or a json object.

B

Oh, no, it's just uh that's just how the the parameter is set in the in the contract itself, but you can pass in a json object itself. If you wanted to oh okay cool, it's just any json string.

B

So let's call into view itself and then get status and specified account.

B

And then we'll specify, um yeah the the arguments or which, which um status message uh account we want to grab from so it's just gonna, be this one and we don't need a specified deposit, since this is just a view, call yeah, and that gets us hello world that we set before and now uh once that's all done. Let's say you don't want that contract to be live anymore. Well, you can just do you can just remove it itself and it will return you, the any deposit it has um it has.

B

uh It has on the enclave itself, so you'll receive back all your storage deposit.

B

Now, um as you can see right here, it's using this particular contract for the jsvm, but that's just the default um for testnet. If you want to specify your own jis vm contract that you deployed to some other account, you can do, let's say, or you just had this. Let's say you can just specify like jsvm and, like your own jsbm contract account like testuser.testnet, if I deployed on jsvm contractor.

B

So all this is like pretty much built in already if you just want to use jsvm.testnet instead and later on, jsvm.near, if you want to go on mainnet but yeah. Besides that, that's pretty much it! Let me know if you guys have any questions on that.

A

I think jacob only had one it was kind of like a follow-up question I had. um The arguments are not named like they are with rust, ban assembly script contracts. I think it's in that same kind of format of like key value.

A

B

All right, um I believe that you should be able to specify key value. Correct me if I'm wrong. Siri like uh it should just be like a json um set of parameters and like the jsvm contract, should be able to parse it itself and apply it to the.

C

Yeah, it should be possible yeah.

B

But, like uh I mean even uh in the rust um when you're calling us a rust smart contract, you don't necessarily need to specify the named args for um this for the yeah, the name argus into the callable itself. So it should roughly work the same like they're um yeah. They should be like pretty much serialized the same and like uh be sent to the proper smart contract call or function.

A

Cool um looks like javascript deployment is only a function, call to the javascript virtual machine contract. Does that mean that one account id could conceivably have contracts deployed on multiple jsvm instances simultaneously.

B

uh Yes, it should be possible like um by multiple jsvm instances, you mean, like multiple jsbm contracts deployed to the chain, then yeah yeah, it's uh it's just the account id is associated inside the enclave itself. So you, your local account that you have like test user.testnet that won't that won't actually store any of the contract. Bytes.

A

Cool um this is an interesting question, so the 30 gas fees that are earned by depth developers um are usually sent to the contract. Owners um is for the javascript vm. Is that going to be sent to the jsvm account or are they stored on the jsvm account? And then the jsvm smart contract has like a data container that keeps track of how much near and what accounts on which uh yeah? I don't know how you guys thought about that at all.

B

C

Yeah, I guess not for now yeah, but it's a really good suggestion, yeah, it's something that user wants to get and needs to get.

A

Cool awesome, thanks for thanks for flagging that issue. um Yeah plea, please, post, that in the discussion on github, so we don't lose that.

D

I was definitely gonna say: can I ask you to create a discussion around that, so we don't lose that thought and just like, echoing that this is like version 0.1.

D

So a lot of this is probably if we have a massive amount of usage, obviously something that would probably be prioritized so, um but please open the discussion now. Thank you.

A

Cool all right: well, we got two minutes left. Did we cover everything that we we wanted to get to on uh uh on your side, austin and sergey and phong.

C

I'm good austin. I.

D

Think so all I was gonna plug at the end was just what we're focusing on immediately. So it's obviously this javascript sdk getting this out the door. um Workspaces, rs 4.0, expect to see something uh expect to see a release come very soon next week, hopefully, um and then focusing on the on the api as well.

D

um So uh I think that's it I'd love to just say a huge thank you to sergey and bo who's, not here for a ton of work on this javascript sdk to get it to where it is and and and fong. Thank you for jumping in and uh putting your javascript ad on with the with the cli work, uh to get the interaction working so um yeah massive.

D

Thank you to the entire team and and a huge huge thank you to the community um for these amazing questions with a new like a new product where a new tool, um we definitely expected a lot of discussion and- and you all didn't disappoint. So just another reminder continue to have these discussions in github we're going to try and have all of our discussions in github um and uh we'll try to improve this and super excited to see what everyone builds.

A

Yeah totally, thank you so much everyone for uh for joining again continue. The conversation on github, please give us feedback, show us examples of things. You've made ways in which we can improve uh yeah. We are basically guiding our development process on community feedback, so please participate and help us uh shape our future, um but yeah thanks. So much fong, sergey austin, uh yeah love. uh I love this discussion uh and uh yeah, I'm stoked about the javascript sdk and where I can go from here, so uh cool.

C

A

Share with your web two friends, absolutely absolutely uh cool. Well, have a great day. Everyone we'll see you next time bye, see you guys.