Tools Community Call #2 - near/dev/hub

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

1. 0:00

   ecosystem uh today we are joined by y or soon we will be joined by y who is going to give us a lightning presentation on lava for those of who don't know uh this aims TOA aims to help scale the RPC servic and demand for uh we are also Jo by fro um with update on the SDK and the CLI um un fortunately luk from near blocks won't be able to make to the call but he provide some updates which I'll be sharing with you

2. 0:30

   uh Andre from sour scan D from Pik speak and Z from JSO and also we are joined by and his team who are going to be uh talking on near API JS so without further Ado uh we can start um since Y is uh having difficulties so joining this call I suggest that we start uh with are you okay ah if you want me to start I can still start okay then so yep you you can start on your lightning

3. 1:06

   presentation on network yeah thanks um yeah hi everyone I'm yal I'm leading Partnerships with lava specifically I'm leading the um Lava partnership with New Foundation uh so nice to meet you I think I've been chatting to I've been slowly getting to know the ecosystem so I've been kind of reaching out to people and uh getting to see all of the amazing stuff that people are building on near uh slowly but surely so it's very exciting to be here

4. 1:38

   I actually um didn't this this was all very last minute so I didn't um prepare anything but generally what lava does is uh it's essentially based on a cosmos um SDK uh L1 chain and what it does it enables uh to create an open market for blockchain data so the most um basic use case is for RPC then it becomes more and more complex with more advanced apis index Sals oracles Rel layers um Etc So currently we've been uh working with the

5. 2:14

   near Foundation to uh kind of uh improve the developer and user experience uh of RPC uh in the near uh Community I've been seeing that you know um there is some room for movement from you know a speaking with developers and um uh yeah getting more involved with the community and basically what we're doing is we're creating a new public endpoint which will uh allow anyone to start very fast to get started with near and get access

6. 2:44

   to the blockchain uh but essentially it's not based on any single RPC provider uh it's based on multiple RPC providers and the best ones in the ecosystem so that's you know Pagoda chain stack no drill and uh we have multiple other partners um that are joining as well and we also have a very large community of node Runners so essentially this end point thank you let me actually post if I have another minute I'll just show you like how how it looks but essentially it's any other

7. 3:16

   endpoint that you guys know but behind the scenes it will connect you to multiple providers rather than a single provider so that will allow you to have automatic fallback so if one provider is down uh your app doesn't need to go down um and also it allows for cross referencing data so the data is more accurate um and consistent um and yeah that's that's the gist of it um I've sent you the link to the Gateway I just want to show you kind of how it works but essentially you can

8. 3:50

   use lava either on the public endpoint which is just an endpoint or you can sign up to the Gateway which I'm presenting now and essentially this allows you to get uh the same RPC um but with higher rate limits and we can also customize the rate limits for you guys if you need any um spatial uh requirements um and essentially you can get RPC for both testet and mainnet we also have um Lava SDK which is a very exciting project which allows you to plug into providers on the network

9. 4:33

   without going through any kind of server that that is run by lava itself or any kind of of uh service so basically to be totally self-reliant uh with complete um peer-to-peer access with RPC providers um I don't want to talk too much because you said five minutes um but I think that's it we will have archive data supported very soon and I encourage everyone to check out the Gateway we are going to launch officially next week and we are working

10. 5:07

    with a few uh of the guys here and other dabs to uh you know make this a successful launch and bring more people to the gate to the you know to the lava end point um essentially diversify the RPC ecosystem of near if anyone has any questions uh the best way would just to DM me via uh telegram I'll send here my handle amazing yeah thanks for for the brief introduction to to Lava RPC so uh

11. 5:44

    for those of you uh I we put some chats uh who didn't see we put some links into the chat window or you can directly uh contact on telegram or also in our Telegram group uh near toos uh which I'll be giving the link later on uh so yeah awesome that's I was playing around a little bit with lava I'm quite excited because I see that uh it will be in general it's quite hard to get uh uh get to know about the existing VPC providers

12. 6:18

    because we rely at the moment for the documentation to be updated in order for people to see it and you have to switch and like services like lava and pretty much you have a one Gateway and then lava takes care of the rest so thanks I I really really hope that you have a successful lunch and I'm excited about your service all right so I guess we I guess we can continue with fro who is going to give us updates on the sdks and the CI Pro are you

13. 6:54

    ready yeah hey everybody let me share the screen so we can immediately start with fun part um M sure all right uh I would't be able to see the chat so let me know if there are any question there can you see my screen now yes I will awesome so well uh today I want to actually talk about like the whole Ras stack in terms of the dev tools on here and I will unpack it today what what I mean by it um um a little

14. 7:30

    bit like for those who may have not meet me uh even though I'm very active in our community I'm FR and I'm building Dev Hub together with all of you and I joined near back in 2019 and by the way I use Arch and I love near and rust so this is where we can I think align so if we would uh jump right into the topic of uh development on near I feel like this is the very simplified version of developer Journey uh so there

15. 8:07

    is a up developer who is coming to New ecosystem and they are thinking about building something that either needs a frontend some UI uh and then they would go to choose some front end stack available in near um it it could be boss components it could be classical uh react GS uh any other front endend framework really uh near PS is rocking these days uh and U otherwise if they are into building um the backend part sort of um

16. 8:44

    they would need to choose the language first um because on near we have um web assembly runtime on the protocal level which means we can basically use any language uh really but um rust is uh one of the most loved languages so today we will talk about R Tech um and without further Ado let me uh dive into it and show how like what are the pieces and where um how it all fits together um I'm not sure if we will

17. 9:22

    have another uh talk today about this stuff that I will show you but it since it's at least I'm not uh up to date Let Me Maybe picture you some of the um latest uh and soon becoming uh the default way to to to deal with the rust stack on year hopefully and to do that I suggest we start with this repo which is carer new project template which is not um so it it was originally uh created as is a just a template that you can clone and fork

18. 10:04

    and give it a try there are some useful links and there is carger extension which is the first one we we will talk about today um if you're familiar with rust you you will be familiar with Caro car is awesome um Dev tool in near in rasti system uh to simplify building testing of your project and carger is this extension that does even more so it allows you to basically have this carger

19. 10:34

    build uh carger API if you want to do it uh car near create Dev account on testnet as a stand on command and deploy so you don't even need to uh think about it too much but let me uh actually show the the exciting part even more exciting part about it is that with a GitHub they actually have this nice feature of code spaces uh that you can launch a code right from the browser you don't need to

20. 11:08

    install anything locally you just uh click the button and you have a full remote uh environment available to you nice um with this project that we just saw um and if you would uh so in Ideal World we would start immediately with carger build uh we're not there yet uh in fact we don't have even carg here so in today world we go and install rust hello so you just go to rust up regular flow how you would do it um and install

21. 11:59

    actually I also realize that we can use table channel here instead of pin version of rust and also we will need to install carger so if we go to carer and well I just tested it the most recent two releases do not work in in this environment let's pick the the previous one and install here boom so now we have rust and carger installed here and we need to restart the uh shell so it picks up or or or Source the N we

22. 12:49

    can Source n and now we have cargo okay yeah it it actually also installed VM runtime for us VM Target um and carer nice so what's next so well we can immediately start with carger so it's if you were familiar with uh other clis in Rust they are all interactive and um helpful so we don't even need to um type down the whole command there and we can start with creating Dev account so let's create a Dev account use a random account ID for it

23. 13:38

    enter um wait a little bit U for it to check which account names are available and hopefully soon yeah it offers us to also autogenerate a new keyp for this account uh I will save the access key in the Legacy key key chain because there is no system keychain inside this virtual environment we'll probably need to smooth this user experience for the future and it's going to be testet

24. 14:10

    account obviously um and we creating it so with this simple flow we already have our um testet account in a moment and we can start with car near build um while we're speaking it will be building dependencies um let me close it for now and just walk you through what's inside this project basically so well we'll we'll start with readme RM is um pretty short and sweet uh you can test

25. 14:52

    the contract you can build it you can deploy it uh right from from here and there are plenty of useful documentation resources um the source code of it is a standard U set um set status message uh contract with some unit test um I believe here and with some um end to endend um integration testing here with near work work spaces which compiles the the whole contract and interact with it so

26. 15:29

    um the thing that I want to point out is basically there are several things in play here um the next step after the CLI part is basically the SDK uh which you probably is familiar about with and the and near workspaces it's a endtoend testing framework and with this and these two basically compile compile a lot of other small nice dependencies internally uh which allow us to build these sandboxed environments um for local testing so we

27. 16:09

    don't even need to use test net for testing the contract we can uh simulate everything locally and the yeah the SDK itself is pretty neat and Polished and the 5.0 release makes even more a nice patches there so with the status here almost done um yeah so this the this is the um developer experience part but there is also another CLI which you may have also seen but I'm I think

28. 16:55

    it's it's nice to always see in action um it's near CLI RS which is also uh which is more general purpose CLI for near ecosystem if you go to releases uh you can pick any any of the versions I believe unfortunately the this in this environment that I'm testing I need to go and grab some older version for it to be installable inside this envir M on regular Linux box and regular um Mac OS Windows it works fine just

29. 17:37

    something specific about this environment that I will investigate further um yeah so this is this was the whole installation um it's already installed and you can use near command to interact with you can view help if you are into typing it out or you can uh just go in into near um command hit enter and interact with this nice um way so and what what we will probably do um let's check out what would the account oh okay it's compiled now uh

30. 18:17

    what was the account that was created for us uh what create create create create create new account redundant chin okay let it be and I I'd like to view the um this account summary actually it it has autoc completion based on recent interactions so I I I actually didn't need to copy paste it and let's just view okay it has five near um already on the balance it has one full access key and there is no contract code there yet so let's do car near

31. 19:09

    deploy where we want to deploy to this account uh it will recompile it just to be on the safe side um we don't need to have any insallation function calling and it's test net yes and we are signing from Legacy keychain send boom so this will deploy the C code to the chain no magical shinig Gans hopefully transaction doesn't exist interesting I think it it was still submitted it just failed to no contract Cod okay let's try once

32. 19:59

    again and the nice nice part is that you can always just copy paste the full command from here you don't need to always go through the interactive mode you can even cut it in in in the middle and use part of the command and if you want to replay it only partially uh BL one question that we have in the chat is do we have any release date for uh the r K5 not like it it is all these all these

33. 20:35

    uh paper cuts are currently being fixed and as soon as we like we we go through this experience end to end with no hiccups uh it will be released hopefully in like next week two and that's all yeah uh so I don't want to take any longer time uh I will investigate what's going on here the overall um experience I think is more or less clear so as I said like I can cut it this command in any at any point and it will just interactively ask me for the missing bits of the

34. 21:14

    command um oh actually it was deployed I don't know what's going on with testnet right now uh yeah we actually had the suggestion from Noah that he spends about three minutes to see to present like four is it four uh three minutes to actually see how simplified is now how simplified now the dayf container is is that correct now nice yep y sorry for taking but it's I it's I still think it's uh cool to see how it works underneath but it would be definitely

35. 21:48

    great to see how it's improved uh with your help uh so yeah and last last thing that I just wanted to show is how to call a function we we are selecting that we are interacting with the contract we want to call a function read only on our contract and it's get status uh function we passing parameters say Json so get status receives account ID well it doesn't really matter account ID we didn't get we didn't set anything there yet so it will be just return an

36. 22:22

    empty result but yeah now but the nice part is this we can always copy paste it boom we have this result um yeah thanks for uh listening in and uh once again it's it's being only possible uh because we had a lot of people contributing to this whole experience end to end from near workspaces nearest dek near CLI so I invite those who are interested in contributing to this tooling to join through uh near devhub work there is a fellowship program where you can find

37. 23:06

    those who are who can guide you to contribute to docs to tooling um yeah that's all from side awesome thanks Ro and another question that we have from the chat is do you envision the complete division of the JS and the rust Tools in example rust devs use go and the jsd use no npn like how would yeah so ideally uh the developers of respective platform is using are using their like native tooling so I expect R the devs would use

38. 23:42

    Caro extension while GS developers would use something from npx or um yes some some of that experience U but uh some of the tools like near CLI RS could be Universal and it doesn't need to be dependent on the stack of developer but other like car near New it doesn't make any sense to be built uh for um like GS world I hope yeah that makes sense awesome uh thanks very much for uh Noah are you ready to present this is a very last minute actually it happens right

39. 24:23

    now live for all of us so no is going to present how the dev container is simplified so this is something that you have been working on currently under Dev Hub I believe or yeah so in short uh I got a grant uh it hasn't it was confirmed like last week and I started work a bit early because I had some free time um so the grant is to implement a Dev container which can be reused for all near rust

40. 24:55

    projects uh and uh in that I came across a few hurdles uh namely the fact that some of the tooling for Dev containers was a bit under maintained so I had to contribute to a few other minor projects for Dev containers and Dev container features but the final decision was to to write a Dev container which is like the base for for everything uh which is just a more or less a Docker file um

41. 25:25

    that installs rust okay and uh also additional packages that are needed so if you were if you were doing this and if you try to build maybe something more advanced or maybe in uh installing cargo near from Source uh you would face some problems so when you pull up code spaces like you did you run what's called a universal image which has a lot of stuff installed in it a lot of different developer libraries

42. 25:55

    Etc so it's a bit heavier uh then what one may use in a more like if they're only trying to do one thing which is rust development and Dev containers are all about being more specific so in short I'm building a container for rust I'm adding the lib udev Library which I found was needed because of uh hia crate which is a cargo near dependency uh I'm uh building a Dev container from that as well as adding some common utils

43. 26:31

    uh I'm adding cargo B install to speed up installations of any cargo packages uh I'm adding git because you're going to need git right uh which come by default in code spaces but uh since this is a general Dev container uh I found it useful rust this is the feature I had to fix so llvm uh for anything Advanced and this is thinking ahead with like um wasn't have Grant in mind I'm going to need llbm so I'm just putting in llbm

44. 27:04

    right now because you know I'm going to need to do work on this feature anyway uh to get it everything working and also write wrote a custom feature for cargo near which is defined here so this is the dev container feature for cargo near which depends on Rust and be install and it installs cargo near uh directly that's pretty much it no options nothing for now and uh hopefully it will be deployed to maybe a repo I need to I

45. 27:36

    need to see where I would put it so there is a Dev containers Community or I could put it under near protocol as a repo uh these are all options uh that you know I just need an executive decision later on um and you may have noticed I'm I'm in vs code right now and what you probably didn't notice was was that I'm actually in the dev container right now so this is a Dev container we're running here uh literally a minute ago I built it and uh

46. 28:07

    right now it supports cargo near it supports cargo build uh whatever you want everything's working fine and you could honestly start using it right now uh but the stuff I need to do is I need to maybe publish this feature uh to the GitHub container Repository uh for cargo near and I I need to see where I want to put this whole Dev container definition because right now it's in the cargo near new project and it may make sense to put it somewhere

47. 28:39

    else uh other than that you know it's it's honestly working you can use it if you want I can send code to individuals I'm just not ready for like a public release yet yeah that's it Tre minutes up all right amazing thanks a lot Noah uh yeah so as as earlier mentioned unfortunately look from uh near blocks is not going to be able to make it to today's course but uh he briefly provided few um yeah few um updates and one of them actually is

48. 29:18

    that they're almost close to releasing the entire near blocks as far as I understood on boss so we I'm going to drop the the link into the call so basically you can go Beta dock.io And so they're close to releasing the the entire Explorer I believe on boss which is amazing um they're still addressing remaining uh feedback issues like holders and which some of them are slow to update as he by

49. 29:49

    his words is every 24 hours and basically uh yeah they are still looking for feedback and if you want to reach them you can do so on our public channels be it in the near death telegram group or the two links but they're widely available uh and yeah for the remaining like or at least for what they're planning to work on I'm going to drop you can actually see their post on uh def cup so on your social so I am putting this link in the begin into the

50. 30:22

    chat and yeah this would be the very uh fast and brief updates from uh from near blocks so we also are having on the call Andre from Source scan uh Andre are you around hello everyone sh up yeah so uh the next updates and the presentation we'll get is from Source scan so go ahead okay so hello everyone and today I would like to talk a little bit about our project Source scan which is a near native wasm smart contract code verifier uh so why did we start building this

51. 31:03

    project at all in the first place uh we really believe that such technology uh that is a common thing among all the blockchains eliminates the need of facing Black Box contracts enhances developer onboarding experience allows trustless Anonymous creations of smart contracts improves robustness and security of the blockchain and also enables cisem participants to detect fraud before it is too late and uh in the past three months we have been

52. 31:35

    working on the uh on some features that would improve our first approach that has some drawbacks and today I would like to focus on uh such features as wasm reproducibility across uh the client site and uh server s side also you don't need to uh provide the full access key for us to verify the smart contract now also we implemented the contract code viewer and we started to work on the contract reputation system let's head to

53. 32:08

    the demo uh here I have some example project that was prepared for this presentation uh it's a simple rust smart contract uh but I will be building it not in a simple way I have a special script Builder uh which uh this script will will uh pull the latest contract Builder image and uh it will create a container with this image and uh Mount the hosts folder that we're currently working with into the reproducible environment so uh with I

54. 32:41

    option you can uh specify any uh reproducible image you would like to use for the compilation and this air option uh you would uh you can specify the comment you're going to execute I will be executing the deal Dosa it's common uh R compilation script and as you can see the co the container was created and the um the host environment was mounted inside of it and right now it is building into the folder of the host and

55. 33:14

    uh this so the CPU architecture affects the reproducibility of FM so that's why can you see my screen yes we can okay sorry uh so yeah it affects the reproducibility of FM so that's why we use only MD 64 images but as you can see I'm on Mac that has M2 Chip its arm and under the CPU emulation there are no any no problems to compile like that so uh we have an output BM here now I will just simply use a near CLI RS to deploy the smart contract to

56. 33:55

    the newly created account uh yes and it was deployed uh now I need the name now I will go to the uh boss app uh of source cam we need to go to verify page here we need to specify the name of the smart contract then I will choose the GitHub repo that I was using uh then I would need to choose the uh branch and commit uh the entry point and also we have here two options the alt option

57. 34:31

    where you can um verify and deploy through the full access key and the new Option with a dock for image U so here you can uh copy the digest of the uh image that is currently used on the compilation server here you press this button to be able to verify this tutorial uh has the steps that we have done in the start of the demo also you can optionally upload to ipfs and I press verify and right now on the remote compilation

58. 34:59

    server the uh same commit is being compiled in the same uh container using the same Docker image and as you can see contract was verified successfully I haven't used any full access keys or so I'm on the different account here I haven't signed any transaction now I will go to the scan page to see the new smart contract and here is the new smart contract I will go to show more uh so

59. 35:26

    here you can see this code hash of the smart contract I also have a special script that can uh provide us with the code hash of a local was file let's do so and compare it so as you can see the code hash is the same so I was able to reproduce the same uh wasm on my server the same as I did on the client side also we we are storing the Builder image here so even when uh when few

60. 35:58

    years would pass it would it would be possible to uh recompile the same project uh having the exact commit having the entry point and Builder image of the environment uh to have the same code hash also we have the ability to uh view source code uh by GitHub which is yes and by default it open op sleep.

61. 36:24

    RS also we have a special code use that is fetching the code directly from ipfs uh also we have the social features of the smart contracts such as upwards Down vs um this would affect its reputation in the future also you can leave a comment uh here so let's do so and as you can see one comment has has appeared and we can also upload and download comments and based on the uploads and downloads comments are

62. 37:02

    displayed differently on the page so that was it with the demo let's take a look a little bit uh on the technical side verification so first of all uh in the C uh we compiles the smart contract in a reproducible environment then deploys it to New blockchain using any tool we want then in Boss app uh we are access ing The Source con IP to clone the repo check out the commit and request the compilation and verification of the code on the server side uh it

63. 37:35

    clones and it closes the repo in the temp folder uh that will be available only for 10 minutes then it compiles uh the this folder uh in the container using the same Docker image as client then it compares the check sum of local VM that has just been compiled and the code hash that is on chain so if check some matches it adds this contract to the verified contracts in our uh smart contract using our signer private key uh

64. 38:12

    this is the great um solution to use in cicd pipelines such as gup actions which is commonly used in the critical smart contracts on near when you compile and deploy contract uh in a GitHub action and after that you delete the the all access key so the contract would be locked since the start also uh the cloud-based development environment fits perfectly with this solution uh because they are prebuilt with the docker engine and user don't need to install Docker engine on their uh

65. 38:52

    machine uh so in the future we're planning to integrate and cargo near uh and also there would be a like framework indexer that would automatically cat all deploy actions and compil verify the U code so the final flow should look something like this the user starts the code spaces for the selected repo runs one single common carger deploy uh this common compiles in a reproducible environment the contract deploys it then the repo information is stored in

66. 39:23

    contract metadata on the server side the indexer listens to the deploy actions checks the metadata sends the request to compile and verify the contract and the servers are compiling and verifying the contract as it was before also here are some useful links we have a documentation that has more information on the technical side of the source con and also GitHub all the code is open source and uh also there are some good examples over there so this was it I'm ready to answer your

67. 39:55

    questions amazing thank you very much see yeah seems like a lot of people are excited about it indeed that is the case so I'll wait for a minute uh just see if any questions uh also a reminder that uh uh we can all reach into uh the telegram group so if you're interested more about actually connecting with the projects that they're currently presenting those are just members of our community which we

68. 40:25

    are happy to have around so yeah come and join us on the telegram Channel and let's continue the talks um next on the agenda uh since I don't see any current questions uh or we have only question that Owen has if you can share the deck Andre so your presentation deck if if you can put it into the chat that would be amazing uh meanwhile I believe next on the agenda is Didier from Pikes PE dier

69. 40:57

    Hi how are you hey sorry if I buted your name but my name is not that easy as well okay awesome it's it's good that on mind just says devhub that's pretty good uh anyway so take it way yeah thanks for the invitation uh by the way and uh very glad to be here I think it's my first time in uh the dev Hub community call um anyway I'm the co-founder of Pike which is a data and analytic solution built on

70. 41:29

    near we've been live for a year now and we've just released a new version uh yesterday and for example we used to have this awful uh login wall but we removed that and we also uh pushed a new features and a new um I would say user experience uh so I'm not going to do a full demo uh but yeah basically Pik speak is three things right we have top of the iceberg all the dashboards that are um accessible for free then we have

71. 42:05

    our API with 50 plus end points and you can you know query data on a specific address for example or also metrics related to a specific validator and so on um and the third and last thing we do is more specific and Niche FL on demand features like you know custom indexers as we did for shard do for example or one for NDC um as another example uh but just you have to share my screen uh very quickly uh

72. 42:42

    here um so you could use Pike um I guess as an alternative to new blocks uh we ambition to be in the Explorer uh selector very soon uh but that's the Ownage now where you know you can input any address or transaction Ash block ID will come very soon U so you have you know the TPS meta insights such as uh the total number of accounts daily unique active accounts um and also some

73. 43:16

    Trends about you know what's happening on the Ft transf transfer side but also the stable coin transfers so you can you know go to Pik speak and have a feel and have a look at this new version uh we removed a lot of noise we used to have uh basically we also have the money section where you can check you know what's trending in terms of you know tokens stable coins and if you want to dig in um you have access to you know uh

74. 43:50

    the full uh rich list for this token the number of holders number of of transfers uh the wealth concentration um as well and you know the last transfers and yeah if you um go back here for the transaction uh Explorer so for example we take this one uh you know it's an Explorer so you have the breakdown of the different receipt and we also have a tree view um of any transaction um so you can dig in right

75. 44:24

    um for the different receipt here here and U yeah and if you click on an account you have access to well this is okay uh this is interesting yeah you have access to basically the wet Explorer uh where you have the overview uh for a specific account if it's a contract uh we also added something interesting which is uh the money flow for a specific address you can have this for any address where whether it's a contract or not right uh

76. 44:58

    but it's quite interesting if you want to understand and have a picture at a glance of how the money is moving from and to these accounts and we have the same thing for the token right and you can dig in uh for any token um and yeah otherwise the you know historical view where you have access to all uh the transactions and we are keep we are still working on you know passing well um well-known transactions such as you know swap on refinance uh like a staking

77. 45:34

    or unstaking event for example and and so on so I'm not going to do a full demo but if you haven't seen the new version I would encourage you to have a look and you know make feedback if you have any and we have a lot of new improvements coming too uh but yeah this is our new bik speak amazing thank you very much I would uh dig into it right after the Cod to be honest it looks amazing and it's really good to see more data available

78. 46:05

    um yeah to all the users it might be interesting to explore the idea of also bringing it up as a components on near the torque or near social so that's an interesting concept that could be explored I assume uh so next to the agenda is the heat from Jutsu uh the heat are you around yeah I am hi everyone so uh thank you for I'm going to share my screen do you see my screen yes we did it okay because I

79. 46:49

    don't I don't see you so that um okay so uh uh so I'm zahid uh founder of Jutsu um I'll tell a little bit more about myself but like a today I want to just show our plan of kind of a V1 launch like how we are planning uh so the agenda is simple uh I want to talk uh who I am and then uh our product demo some of the new features we created and our road map uh uh so first of all I am zahid and um

80. 47:29

    I'm building Jutsu for almost one year exactly last year in E Denver in uh boss aaton so when I participated the boss aaton and that was kind of where I created some components and then I realized how difficult it was to build a component from there uh I created a simple IDE web IDE and then um community start using it and that's how it started so and I'm involved with near ecosystem almost two years now other than that I run one of the largest uh JavaScript

81. 48:07

    Meetup Group in in San Francisco and I really want to build a bridge between web two and web 3 and make the web 3 development experience as smooth as possible other than those I I have been working in AI for many many years and now trying to bring all my AI experience into web 3 so instead of talking let's go and see some demo uh first uh I cannot see how many of you used uh Jutsu but Jutsu is a web

82. 48:44

    IDE designed to build uh boss component and the main goal for Jutsu is to kind of help beginner and intermediate developer who don't want to install all the local dependency just to get started so when you log in you kind of land into a web IDE uh so uh probably some of you already use use this platform but the new features are lots of community developer ask about like what are the different things

83. 49:21

    supported in uh in Boss VM some of you who knows um what is boss boss boss kind of a framework that run uh a framework called VM uh near social VM and that kind of uh convert your code from blockchain and then kind of render it in in a uh in a website so and uh there are a lot of functionality so it support uh react like component but it's not entirely react so it is very diff difficult for developer to know like a what are the functionality are available in VM that I

84. 50:03

    cannot use as a react developer so today we added some intelligence so let's say I want to know I I let's say I want to use uh social so when you start typing you'll see uh our intelligent will show you what are the different um classes are supported by uh near VM so we can see there is a near do social doget and you will get the full function signature uh of all those so let's say I

85. 50:36

    want to call a near smart contract right so I can start typing and then I can see like a near uh object have a call method and then you'll get the definition of the call method typically what you have to do you have to go to uh go to the documentation so near Hab boss of a really decent documentation where you can go and you can read about all these different functionality or you can just from now from within the uh IDE

86. 51:08

    you will be able to kind of a uh start getting an idea of what kind of component uh it's support so it's not only just the uh JavaScript component when you come and you start typing you'll know like a there are a lot of web component that uh near VM support for example uh markdown or um if you want to upload a image or if you want to create a typ ahead so this is kind of a making developer life a little bit

87. 51:40

    easier so that they don't have to kind of a worry about like going to different documentation and reading about what are the things are supported and our goal is to kind of a keep this list up to date with all the new features that uh near social will launch the second feature is um one of the main use case that we saw like a lot of people use boss for is during the hackathon or like when you are building in a team um or even in a education

88. 52:13

    setting like you are running a workshop or something then uh you need to collaborate or show other people code so we built a feature called live collaboration where you can start a collaboration a component and then let me share this with the community and you guys can just uh just go to that link and then we'll start seeing like a people um just try that link so we can see a lot of people if you are um if you

89. 52:48

    are logged in so this this person is logged in so it will show your near ID but you don't have to log in so we can all collaboratively kind of build something so build a component so that's like a the idea core idea here is for a small team who want to kind of collaborate or if you are in a hackathon and then you have a four or five people team you want to start building so that's the kind of the goal for this collaboration feature um and another big challenge of

90. 53:20

    of kind of a building component is kind of a how do I know uh let's say I want to build a component but where do I start so I'll you can keep playing with the collaboration but like a so let's say I want to see like if I can add a or some sort of component like a defi component in my uh here so of course you can go to the search box and then you can search uh so uh search Unis swap or

91. 53:51

    or anything really but from inside your IDE let's say if I want to know like a um I want to use unisoft or something so you can now press command P so it will open a more like Visual Studio code like uh a quick search and then you can search like Unis swap uh and then so this is uh then it it will uh basically you can search any component here and then just for quick uh let's say link

92. 54:22

    tree so instead of like every time you have to go to kind of a search and then uh check um check the component of course when you go to search you get you get the detail you get the history um and and but you can do all those things in uh from inside the IDE the third feature I I'm really interested so all these things all these feature are kind of a we are planning to Launch uh before E denber so a lot of things

93. 54:58

    are kind of experimental so one of the thing is we are building a copilot so where basically the idea is to help developer to build uh like a more like can I build something with collaboration with a co-pilot like a GitHub co-pilot so let's say if I select my code and then I can say uh can you can you add add a hero or a H1 D with hello world so we are still sorry for jumping in the hit I just wanted to give heads up to everyone that we are just crossing the one hour mark but this is not a hard stop so if you have another couple of

94. 55:52

    minutes would be amazing and don't miss on the talk that Crystal and lime chain are having on near apjs as well so yeah well sorry I just wanted to know that okay I I'll be quick so you can see like it gives me this uh this code component code so if I can just copy and paste now I can see it created a H1 but it's not just creating a H1 the goal is to kind of taking all the component that we have today and kind of a uh training um a

95. 56:22

    model so that like it can generate more uh uh boss component because boss component you know that it's different than just generating react the last one I will show is like um so one of the feature we are also building where you can build a landing page um or or a simple app um using uh this will be mostly for if you need a landing page or a website builder so we just prompt um other than like that like a pool request and document mendation

96. 56:55

    those are kind of a uh there for uh for a while so this give it a try uh the um all the new features uh the co-pilot and the Beno will be ready in let's a mid-February so that's kind of the goal uh and another thing we did is uh so we received or we are in we received uh a grant from uh tab Hub so so kind of build a bunch of features so we have a public road map that I will share so these are kind of adjust some idea but like a those people probably know me

97. 57:36

    like I love to build with Community uh because it's a community tool so feel free to kind of I'll share this link feel free to uh propose new uh follow the road map and propose new featur so we also have a place where you can request new featur features and I can guarantee you that I will read your feature request and then I'll do my best to kind of implement those um yeah and if if finally yeah if you have any question uh go give it uh give

98. 58:12

    uh Jutsu a try and let me know if you have any question amazing great work a hit I know that you have put quite a lot of effort into it and it really shows um I will drop in the chat the telegram channel for uh for Jutsu so if uh people want to reach you they can do so you're quite active also on Telegram and also in the community groups uh so I encourage people if uh you have anything to do with JSU just reach out the hit uh

99. 58:46

    amazing and uh yeah so last but not least uh we have Christo I believe on the call uh Victor as well and joined by their colleag from lme chain who are going to be talking to uh who are going to be talking about near API JS uh so I'm not quite sure who's going to present yeah start here we do the screen aome take it away okay so yeah thanks a lot for encouraging to join here actually me is

100. 59:20

     very interesting and we're happy to provide further insight into what we're doing uh so a little bit more context about who we are we are at Li chain because it was I think around a year the last time we joined the community call so we are a software development company we're focused entirely on blockchain related projects one of our core missions and the reasons why we existed that we would

101. 59:44

     like to support the technology advancement of the DT space as a whole that said for the last six years we have contributed to a variety of ecosystem systems we're proud to say that from the top 20 wildly adopted ecosystems we have contributed to most of them we have done a lot of projects such as different kinds of toolings sdks CIS host layers run times alternative clients and Etc

102. 1:00:15

     and Etc um naturally our R right now and for the last year is focused a little bit more on scalability Solutions Z case Crossroad communication data availability you know all the topics that are some kind of trendy these days um our journey with near started I think it was around an year ago with relatively small contribution by implementing uh a module for near API JS that enables local execution of view calls recently we managed to do a lot of

103. 1:00:47

     updates and enhancement in the near API JS which you want to present here so that's actually the first point in our agenda to get everybody up to speed to what we have done so far for the last three months besides that as the next step we have more or less clear agenda on what we want to do for the next three months so we want to present that as well and we also like to use your opportunity

104. 1:01:10

     because it's important for us to collaborate with the community extensively so we would like to the opportunity for something like and shout out to encourage everybody if you have any ideas pain points everything that you would like to see happening in your API JS you can use the opportunity to bring it now or Reach Out us after that we'll be happy to discuss with anybody any ideas and make sure that we're implementing things that are recognized by the community as significant

105. 1:01:40

     contributions um that said um I'd like to hand over now the the talk to Vick who be presenting a little bit more technical details on what we have done and of course if you have any questions suggestions comments please feel free to to Bro those so Vick up to you okay so thanks Christo as uh you briefly mentioned in the last few months wime chains team took ownership of most of new API jss de development and

106. 1:02:14

     maintenance and as with every unknown repository we had to spend some time grooming and housekeeping initially in order to get to know it better and understand its outstanding issues and as a result of that in the last three months we have successfully um reviewed four PRS by external contributors we have four we have closed four old PRS that are weren't weren't relevant anymore and we

107. 1:02:46

     have merged already 12 PRS that are part of our uh issue resolving and upgrading the functionality of um njs so if you take a look at the graph this means that we have touched upon about 45% of the PO requests that are currently open on uh that were open at some point on near Apes um regarding the issues um we can see that we have close 25 irrelevant ones these were mostly um very very old

108. 1:03:23

     issues that that were dating all the way back to 2020 and they weren't like up to dat anymore and we just uh closed them and um during our few months here we have managed to resolve five outstanding issues that were with very high priority and impact and we intend to work on at least uh five or six of those in the next um in the next few months um now that we have the bigger picture laid out we can focus on the key changes that we have

109. 1:04:02

     made by resolving or merging uh some of these PRS and the first thing we we'll talk about this security and we know that it's a critical aspect of every open source library and even more when we are talking about a web three library or two we all know what happened a few weeks ago with Ledger and we don't want to take any chances with that happening to the near ecosystem and that's why we have taken a few measures to tighten up

110. 1:04:33

     the security uh we have locked package.json dependence file versions which uh decreases the attack Vector of supply chain attacks and we have removed removed some unneeded dependencies such as JS sh 256 and bnjs and we have also changed the the previous cryptographic Library which was tweet knle with the more reliable and smaller smaller in terms of size called Noble curves um this Noble curve Noble curves library is already pretty integrated into the ethereum world it's well

111. 1:05:16

     audited and um it it should be a reliable one um okay the next thing is bundle size uh although it's sometime it's something that sometimes is neglect neglected neglected sorry in JS libraries our team strives to deliver the most amount of functionality um with the least amount of dependency and such and because of that we have removed some a needed dependencies as mentioned uh before and we have managed to currently reduce the size by

112. 1:05:57

     5% and as you can see on the chart after the pr for removing B.J and replacing it with uh the native Bend of JavaScript um this size will drop by another 10% um there are some technical reasons why we're not uh merging it currently and mostly that it will be a breaking change and we try to group a few breaking changes together so that we don't have a necessary version bumps um yeah and in as it will be mentioned in

113. 1:06:38

     our future plans our current plans actually uh we intend to remove also the not to remove but replace the hvv library which is currently used for Json parsing and it will reduce the size by another 25 to 30% because this library is currently the biggest one um of all the bundle and it's uh taking up about 30% of the size for just parsing some chasons um and last but not least uh we have done some work regarding the

114. 1:07:18

     documentation and tutorials um this is a never ending effort when working on on opensource software and in the first few weeks while working on near API GS we've managed to fix some typos and broken links we we've added JS dos to functions that didn't already have one and we have uh created a guide called integrating near API near API JS with react and it will be out very soon on W chains medium uh we are currently putting some final

115. 1:07:55

     touches and reviewing feedback huge thanks to vat and germo for the feedback um and yeah if you don't have any questions about what we've done up until now I will continue with our current scope so as mentioned already we have uh we we intend to reduce the bundle size by another 30% by replacing ajv Library we intend to improve the error handling and code coverage by increasing the um the amount of unit tests and code

116. 1:08:37

     covered we we intend to uh to integrate labo mode which is which will further enhance the protection against the supply chain attacks we will create angular and view templates and also add bunch of new features and even more you can see all of the details of our work in the our near social uh post I believe Christo can send it somewhere here or you can just type in l chain in the search bar in your social

117. 1:09:15

     and yes sorry just curious like is it like a near APS or is it a separate library and what is the relation with near API JS with angular or view is this part of the template so I'm just curious yeah this will be just boiler plates that everyone anyone can just get clone and start coding right away without uh doing how the sometimes cumbersome setup that might be needed with front end Frameworks my question is is it part of near API JS or is it a separate template

118. 1:09:57

     like you have a separate project for templates no no no it will just be a separate uh GitHub repository that you can clone okay yeah thank you okay thank you for the question and following this we are going to talk about a bit our future work and ideas they're basically going to gravitate our around improving developer experience reliability and security of the packages I've already talked about this we are going to um create some front end specific tools that will like make the

119. 1:10:39

     life of developers much easier such as creating react hooks for near API CHS this this means that common functionality that is used in almost all projects will be abstracted away to to hooks um we also want to create some backend specific guides and examples for example um using near API JS in nodejs environment in order to authenticate users or to generate keys and as Christo already mentioned we

120. 1:11:15

     would love to gather more ideas from the community this way we we we feel that uh we make an impact to their lives by resolving their issues yeah thank you for your attention if I have um I will pass it to Christo for if he has any closing words and do you have any questions about our topics yeah and again for everybody that will be watching this after that recording we can drop maybe I drop my

121. 1:11:56

     telegram handle here so if there are any further comments ideas suggestions questions we'll be happy to to discuss those and see how we can improve near apjs because in the end of the DAT this is very very important component and it's uh yeah of uh yeah I mean at the end of the day it is the first thing that developers have touch base with when they start working with the near Tex TX so it's important that it aligns with

122. 1:12:30

     the community expectations and provide the best developer experience amazing uh thank you very much everyone uh I would like to to thank uh no to all the participants who made it this far and actually all the people who are doing this amazing work that we are uh that we are having uh around near ecosystem uh I would like to share our telegram this is the near tools community group and I highly encourage that if you your project or

123. 1:13:01

     you know somebody who is willing to or is interesting into tooling join it let's talk we are pretty active community over there and we would love to have you on the next call uh speaking of the next calls we have we are aiming to have these calls uh held at least once a month so we are already in the in the process of planning for the next call so if you have anything or like any

124. 1:13:25

     news or anything that you would like to share with the community please let us know and thank you very much if that's everything from everyone all right then I guess I will see you and see you on the next call bye bye bye bye everyone