DevHub Live: Building NEAR smart contracts in the browser with NEAR Playground

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

1. 0:00

   What you want? Tell me what you want. Tell me what you want. Hey. Hey, welcome to a uh exclusive edition of DevHub Live. I'm your host Joe from Near DevHub. Uh we talked a while back if you've been following along about bringing on just special presentations through this live stream to really connect uh with builders and projects that are going on here and things that we find uh exciting that are in the ecosystem. And today I have one of those. Uh there's been a new project

2. 1:03

   that released called uh near play or near playground and this is a really cool project about building smart contracts and I wanted to make sure that everyone could get sense of what it is talked to the builder about how it was built uh how to interact with it where kind of the ideas came from just as a builder like building tooling which is something that we don't always have on here is you know uh what's like to actually build tooling for near

3. 1:28

   developers and just talk about some of the things around the near ecosystem. Uh if you have questions, you're more than welcome to post them in the chat. Um and we will try to get to those as best as possible. But without further ado, let me bring up our special guest uh Toga.

4. 1:42

   Tolga, thanks for uh joining us today. Uh thank you for a nice introduction, Joe, and I am very happy to be here. So today I will excited to uh share about details about new playgrounds. Awesome. Yeah. Now I want to I want to take a quick step back and just talk a little bit about the idea behind what near playground is and I'll set it up for for you a little bit here. Uh it is a way to work on near smart contracts. Uh you can interact with just

5. 2:13

   in the browser but to get to that point what was it for you to like have this idea of like I want to build this type of tooling. Mhm. So let me start from there. uh actually uh I am working with many protocols and uh making actively developments in last three years at the blockchain area. So always one of the main problems have about usability. So as you know wallets has usability problems, developer tools has usability problems. So uh most of them doesn't

6. 2:45

   have a good user experience. Uh so while discovering uh the near uh tooling ecosystem uh I just mentioned about that uh maybe we can make more similar to uh near contract developments uh onto web. So uh what I'm trying to say for example when you want to uh work on any near smart contract at least you need to install cargo near CLI and you need to have at least some information of how to install Rastop and ETA but in near

7. 3:24

   playground I aim to collect all of them into one place to make usable for who experience near smart contracts in yeah I really I I like the the concept behind that because a barrier to entry at any time is right is like just the setup of tooling and uh funny enough like just completely aside from this I was actually kind of complain tweeting about this like last week of like I wish I had a something that would just like set up all my environments for me because that's sometimes the biggest

8. 3:57

   hangup and this is a great introduction especially if you're coming from yeah another chain but even if you're just coming from like web 2 to web 3 to then say like oh okay like I I don't know what it is to set up all this different stuff and all these different SDKs but I want to learn smart contracts and you've enabled that. Uh actually I was just born in the web three area. Uh on my last years at university uh with my friends we decided to work on the web

9. 4:26

   three space. So uh I must say my most of the interactions with web three not web two as a user right but as a developer I mostly work on web three projects. Nice. Nice. And so, you know, um, kind of one of the things I just want to like I think is important here is, uh, you were able to put this together and iterate on it pretty quickly. You took feedback from the community. You posted it and you shared. Um, can you talk a little bit about that approach of kind

10. 5:00

    of building a little bit in public and taking that feedback and being able to, you know, change make changes so quickly? Uhhuh. Uh so actually that is a very good point to touch. Uh so building in public actually very important uh especially if this project is for the public. Uh so uh actually we got uh very positive feedbacks about new playgrounds. Uh some uh some people requested new features, some people has

11. 5:31

    discovered bugs very quickly and we fixed them very quickly too. Also for example, near playground uh has deployed probably 5 days ago and in 5 days we sold a few bucks and reached uh more than 70 user registered on the uh playground. I will share in details at the later stages. Uh so I love to uh build in public and uh also uh this project is open source. Anyone can review the source code if they wish. Uh and that's all.

12. 6:03

    Yeah. No, that's great. I mean, and that is an ethos that we've certainly seen be successful um not just here at Near, but you know, across software over time. Uh why don't we take a little time and start to go through the project and kind of just walk us through a demo. We can kind of talk through it a little bit here. Uh of course, uh this would be great. Let me share my screen first. Okay.

13. 6:35

    Now can you see my screen? Yes, we have you live near playground landing page, right? Yes. Yes. Okay, perfect. So this is our landing page. Actually uh it summarize you what is near playground. For example, it will uh helps you to ship faster on near protocol uh by reducing the entry barrier. For example, uh we as we mentioned early, uh you don't need to install Rust near Cella Caron near or you don't need to deal with pets

14. 7:07

    permissions uh and you don't know to how to deploy uh your contract etc. So near playground simplifies all of that. Uh all you just need is visit nearplay.app and click the launch uh the button. For example, you have two options here. one, you can use your email address or you can continue with GitHub. I will prefer continue with GitHub for this demo.

15. 7:35

    Uh, and I just entered uh because I previously entered with my GitHub account, it didn't ask my permission, but if your first time, it will uh open a GitHub allout page and ask for your permission to connect to near playground. So, when you enter near playground, uh you will see this page.

16. 7:55

    This is uh projects page. Uh in this part in this top you can see your project. For example, at the moment I have five projects that I created on the near playground. You can see it is descriptions when it is created when it is uh updated. And if you have any deployments for example for this top two one I don't have any deployment zero but other ones I have one. And share means you can share your

17. 8:22

    the uh projects uh to public. Uh it states that now at the moment all of them private. Uh I will make them later. How to make uh public. If you want to edit your uh quick details for example like project name you can do from here.

18. 8:42

    And that's all. Also uh let's say by the way uh when if it is your first time uh I will create counter and uh creating projects as default uh to uh start very quickly. Also, we have five templates. All of them tested and working. Uh let's say you want to go with funible token, nonfungeible token, coin flip, uh or other ones. You just need to click for example use template and it will create your project automatically. Uh and this

19. 9:15

    is the core of the near playground. For example, in the left side you have a contract editor which is you can write your uh near Rust smart contract code directly from here. As you can see um many function have exist here. Also you can say with one button uh click compile and deploy. for demo purposes to make it more simple I will uh continue for counter project because it is uh more easy to understand at the first glance.

20. 9:48

    So uh as you can see I just named that counter uh dash devop. So I have some simple uh counter contract here. Uh there is public increment method decrement method and so on. uh for example uh when or you are on the local uh you just need to know comments to compile that project but in near playground you don't need to know just click compile and wait for compile console output.

21. 10:19

    So as you can see uh build succeed and we can see some logs here. But if you want to go further just click see in detail and you can see all of the console output from here for this project. Also uh there is a uh quick tip when you just click pages for example as you can see it will make you a quick tour between the messages.

22. 10:43

    Oh nice. Yeah. Uhhuh. Also uh if you want to share with anyone else, you can just directly from copy here or download the log file directly to your computer as you wish. So uh let's say I wrote my contract here and I just compile successfully. Uh what I need to know at the moment I need to deploy. So uh for example this is very easy uh like compile here for example you just need to click deploy after you say after you clicked uh it will open a new dialog and shows you where to deploy

23. 11:23

    and uh giving you some quick info. U by the way in the near playground you don't need to connect any wallet we will have a built-in uh wallet which is prefounded and for your each deployment um this main wallet uh transfers to near to uh N sub account and for every deployment you will have separate new accounts on the near and here you this is all using test net right? Yeah.

24. 11:53

    Yeah. All using test not mainet supported at the moment. Yeah. Uh also you can see very quickly your contract interface here. For example, it will show you your methods and parameters very quickly if it is seems right or not. And seems right to me. Uh because of that I will click deploy. And it says deploying contract near test nets.

25. 12:17

    We need to wait a few seconds. So as you can see it is deployed successfully and my contract interface uh showing here. So uh I have a contract address here. So there is some uh formatting here for example user ID project ID and Unix time step near play testnet. So and it shows the time for examples uh if you want to check you can just click that button and show in near blocks.

26. 12:51

    Yeah. So as you can see I have a that account and deploy contract method transfer method and so on. So as you can see uh it was very quick and clear. I just compiled my contract with one click and I just deployed my contract with another click too. So with with just two click you can compile and deploy test net and that is uh very loved by the community.

27. 13:20

    So behind of that uh sorry behind of that uh you need to use contract interface to interact with your contracts. For example, you can see your contracts here. Uh let me say I want to make call on this function Vietnam. Uh it says this is a view function. I will click that execute. And it is showing me the contract address here. And I can visit uh again if I wish and I will just

28. 13:52

    click execute. And as you can see it is uh returning uh value at zero. So that's really neat. I want to pause you right there for a second. So, not only So, I I think there's like a few different things going on here that are super valuable for building contract that I hope people are picking up on, especially like for speed of development.

29. 14:13

    Like one like you're doing like a rapid deployment, right? It's right from there. Yeah. We can do that. But then I can continue to test this all in the same interface. I don't have to make my own thing. I don't have to go to nearblocks. I don't have to, you know, sit in the terminal. I can just start to go through and make sure it's behaving the way I want um through there which I think is

30. 14:37

    to me like that's a really awesome feature because I can stay within the same context right like so many developers talk about like I lose context once I'm trying to change you know I go to test and now I get distracted by testing and I'm off someplace else right but now here I can focus in and just test it yeah uh that is definitely the point as you mentioned. So because of that uh I

31. 15:03

    tried to keep all of the uh necessary functionality in just a single page. Uh yeah we can make many tabs for example uh for editor also we can have separate uh page to interact with contract but actually uh that is not the way that I liked. So uh with uh this unified interface uh before leaving the screen you can do all of the things uh that's the playground allows. So uh let me continue with the method

32. 15:36

    testing. For example, we just returned a zero. So I will try to increment here. For example, I will try to increment five. I will just click write five to my parameters. It is integer rate. So I am waiting for result and it is uh returning me outcome and I can see from logs it says increase to number five and it success. By the way if you want to see this particular transaction you just need to click here and as you can see it

33. 16:06

    shows a few seconds ago call increments uh in contract blah blah blah. So as you can see our call success. So let me check again now. So we should expect to see five uh at the moment because increment returned success. So as you can see now I can see five. Uh so also let's say you made many interactions uh with this interface uh let's say uh 20 25 no matter also you have abble to uh go back to your be previous states for

34. 16:44

    examples in order first I called get num after I called increment and latest get num again for example increment uh for increment you can see transaction hash and you can opening nap like we do previously and you can see ra output. Uh so also you have ability to use the application lights and dark modes. You can share your for example uh project.

35. 17:13

    Uh let me uh show you. You can just uh click that button and copy that. when you just open here uh you will see but uh I am in now the same browser uh I can't open a separate uh private window uh because I didn't share that but uh you will just try and you will see you can see the uh this project interface uh it's same but just read only also when you uh go back to your project

36. 17:51

    you can see the project sharing status public. So that means anyone key anyone see your project code uh directly from this link. Uh actually that was the core features uh and community uh requested many new features but uh before I jumped into that part uh I will uh give word to you Joe.

37. 18:17

    Yeah. Yeah. No, I think this I mean I really love what you built. Um and so I I really congratulations on really building a cool product that it was really well received and um I think what has been nice here and I'm curious about yourself building tooling is that you know every developer has you know some of their own quirks of how they want to build. So when you get into the world of tooling people are going to have a lot of different opinions. How have you started to manage

38. 18:48

    some of that of like what choices to make and now adding features to this? Uh could you repeat your question please? Yeah so because because developers can be very opinionated on how they want things especially you know with their tooling. How have you decided to make choices on functionality? Um, is it simply just if you know if somebody is looking for it because it's a newer

39. 19:13

    project, you're going to probably do it or are you trying to fit into a particular setup um in your in your product? Mhm. Uh actually for this version I tried to cover the basics and core interactions. for examples uh it is working on the test net and uh it is a uh simple and qual code editor and it has a simple interface easy to use uh you have all the tools in your hands. So

40. 19:45

    uh my goal uh was to create a good uh interactions uh but uh not an annoying user. So uh of course uh products can be more detailed. For examples I have also uh very advanced features in my mind. Uh for examples from the community someone uh asked me about can we add our crates too but this version not possible because not designed for that.

41. 20:15

    uh and actually purpose was to see the community's interaction if people loves uh that product, if people uh use that product and I am very surprised to be uh to be confessed. So for example, let me share you some stats. Uh I am using Sappase for some database operations. uh for examples uh in just uh last four days 75 user registered and that is a huge amount for that kind of dep tool to tooling in just 4 days.

42. 20:48

    Yeah. Also uh nearly uh about 200 projects created also 39 deployments made uh by the users and 83 people compiled their first project and uh 52 function calls uh made with near playground. So we are just uh starting also one uh nearly 105 people visited the website uh but actually far away than that because most of the people's use ad blocker like something uh so uh that's all uh first interaction was good and my purpose was the uh gaining the first traction actually uh I

43. 21:34

    have very uh advanced features for future reasons. Yeah. No, I I mean very successful I mean I think initial launch and uh again I I've seen all the the feedback in the chats has been very positive uh and so that's really awesome when you know for this I guess of like when you said you wanted to build something why this like why a near contract thing like I I get what it does and I get like the value of it but like why did you personally want to make a a online contract builder.

44. 22:14

    Huh? Okay. Okay. I got the question. Uh so uh as I mentioned beginning at our conversation uh I built many projects for web3 protocols and work with many of them. Uh and this helped me to uh handle with many of the texts. For examples uh I tried many atarium tooling. I tried many Solana Atarium tooling. I tried many intense computer tooling and uh at the at the end of that uh I decided that

45. 22:49

    uh actually there are some playgrounds like like Remix for example everyone knows about Remix but there is not a usable and easy to use one. Uh Remix like u Remix more like feels uh debugging not a building for example. Yeah, of course remix has advanced features but uh you don't have a single interface that uh like that which you can handle uh everything for examples generally playgrounds has uh many tabs and many pages and uh this this causes

46. 23:23

    to lost the context as you mentioned uh previously. Uh so I tried to oh I see to answer your question uh I was aware of the playgrounds and most of the toolings uh because of uh my previous developments so I decided to uh make it more usable and uh try to developers best developer experience.

47. 23:48

    Yeah I mean it's clearly built by somebody who is a developer right like I think that's that's really key. It's not it's not just someone who wanted to make a product like it feels like you know oh okay like a developer built this it has the things that I'm looking for uh for yourself as you start to expand and grow this is there a place where you see a a model to have payments and

48. 24:13

    sustain the project um right now it's free where people can just sign up and use it um but there's probably you know there's your time there's other costs that go into it do you see a path to that model. Uh actually I don't think so uh for this playground because generally these are core things uh for the protocols.

49. 24:34

    Uh so probably this tool will be always free and I try to keep that. That's awesome. Uh and and you know for yourself and you as you start to continue to build on that um you said you know it's open source anyone can go to this. Is it something where people can uh you know create a PR and actually contribute to this project as well?

50. 24:59

    That's something that you're looking for or are you trying to keep it somewhat you know within yourself for now? Uh actually for now uh uh I'm trying to keep it myself because project is uh fresh new but uh of course I am open to any contributions. So for examples uh we can share this link also. You can just go to my uh GitHub near play also this link uh has exist in the landing page just click uh nearly app and just click it up and you will see this page so you

51. 25:32

    can make any contributions that you make that you wish and open a PR. So if that makes sense uh we can of course merge no problem about that but of course uh that uh also means we need to save the quality of the uh product uh so any positive and good contributions will very welcome.

52. 25:54

    Yeah. No, that's great. Uh I want to talk a little bit about some some future features here and some things in here. Uh is there uh code code completion in this as of right now? That's something you look to do if you don't have it.

53. 26:08

    Uh yeah, it should be uh for example uh let me try for example Oh y yeah similar something like that. Yeah. Awesome. And um you know another thing on on near is there are multiple different you know SDKs that you can write smart contracts in. Is that something that you want to support over time like the JS and like the Python one or is you know most people do write in Rust for these contracts is that something you want to just focus on there. What's that look like?

54. 26:44

    Uhhuh. Uh actually this project just started with near but of course uh other SDKs as well uh can be handled in the uh this philosophy but uh to go with that we need to decide if community uh wants to do that because as you mentioned about u most of the development takes time and for example rust tech and python tech is very different uh so also GST is very different. So if we need to

55. 27:16

    uh integrate GS we need to uh give uh a good amount of time. Uh so this is this just started with Rust because I just saw Rust is very popular in the near smart contract development but if community wants to uh other languages we may plan no problem about that.

56. 27:38

    Very nice. Um, this was a great intro and I I'm I really I hope people go check this out. Um, if you're new to Near or if you're already a builder on Near and you've written 100 smart contracts, it's still worth checking out. Uh, really is a nice piece to add into your flow. Uh, if you like it, but I do want to talk about actually building this product and building tooling. So can you talk a little bit about the process of going through this and uh like what's the

57. 28:07

    architecture behind this and how how are you how did you build this essentially? Uh okay uh you are asking me technically right? Yes. Yeah you can get technical. Y uh okay uh so this is a react project. Uh for the front end site uh I am using whites and uh shadowon templates mostly.

58. 28:27

    Uh for the front end part I use deadst also there are some helpers like Axios and something for the back end uh I am using a sh uh axios um I can't remember the name but I am using a ras back end library uh also there's a there's this is works like that for example uh let's say firstly you need to open an account uh most of the things in the playground connect to the accounts uh after you

59. 28:59

    created your account with GitHub or mail. No problem about that. Uh I have a few templates for example like contracts uh deployments at ETA uh for required functionality. Uh for example let's say you created a project and visited uh your project uh I am storing your code uh into a postgrad database. your code is stored but uh when it is uh come to compile parts uh I have a backend

60. 29:30

    service which uh has an API uh I am making some API request with your user ID and your code. So this back end service try to compile your code and showing the output of uh your uh compilation output uh into you and you are seeing here for deploy we have similar logic uh at the back end uh I have a main account uh and all of the accounts uh created as sub accounts on nearly.est.

61. 30:05

    So for every account there is a naming logic. For example, this is your user ids uh first six characters. This is your project ID first characters and this is the Unix time stop at the moment uh you are deploying. So uh back end in the same way using that account basically and deploy your contract with near CLI and return to show you your outputs for contract codes logic is the same. So basically most of the logic handling in the back end side compile compile deploy and contract calls.

62. 30:43

    That's really neat and I mean for you I mean this could become like a lot of stuff to start to store. Are you um like you know like deleting the womms after a while and you know uh to try to you know not build up too much storage or is it something where you feel like uh most womms are small enough that we can just store all of it?

63. 31:06

    Uhhuh. uh at the moment I am storing uh most of them and didn't delete anything but uh as project grows uh as you mentioned there need to be make some optimizations uh for example first compilation takes a bit time and we can focus on that and improve the uh comp compilation time um using some uh sorry no go ahead go ahead okay okay uh yeah we need to make some optimizations but uh now system is uh working very well and doesn't have a problem.

64. 31:45

    That's great. That's really great. You know one of the things here I think is really interesting too is that you know you are really trying to simplify this whole testing part and you know you've made this really simple for developers.

65. 32:03

    Is there a part where you see this going a step further and making this actually like production ready where I could actually ship mainet code or is that something you feel like is not something that fits into your model here? H uh so there is two ways actually uh for test nets I think yeah that is uh like production ready but uh to must say fully production ready we need to support crates as well for example you

66. 32:34

    don't you can't use uh custom crate you can use just use near SDK and near contract uh rust so uh for production probably you will have another packages too which is great but uh at the moment you don't have uh on playgrounds so this is more likely at this stages for experimenting but I would definitely convert this into a fully product which you can which you have a uh file explorer uh which you can edit all of the files as you wish uh in a sandbox

67. 33:10

    environment which you can add custom crates also even uh run the near CLI comments directly from Here for example I am uh running some comments when you click that. Yeah but uh if you wish you will you should uh run your comments directly from here like you are using a terminal for advanced use case. So uh we just started uh and very fresh project uh and that is uh mostly enough for the

68. 33:40

    test net and uh beginners but uh I can say uh not a production ready for mainet at this stage. Uh but uh according to feedbacks we will make a version two plan uh and uh try to collect most of the uh wanted features here like custom page file explorer terminal mainet connection wallet connection eta uh and hope to s hope to uh meet with community with the new version. Yeah. No, no, that it's that's awesome.

69. 34:14

    And I I mean I really definitely appreciate your ambition here um with all of this too going forward. Oh, what the thing I kind of want to wrap up here um this has been a really great demo is the educational piece. So um I saw that you you you linked to the main near docs um for people to use which just makes a ton of sense, right? Um, is there a piece where I'm not saying that you necessarily you build, but like do you feel like this is a tool that should probably be integrated somewhere as part

70. 34:47

    of an educational plan where you can have preloaded stuff, learn how to actually build and go through this uh in a manner that introduces you into this. Yeah. uh actually I think uh but to uh to be able to succeed that I need to work with uh some partners for examples uh someone from the community reached me uh he is recording a video series and asked me about uh if I use your product to uh compile my contract and recording

71. 35:22

    my videos and I said of course you can do uh for example you will have templates Here uh we can create guides for that and anyone can use the templates. For examples in a live workshop or most importantly in a hackathon which you have a limited time uh you can uh create a counter project very quickly and everyone can open in their uh computers and they can very quickly write some code block the logic and try again compile deploy within a second. Uh so probably uh in Hecaton uh

72. 35:58

    site most of the people probably uh may not be uh handled with your uh ST previously that can be the scenario in this kind of uh anyone who is new to near contact development uh can start very quickly at least understand h that is work like that I compiled I deployed uh I can see my methods and so on but uh also I want to make this tool uh more uh generic for educational purpose

73. 36:32

    what I'm trying to say for example imagine that uh let's say you have a website and you are creating tutorials about uh near smart contract for example uh this can be a dowo contract uh I will create uh I will think to create uh uh embed buttons uh for example I will just give a quick small script and you will able to configure this script uh with a simple interface. So this works like that you have a contract place that

74. 37:03

    button in your GitHub or the website and when users click that uh near play directly will open with your uh codes. I like that that's very for example let's say you have 20 contracts no matter just configure the script place into your website and when user click it will show this interface directly and in this way they can iterate and develop very quickly.

75. 37:30

    Yeah, I that's really cool. I mean, that's kind of where my head was going a little bit, like um some of the different like JavaScript tools that kind of do the same thing, right? Um you know, I I I really like that approach, especially where you know, smart contracts for some people, if you've never if you're coming like from web 2 into web 3 and smart contracts is a new concept, like being able to actually interact

76. 37:54

    with it and actually write one and work on one helps learning it so much better. like it's so like to then just hearing about it or reading about it and so I love that approach to be able just to dig right into it. Uh that's terrific.

77. 38:08

    Uh yeah, also uh I want to add some not please if someone uh needs to use near play for educational purposes within their communities uh we can add custom templates uh just reach me. Awesome. That's awesome. That's really great. Um, I want to end on one last thing here and I'm actually going to show my screen so we can talk a little bit about it. Um, so you did something awesome here that uh you built this, you shared this and then you were able to

78. 38:39

    actually go and get sponsored on Ner um with it. And what I really liked um about this is that you went out and you built this first and you prove the concept. like you know here's what I've built. here's what I'm interested in and got people excited and then when and the infrastructure h committee has an open sponsorship and you applied there and it was approved and I think this is just I

79. 39:07

    just kind of wanted to highlight this path of building where you know you were passionate about something you built it and then you were able to actually go and probably have an easier time than than if you just had the idea uh to go apply for the for the sponsorship. But yeah, for yourself um you know like what does that change for you you know now that you have some sponsorship to actually work on this um how does that change your approach to building this or maybe

80. 39:39

    it doesn't at all of course uh so firstly uh I must say without near uh this project wouldn't happen at the moment so uh as you can uh mentioned about for this kind of tooling for this level of tooling I think I gave uh very high amount of time uh uh except of time uh this comes from the web3 experience previously uh you need to you need to know something about tooling you need to know how concepts well you need to know how developers love so this is

81. 40:12

    just not about time to also uh but thanks to near I hadn't this opportunity to make this product live uh on the near and I am very happy to say Yeah. No, that that's great. And um it's a really nice success case to show kind of that pathway to. So, I'm I'm really happy for you. I'm really I'm really excited to see what you continue to do with this.

82. 40:38

    Um again, you know, I don't know there's anything else that you want to add here, but uh I really hope people continue to check this out, continue to build on this. Um you've really built something pretty cool here. Thank you. Uh thank you Joel.

83. 40:55

    Yeah, thanks so much for coming on today. Uh we will look forward to all your updates and we'll keep promoting it. Thanks so much. Okay. Okay. Thank you much too much. Uh also I want to adjust that if you have any questions or feedbacks about new playground. You can find me in the New York tools community group at Telegram.

84. 41:14

    Perfect. Yes. Yes. So so on the Telegram channels, check them out. Awesome. Thank you so much. Thank you. Have a good day. Bye. Thanks. Bye. Uh thanks folks. I I really hope everyone checks that out. The links are at the bottom. Nearplay.app uh is the link to check out. Uh please go try it out. Give feedback. He has been super responsive to anything if you have different ideas. So please absolutely

85. 41:35

    check that out. Uh again, uh Ner is a great place to go look for different freelance opportunities. If you're looking for stuff like that in the near ecosystem, definitely check that out. Uh we will continue to have these from time to time. If you have an awesome project that you want to showcase here on a DevHub live, uh please, you know, reach out to us and we will get that set up and because we love to showcase different projects and talk about dev

86. 41:59

    stuff. Uh but until then, uh check out the docs, keep building, and we will see you next time. Thank you so much. Bye-bye.