DevHub Live Episode 48 - Developer News, Infra RFPs and what's new with the Wallet Selector

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

1. 0:00

   Tell me what you want. What you want? What you want? Tell me what you want. What you want? M. Hello, hello, hello. We are back live with another edition of Dev Hub Live. Uh we've been off a few weeks playing some replays. I hope everyone was able to catch up on some of those great episodes. We've had some really awesome guests uh over the past year and want to

2. 1:02

   make sure that we're highlighting and kind of bringing some of those back and they're all relevant topics I think that are if you're building or you're interested in near what's going on just in the larger ecosystem. I think those were some great episodes past few weeks.

3. 1:15

   Uh today uh we are heavy focused on a lot of things that are happening right directly in the ecosystem. Uh, I have two of my awesome colleagues, Josh and Trenton, jumping on here to talk about what's happening in some of the different releases that we've had around the wallet selector, some RFPs that are out there for infrastructure. Uh, we got news to talk about, and we may even have

4. 1:37

   a special appearance from a a fan favorite uh, as well. So, uh, without further ado, uh, again, I will show the newsletter at the end as always, but why don't we get, uh, Josh and Trenton on the stage here and let's start talking about what is happening in the ecosystem. Trenton, Josh, how are you guys? Good. Hey, doing good. How are you? Good, good, good. Well, let's I mean, there is so many places to start, but I want to begin with the wallet selector. This has been something that

5. 2:11

   was initially a high point of excitement when it first released to unify the wallets and then it became a thorn in people's sides for a while. Um, and now we're here at version 9 and I think it's a really nice update. Uh, whoever wants to jump in and feel free to kind of What's special about version 9? Yeah.

6. 2:32

   Yeah, I'll uh I I can speak to that. So, um, our friend, uh, Germo, uh, was really instrumental in, um, kind of coordinating, uh, all the pieces for version 9 and getting it tested. And so, a shout out to him for for his hard work on that. It was great. Um, so the most important thing I think about version 9 is the uh, upgrade to the latest Hey, Vlad. Update to the latest version of near APIJS. Um so that was lagging behind pretty dramatically.

7. 3:04

   There's quite a bit of uh improvements to both the performance and the functionality of near APIs. Um and uh it was holding back um several wallet integrations uh with compatibility issues and it was that you know talk about thorn in your side uh was a very constant problem trying to uh get it released and get it tested because of of those uh backwards compatibility issues.

8. 3:28

   So that that's probably the most significant uh change and that's why we bumped it to the major version is we um we we needed to update that that version. There's some other quality of life improvements in there. There was a ton of updates to um documentation on the wallet selector side. Just some stuff that was lagging behind that needed to get updated. Um so there's there's quite a few little changes in there. Um, we've we've uh some package deprecations because uh

9. 3:59

   some of these wallets just aren't around anymore or or we we moved off of them. For instance, the near wallet hadn't been deprecated for some reason for like ever and ever um and it needed to be removed. So, um a lot of it's just feature improvements. One of the things uh that GMO did for us uh was was dramatically improve the load time for wallets. Uh, so there was a for the nerds out there, it was uh it was kind of a synchronous uh approach that that

10. 4:27

    was that was kind of holding things up and it now it's an asynchronous approach and it does a really great job at just loading up quickly. So um yeah, like I said, a lot of lot of kind of speed improvements, quality life improvements.

11. 4:37

    Uh but most importantly, it's it's up to near API GS5 uh fun in in kind of a similar way. Excuse me here. Um kind of a similar way. Uh we're go looks like near ipigs is coming up on another major version for itself. So we'll have to go through this um exercise again. Um and that that takes uh a little bit of time from a testing perspective, right? We we have to go through and basically test every single wallet and every single integration. So right um that that takes a little bit more effort. It's not

12. 5:11

    something we can just do uh quickly. So near near APIJS we'll have to upgrade and then we will have to uh test it in wall selector before we push out. Yeah. And I think what's important here is yeah there's a lot of behind the scenes stuff that I think was fixed and I like the backwards compat compatibility but as a builder the especially the asynchronous stuff the having the user experience improved because things are loading faster uh it's less weight on

13. 5:39

    your product. Those are things that really should, you know, is why we want people to upgrade to this. It's why we're making a push to get it get the word out that if you haven't updated in a while, this is a good version to jump up to make sure that you're up to date on because it is a better user experience if nothing else. Yeah. And what Go ahead. Go ahead. I was gonna I was going to tag on uh two things to it.

14. 6:03

    um for for developers and even like users um um of their applications. Uh one major thing was that now we have a modal for um uh when you're now like clicking to sign in or sign a transaction, no longer do you now have to um go to a different page and now reload the application. Um now it just pops up a modal. So it doesn't really break your UX anymore, which is super uh important for like, you know, my near wallet, Meteor, um those people that are using those wallets that previously

15. 6:34

    would redirect. And also we did add some um React hooked um libraries and and examples just in making it a little bit easier for you to call and and use some of the functionality. Um just kind of really wanting to use more um hooks and just simplifying functions for developers so it's easy for them. Uh, and you can see those at near um-amples repository or I'm sorry, GitHub organization. Um, we have examples in there for you to check out and implement into your code. Um, but yeah, those are two other things I would like to to shout out in the wallet update.

16. 7:09

    Yeah, that's that that's awesome. Now I think along with the wallet update so going forward there's also going to be kind of this split of two kind of versions of the wallet selector. Can you talk a little bit about that? Yeah, so uh the infrastructure committee uh put out a request for a new maintainer for the wallet selector and we got two really great proposals. Um and so instead of deliberating on which one we were going to go with, the infrastructure committee decided to to

17. 7:39

    to prove two different ones. So the first proposal that was approved is for what we're we're calling Walt Selector version one. Um that is by Lucid Labs and Lucid Labs is going to take over the maintenance of the current Walt Selector that we're talking about today. So they're going to take over the regular updates, the maintenance uh coordinating of PRs and then they have some um improvements that they want to make.

18. 8:00

    They want to do a refactor and improve the code um and and and add maybe add some features. There's there's there's a pretty steady request of feature requests that come in on the Walt Selector codebase. So they're going to take care of that. Then Hot Labs, our friends here, wallet, hot wallet, telegram wallet. Uh they made a proposal for kind of a injected wallet standard like an injected uh paradigm. So we're calling that walt selector version two.

19. 8:26

    It's a brand new um it it is really not it doesn't really have any basis on the previous uh version. And it build it builds a framework. So builders will just add a frame a framework to their to their codebase and otherwise the code is pushed to it. Um so what this allows us to do is basically eliminate the monor repo. Um and each adventure visual package will be responsible for their

20. 8:51

    code and compatibility. Um and so it gives us a little bit uh it gives us some more um some more speed to market right. So each wallet can you know add features if they need to fix problems um and then just put it in their just uh publish it to their package their mpm package and it will just push out to walt selector v2. So it's a pretty exciting development. There's there we kind of uh act as a bottleneck sometimes because you know we we're doing releases basically every two weeks realistically.

21. 9:24

    Um, and uh, this would allow people to basically publish as they needed to. Um, putting the control back into the hands of the the DAPs and the wall builders. If I may add, uh, I want to point out that it's only possible because the hot team is working on the some improvements to the protocol like how to um, um, integrate wallet selector in your application in a secure way. So you do

22. 9:52

    not uh just randomly download some random JavaScript code on your web page. That would be hazard uh from a security standpoint. And instead they they are working on some uh iframe integration that would be isolated. You wouldn't be able to escape from there and it would be just a some messaging protocol between the your website and that frame. And inside that frame we can freely put some random code. It would be uh still need to be audited but it's uh it can be then

23. 10:29

    updated even after you publish your application without changing your application code. So even uh two years from now uh we would finally be able to solve this problem of outdated applications that are still using the old integrations with the wallet that we cannot upgrade anymore and we're stuck there. Some of the applications we still see are using the wallet.org uh which is not no more. uh uh and the uh this approach uh world selector

24. 11:01

    version two would solve a lot of those problems and uh speed things up uh hopefully and also allow to iterate and uh change things uh much faster and bring more features and hopefully also reduce the size of the uh of this integration because currently each wallet uh builds their own way of integration.

25. 11:29

    And uh part of the design that hot team is working on is how to uh reduce and just uh create the some of the uh known patterns for how to uh integrate with mobile wallet, how to integrate with web wallet, how to integrate with browser extension. But there there are like just there are many options indeed but uh they're finite and we can uh design around those instead of asking each wallet to reimplement it from

26. 12:00

    scratch. And the key thing here too is which I think is important you hear the name hot and you hear them here but is not just for their wallet. This is for all wallets to still do. So they are just taking on this project as part of the larger community not again not just for them. So you anyone who is building a wallet can still leverage this which is great. Yeah, it was a request for proposals, public one from infrastruia

27. 12:30

    committee and we had uh several teams uh established and having their own pro projects already on near and new ones submitting their proposals. It just happens to that the uh hot team had always had this uh uh um pain point that they wanted to address in New York system and they have a lot of expertise there and their proposal was very um clear and uh um infrastructure committee decided to go with a uh with sponsoring it. It was a bit risky because it would mean that you need to

28. 13:11

    uh build it from scratch and to the risk it um there was a another proposal also approved to make sure we have continuous support for vol selector until we are ready to switch over to this v2 or who knows they will potentially be able to merge at some point um and that would be the best for everyone I would Yeah, I mean we absolutely get to that point and I think as a developer the things that you should be hearing here are one continuous support so nothing is

29. 13:49

    changing today things change more you can still keep doing what you're doing uh the new protocol is going to make it easier to update deploy do things like that uh and then so there's like both now and future proofing in all of this and that commitment to support for developers I think is an important piece to highlight that nothing is getting just deprecated and thrown away. Uh you can keep doing what you're doing without

30. 14:15

    the fear of having to restructure a lot of your code. Yeah, if if everything goes according to the plan, the wallet selector will have this exactly the same interfaces. uh Lucid team actually works on extending those with support for uh metat transactions for signing transactions without sending them from the through the wallet and basically allowing the application to send the transactions. Uh the same goes for meta

31. 14:44

    transactions and uh signing in without creating a uh um new access key. Um so all those features will be uh exposed to the public interfaces of wallet selector and at certain point um with the improvements on the protocol level and like this how how to integrate wallets through the uh iframe kind of thing from uh the hot team. uh they will be potentially be just you know swapping the internal implementation while keeping the public APIs

32. 15:23

    um the same and it would be hopefully a a non-breaking change for the users uh while enabling this uh um yeah better uh future proofed um wallet integration w selector integration. Okay. Absolutely. Absolutely. While we're on the topic of this was born out of RFPs. If people don't already know, there's something called the infrastructure committee.

33. 15:52

    Trent, you want to talk a little bit about like what that actually is for those who don't know what that is? Like where the RFPs come from? Then we can kind of jump into what's out there today. But what is the infrastructure committee? Yeah. Yeah, the infrastructure committee was formed um by leadership uh across the near ecosystem in the beginning of 2024 to address infrastructure concerns. So um you know the speed, performance and and

34. 16:17

    reliability. Um and so their their charter was uh they were given a a a large envelope of money and to uh work together to go out and you know improve providers, improve uh offerings on on near to make sure that things were working really great. Um it was it was really successful in that in that first year. Um a little bit o just just around about 2.5 million in grants given out in

35. 16:41

    that first year. Um probably 20 plus projects that were were funded. uh sharp infrastructure and and it was pretty obvious by the end of the year that it had had a good impact on our performance and reliability. So um it was that that's where it was. So we're in our second year now. Um and it was it was probably present to have uh something like the infrastructure committee um as uh Pagota as they as they decided to wind down. Um there was quite a bit of

36. 17:12

    infrastructure that they provided to the ecosystem. Um and so having the infrastructure committee there to take on that transfer of those and decentralizing those providers was also a a blessing. It was very significant work there as well. That transition moved really smoothly and we got uh you know we didn't have any downtime. We we got the stuff moved. So that was that was really great. So that's what the infrastructure committee

37. 17:35

    does. Um it's got uh various members on it. It's a volunteer organ uh organization. So our friend Vlad here is one of the uh members of the committee. Um we have Eugene from Fastner. We have uh Eric from Near AI. We have Bowen from Near One. And we have Who am I missing?

38. 17:55

    Alex from Aurora. From Aurora. So um I call it the OG crowd, right? It's the OG council. Um and they they advise and they take a look at this technology and decide, you know, if it if if it's a good investment for the new ecosystem.

39. 18:09

    Yeah, that's and we are talking about projects like explorers wallets uh projects like near lake um wallet selector and um services like that basically um and trying to identify how to make it NRPCs obviously uh how to make it um not just a like forever funded but also make a an economy of um of its own uh in near ecosystem. So the uh infrastructure providers like in true decentralized uh manner have their own incentives, their

40. 18:52

    own customers and they have um yeah metrics they care about um on their own. So we are setting them up for success. That's why for example uh the public offer free uh RPC offering has been uh significantly uh throttled. So um the production applications uh should not rely on some free um provide pro providers because it's not never free infrastructure is maintained. Someone needs to be uh on um in charge of um timely updates and maintaining the performance of the

41. 19:36

    services. Um the uh decentralization doesn't mean free uh options but the free entry. So anyone can run their own infrastructure uh or you can you have an option to uh delegate it to someone but delegation uh means you need to pay for the service and um thus uh lavaet and uh fast are the biggest uh providers these days uh that I'm aware of and um we are trying to not compete with them basically providing the free offering through the RPCs.

42. 20:21

    It it's I think that is such an important piece where so many things early on were so heavily grant reliant that when that money dries up if something changes uh it is hard for the builder in that case for the instructor to stay incentivized. So it's really important that people who are coming in this is not just a grant program where you are again it's not a forever program it is to hopefully kickstart you that meets a need that is in near too that's

43. 20:52

    the other thing I think is important here is that is not just anything it is things that are actually actively have a need within the developer ecosystem so that you know you have a potential audience already because it is something that is needed uh and I think that's a really a really strong part of this too is that you're not coming in just hoping for the best. There is a lot of

44. 21:14

    opportunity uh from day one. Yep. That's great. So, what are some of the things right now uh Trenton that are are are up for RFPs? Yeah, right now the the big RFP, we just extended the deadline on it for two weeks is we're looking for someone to build us a multi-chain uh relayer to support um you know near's u intense and and multi-chain. So um if you want me to, I could post a link in the chat.

45. 21:44

    Yeah, we can pull that up. See that? Um give me one second here. And uh I'm gonna uh just give me one second. There it is. There it is. Give me one. Here we go. Sorry. Too many tabs open. Too many tabs. All right. So, there it is. Um, a note to the group at some point here we're going to be um having we'll have a different site for these to be posted on, but right now this is the this is the one that's currently in use.

46. 22:30

    Um, you can submit a proposal here. Uh, you'll need a uh a near social account um to sign up. So u be sure you have like one near on that because it uh keeps a little bit for storage when you post. Um and um I will also share a telegram group link here with you. Um so if you run into some problems, you can talk to us. Let's see here. It's just called IC requests.

47. 23:12

    But yeah, that's that's the first RF RP. One of the uh one of the things that um our friend Conrad at Near Foundation, who's the head of partner success um and infrauccess, uh we we have a working group that supports the infrastructure committee. That's what I do. I'm a I'm a TPM that supports infrastructure committee. Um and we we are getting ready to gear up for another round of ideation and discussion on the next

48. 23:38

    batch of RFPs. So there are definitely things that that we the infrastructure committee wants. Um and so that that will be forthcoming. So there's there's more coming. That's great. That's great. Let's talk about this one. Yeah, let's do it.

49. 23:58

    So from the name chain abstractor layer RFP. So let let's uh decouple it uh RFP and let's start from the end. So it's request for proposals. So we we are searching for the teams who will be um uh trying to offer the solution here.

50. 24:21

    So there is there is just problem statements here uh potential solutions and um yeah let's dive in chain abstracted uh this means that we are working in the space where it's not near only offering but we're looking for the uh one-stop shop for the solution that would work for any the any of the chains that we are already abstracting through near chain signatures.

51. 24:52

    And um as such uh we want to have a re layer. And what is a re layer? Relayer is the uh service uh or potentially in some cases it could be uh a uh an SDK plus a uh some account where you have the um funding accumulated. But usually you still need some uh backend service for that. Uh that would be funding the um requests uh the the funding the not funding compensating the fees that uh is

52. 25:32

    needed to submit a transaction uh to any of the chains out there. So all the blockchains operate in the mode that you have to pay for every transaction you send. So the transactions are uh not free and you usually need to pay in the native token of the chain. So when you're building the uh crosschain applications, you may often face the problem of that uh you need to sign transactions uh for the users on various

53. 26:05

    chains and you have you have to request the users to pay the fees and if they are paying the fees and native tokens on the chain it's a uh yeah you you either request them to have those tokens or you need to have some way to um um to cover that up. Um and the solution in all the blockchains is usually uh a form of relayer. So instead of sending the transaction that you created uh to the blockchain itself, you send it to a relay service and that relay service

54. 26:45

    wraps up the transaction with their own transaction. So they compensate the the fees associated with the uh transaction submission and the um the fee itself is uh then charged from the relayer account while the rest of the execution uh that was signed by the user account uh will be then exe um yeah processed as if there was no um relay involved. this way um it it could have a very good improvement to

55. 27:29

    the uh user experience uh for if if I if I'm a uh the app developer and I don't want my users to immediately have uh some near token some E Salana any other token uh in order to uh work with my app I can offset that by compensating ating some of their transactions. I can code up some logic in the relayer and decide which transactions I want to sponsor or how many of those transactions from a single user I want to sponsor uh the fees for. Uh but I want it to be very

56. 28:11

    simple and easy. I don't want the uh to build this from scratch all the time and maintain it for every single chain out there. So we are looking for a very simple uh solution for uh the app developers to use in order to make the user experience for their users uh streamlined and uh um make sure that they can have their first for example 7 days trial period uh before they commit to have their own

57. 28:50

    near tokens. for example on their account to compensate the costs. Is another name for this if people have been following along with James fraction like a gas station is this the same concept here. So I think for people who are interested you know as a builder right one of the things that I have seen come up but if you are working on chain abstraction stuff is this is a a an issue of where

58. 29:16

    uh how do you actually fund all of these different things? How do you make sure it's being handled properly and can it be done in a way that is not you like you said Vlad standing up your own stuff every single time all that other stuff.

59. 29:31

    So uh a lot of opportunities here something you're already building here's a great way to get some funding to help you get over the finish line hopefully um and and go from there as well. There's some really uh great stuff there. What is the timeline on this?

60. 29:48

    We extended the deadline till May 29th. Uh so submissions uh we're accepting submissions until the 29th. Um it usually takes about a week to deliberate. The infrastructure committee meets on Mondays once a week. So uh I I would I would guess on average it would take about two weeks probably. Um some discussion on the first one and then some deliberation after they've we uh narrowed it down. Um and uh so two weeks

61. 30:14

    max I would think before the decision is made. And then the execution it's up to the teams to define and propose. Um depending on their experience if they are building other gas stations, gas uh relayers um maybe they have a lot of experience there and they would say oh it's not that much time we'll do it in a in a months. Others may uh say like well we don't have the experience but we have um a product vision and we will be building it as this and that and this is

62. 30:53

    our uh first iteration MVP in two months and then we will collect the feedback and iterate from there that's also an option and we will it's it's u um yeah we will we will hope to see um several proposals to compare with. Um the previous ones we usually had um four to seven uh competitive uh proposals. uh and uh in not even once we have selected two uh so it's uh not necessarily winner takes all uh situation but uh um both

63. 31:45

    are usually really good proposals uh attacking the space from different angles some from the product vision others from the technical um excellence. Both work. Awesome stuff. Great. Uh, other points about the infrastructure committee that we haven't touched on. Anything else that we think is relevant right now? All right. Well, let's I'd love to if you guys stick around, I'd love to have your guys take on some of the different news that's been coming out. A

64. 32:23

    lot of great stuff that's been happening. Uh and I definitely want to start with uh let me pull up another slide here. So uh if we go back the past few weeks, there's been a lot of different things and one of the things right now has been coming up a lot is the faster blocks and um faster finality. Uh this is from our newsletter a couple weeks back. we first kind of uh provided this information including a a link back to what uh Bon Wang from year one actually wrote about this protocol

65. 32:56

    update. Uh there's also some stuff around change signatures which we'll get to in a minute. Just the first part about block speed finalization. Uh Josh, you haven't we haven't brought you up too much yet. Starting with you from like a developer standpoint. Um does that mean anything to a developer really at this point?

66. 33:15

    I mean, I think it does. Like, you know, the faster you're able to finalize a transaction, return those result, the the closer we're getting to bridging that gap between, you know, what a blockchain experience or a DAP is and what a traditional web two development experience is, right? Like, you know, when we first launched and we were actually really quick compared to some of the other chains that are like, you know, five minute or a few minutes

67. 33:39

    finality. Um it definitely you know creates like this what what am I interacting with? How is this experience? You know, it's a hard cell for a developer um to um push out an application that a user is has an expectation of that speed, right? Uh and this is just another push in that direction and us leading the forefront or near leading the forefront of of just quick um blockchain uh block um um um um times that are enabling that experience

68. 34:13

    that is seamless um that you know you don't have to have these optimistic hopefully that this will transaction will go through. No, it's actually going through this quickly. Um, and therefore, you know, you're having these experiences that users can have. And, um, yeah. No, I I definitely think it's really important. It's super important.

69. 34:31

    Yeah. Z, do you want to add? Looks like you're add I I came to NIA from the web two world as many of us I would say. uh and there the expectation that when you sub you make an API call uh to post some data you want to get the results within half a second maximum correct usually you actually expect it to happen within like 100 milliseconds um and this is uh not the case in many of the blockchains including near today

70. 35:12

    uh but we are on trajectory to get this uh really uh on par with this experience of regular backends. And that will open up a lot of opportunities uh for uh just uh replacing the standard web two database that is uh um not transparent and uh you need to make like come up with some strategies how to make uh reliable in a way um with all the history and change of uh like keeping trace of changes. if you want to have it

71. 35:53

    um and replace that with a simple near calls and build your own smart contract to uh deliver that. Um obviously not every application needs to be uh living on the blockchain. Um but with this improvements of uh yeah subsecond uh block production time and the transactions landing there. this fast.

72. 36:21

    This opens up a lot of uh opportunities and usability user experience improvements uh for the end users which is uh definitely welcome and um I think on near this is the what we can uh finally say that's it's it's it's not a quirky blockchain where you have to uh deal with the fact that you submit some request and wait for five 10 minutes and only then hope that it's actually there and that is even at the

73. 37:00

    and and at also at the cost of like hundreds sometimes thousands more expensive than what we have on here. Sure. Is this something you guys know? So, would this because it's now speeding up the blocks, does it cut down the time of an epic as well? Yes, it did. Or does the epic length stay the same? Uh, it it did cut down the epic uh the epic uh time roughly uh by 30%.

74. 37:34

    Um but another question that others may ask is uh whether it uh affected the uh rewards in any way and that is not the case because the rewards are uh tied to the number of seconds in the in a year and the when when the epoch ends it it compares the time stamps of the first uh block in the epoch and the last block in the epoch and um um rewards accordingly based on the projections for the whole year and the how it's called

75. 38:15

    um so it's not distributing more rewards because there's more epics happening right got it got it got yeah got it where I mean from from what I know the there is no plans to further shorten the epoch because there there are some challenges with that. Sure. Uh and yet the uh there is a plan to further reduce the time for blog production and there are some clever ideas that Bowen shared on Twitter uh recently.

76. 38:49

    Nice. And from here, you know, where do you think you'll see this first pop up in in products? Is this probably mostly like DeFi first, right? like we're just finalizing transactions, swaps, things like that. Um, is this going to be noticeable in people's wallets and just other transactions? Like is that something that or does the rest of the app have to be kind of updated around handling this

77. 39:20

    kind of speed? you know like like applications don't need to be changed and the oblig but but but the signing transactions will speed up as I said and at least uh uh by 30% um if it's a very short transaction and up to uh um twice as fast uh for the transactions that involved uh multiple cross contract calls and uh etc. On that front uh while we're speaking about the uh perceived improvements of the speed um I can also recommend uh the app developers to check

78. 40:04

    out the uh what they ask uh as a finality um mode and uh there there are three modes basically. you can be very optimistic and as soon as the transaction is delivered you you you you just say okay it's a that's enough I I I don't care let the user interact with my application. Um the second mode is when you're waiting for uh the transaction to be included uh and the uh receipts to be

79. 40:38

    executed. But that's still uh optimistic in a way that uh the unless the blocks are finalized. Uh there could be a fork and it uh could happen within those uh sub seconds uh several seconds. Um and then if for for for majority of apps that's also totally fine but uh the safest default is to go with doom slug uh finality which happens uh once there is one extra block produced after the one that uh the receipts are included.

80. 41:20

    Uh and that usually happens within those 1.2 seconds. Um so that is the controls that you have uh when you submit the transaction. So when you call the broadcast transaction uh all those options are there. So check out the documentation uh out there.

81. 41:41

    Yes. Besides to that also though too near one then also announced that chain signatures is also now mainet with uh eddsa support which is chains like salana ton stellar hapto and so on. What is the like and just and this is maybe just a more high level like what is the then the developer experience at this point of near where you no longer when you're building on near you're no longer just tied to the near blockchain but you have at the

82. 42:19

    same time all this great infrastructure that's here but then you have this opportunity to kind of really go across these things like how how are you guys thinking about posing this to developers coming in and saying like you can start here and build everywhere like like what is the messaging that you want to get across to people?

83. 42:42

    Josh, do you want to take this one? Yeah, I mean, sure. Yeah, of I mean it's it's pretty awesome that you Yeah, I'm really excited about this, you know, release that um we now have the support. You can now build with Salana. Um, and it unlocks another ecosystem that, you know, Salana definitely leads a lot in like the NFT space. Um, and you know, you want to have one account that can control and um, you know, basically transact across all these different

84. 43:11

    chains. And, you know, we had support for Ethereum and all these other um, um, platforms and now, you know, opening up to more um, chains is just, you know, obviously a better better option for for the developer, right? um you don't have to sit there and like now deploy at each individual um chain. You can now create one newer account, manage um this one account that can then transact across um all platforms. And then that's the same it's a better user experience too for um the users that

85. 43:46

    they can sign up and create an account on say a DAP that can then perform these transactions or perform um any kind of action um across multiple chains by just having one account rather than having to sit there and try to manage all these different accounts across all these different platforms. Um, for me it's just like simplifying things a lot and makes things easier and the the better, you know, we we continue to develop um

86. 44:10

    better tools and better um, you know, making it easier for developers to build and make it easier for users to use their their their applications that they create. Um, so yeah, I mean it kind of feel it feels like it's a no-brainer for me. I don't know. Um, for all the nobrainer and there is no alternative that I know I'm aware of. Uh and the the what it opens up uh is basically this uh

87. 44:36

    uh Lord of the Rings uh rule one one one uh one ring to rule them all. Um one chain to rule them all. One chain to rule them all. uh but uh in simpler terms I believe that uh the this is not only for the users to benefit from like well if I'm a user I I'm maybe I'm okay with having all those wallets and it's maybe I'm using like three of them and it's it's kind of manageable but what it

88. 45:11

    opens up is to basically build uh apps that just operate on their own And or maybe like uh there is even a chain of applications that actually uh integrate with each other and uh at any any of those application could could also interact with the uh applications on another chain uh and manage some state there. the request to change some this or that uh on the on the um on a different chain for this specific application and the owner would be the

89. 45:51

    smart contract not the user uh which is uh not the use case that we saw before where the users would interact and um being charged with their own keys. We we move this uh a bit further away and uh this opens up uh potential for agents and other programmable entities that would uh interact between each other and have a one place to to have full transparent control uh over other blockchains and uh stuff.

90. 46:38

    Yeah, I think I think that's really interesting on a few different fronts and I think that falls into the next kind of two-parter that I wanted to talk about in context of being a developer here on Near and stuff. So, uh, Proximity sponsoring shade agents and they're pushing out shade agents which again agents that kind of run in the background. So right they're they're they're not as upfront and this not the front end isn't necessarily there. And then you have things like you know the announcement also this this past issue

91. 47:11

    here of pass keys. So the algorithm that goes to the pass keys support on the runtime level of of near blockchain. So now really reduces the need for different kind of identification. Right. So like you can just come in with your phone and you're off and running all the way from there.

92. 47:30

    with all of this. So now you have this crosschain, you have agents, you have ability to really abstract so much stuff. You can use just the biometrics that are built into the phones, all stuff. How I mean as a developer now with like you have this almost like uh abundance of choices of how you start to design your product.

93. 47:55

    What is the thought like where do you have someone start and maybe trend you as a TPM you know you think about these problems of like how do we right organize all this stuff like where where do you go with all this where do you begin because you could be spinning your wheels for weeks just figuring out like how am I going to architect my my my app here. Yeah. Um, I think Hot Wallet uh

94. 48:20

    had a lot of success just implementing uh one-click connect um to help them leverage uh near intense. And I think that if I was if I was to start uh doing something with payments or um with with uh transactions on my app, I think I'd start there. I'd start just to look at that implementation. Um and at the minimum, it's going to give you some ideas about how you might want to implement it, right?

95. 48:45

    Um, yeah, I think, um, I work I work at NearDev now. Um, and I work with some some really savvy people that, uh, build, uh, documentation. So, I I I do still think that docs.near.org is a fantastic resource. Um, you know, it's it's just about kind of understanding the core transactions. I mean I mean when I when I look at these these changes fundamentally if you're if you want to develop on near and you and you uh understand how to interact with

96. 49:18

    smart contracts the fundamentals are there right so right um the you know you're going to uh you can you can load up a user's wallet and we're we're basically housing assets you know directly on on their account right so I think that the I I I don't think there's a lot of differences and Vlad could probably speak to this a little better than I can, but I when I'm looking at this from from the 10,000 foot level, I'm still

97. 49:43

    seeing the basic interactions. The the fees, right, the time to finality, the the the the speed of the near network, and then the fees are are like significantly lower, right, than than you would that you would find in a lot of places. So, I feel like there's there could be a lot of advantages for app builders that do want to have that um that compatibility and that that that broadness, right? So, I think where the lowhanging fruit here is for the dev world right now is to remove some of the complexity around the technology, right?

98. 50:20

    Like crypto is is tends to be pretty focused on technically adept people. Um, and with the advent of things like shade agents, um, with the with the with intents, right, we're you should have the ability to abstract some of this away. And when we say, it's more like obfuscate, right? You should be able to obuscate some of this complexity to the end user. So, for example, if my wallet holds five different assets, um, and I

99. 50:48

    need to transact with the network, you know, um, at some point in the future, having agents that could go out and tell you like where's the cheapest fees are, where the fastest stuff is. I'm I'm still convinced that's going to be on on near, but um, you know, uh, you could or maybe be able to pay your fees um or your native fees, which is cheaper. So you could use your, you know, soul, whatever, you know, to pay those fees if you had them in your wallet, you know,

100. 51:13

     options like that. But, um, yeah, I I I think the fundamentals are are still going to be the same, right? And it's going to be how the app developers, um, figure out ways to leverage that back-end technology like in intense, like uh, multi-chain in a way that the end user doesn't doesn't need to really know about it, right? So, I have an NFT marketplace. I want to mint an NF N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N NFT and like how do you want to pay for this,

101. 51:38

     right? How do you want to pay for the mint? And you know and it your wallet your near wallet is connected to the marketplace and you pick from one of the assets and you transfer that asset and and and you're done, right? So yeah. Um yeah, I don't think this is I think all this is doing is expanding our our dev's ability to to literally interact with multiple multiple chains being being

102. 52:01

     more chain agnostic. Yeah. Right. and creating something that is gonna have a wider appeal which then broadens your audience, right? So, for sure. So, yeah, I think I I think that that the fundamentals are there. Take a look at oneclick connect. I uh some other people have learned from it and uh yeah. Yeah, I think that that's a really interesting point there uh around like the fundamentals haven't changed. So if you're looking to build a particular

103. 52:26

     product, stuff's there. What what we have seen though is better, more efficient ways to do things, cheaper way to do things, things that provide a better user experience. So the goal I feel like for someone just my opinion coming into here is let's not try to build everything yourself. Let's leverage what's here. Let's leverage what the infrastructure already provides you both at the protocol level and

104. 52:55

     beyond and really streamlining your product. Think about like what's your end goal? What are you trying to do? Like you said, you're trying to just buy an NFT. Great. All right. Here are different options. Now, instead of it just being a simple transaction, hey, maybe you add in the ability to pay for it with any, you know, any token. Now, that's the next step, but you don't have to build that yourself. Those pieces are

105. 53:17

     here. So that I I I really like that approach like the fundamentals haven't changed our building. Um we we really just made it uh more streamlined and stuff like that. Josh, what do you guys think about some of the stuff here? Yeah, like well you know I kind of like answer your question like you know where do you get started? It's like you know I I don't know like if you like if you

106. 53:41

     were to go to like npm and like all right I want to create a React app. All right look at all these packages. Which one do I import? like where do I get started? It it seems so like or you know I'm going to the grocery store you know where do I get there's so many choices here it's difficult right it's difficult to say like you know what do we want to hone in on because it's like near

107. 53:57

     doesn't really have like this we're just doing this one little thing like it started out as like okay let's just make blockchain development easier both for the developer and both for the user let's make it quick and easy to develop.

108. 54:07

     Um, and it's been like an evolution of that of like trying to just, you know, focus in on little areas and make these certain things easier to build with and easier to develop. And we have like this large ecosystem of people that are have that have different interests and have different areas of expertise of like, you know, proximity is focusing in on the DeFi stuff and they really want to, you know, focus in on like multi-chain stuff. And then you have it like oh now we have these chain signatures um folks

109. 54:31

     that are like oh wait we maybe we could do this around MCP and you know then we have near AI that's like you know spun up and and um trying to make that easy as possible to you know develop develop agents and and you know just a couple lines of Python I can get an agent up and running. I have free some free inference and you know so we have a lot of stuff going on but it's kind of like this evolution of an ecosystem. Um, and it's kind of hard to like, you know, like like, you know, going to

110. 54:56

     Disneyland, what ride should I ride first or what am I actually trying to do? Uh, but yeah, it's like, you know, hopefully you come here with like a problem that you're trying to solve. Um, and if you're trying to solve that problem, yeah, definitely docs.org is the best place to start. Um, and if you can't find your your issue there, you know, there's a little helper thing, you know, feedback, you know, hit that button there and a team of uh deval engineers, we look at them every week

111. 55:20

     or, you know, periodically even more than that. Um, seeing, oh, someone couldn't find something. Let let's let's make sure that we can we can find that. And if you don't find that there, there's a a treasure trove of Telegram groups. You could see if you go to just our GitHub, GitHub near um you know, there's a developer um support button and it takes you to this folder and you got 20 different groups of different areas of things. Um you know, we're

112. 55:43

     talking about that like how could we consolidate? Well, it's different groups of different people that want to build different things and want to focus on different things. So, it can be definitely a very tall order to to say where do you start as a developer? And I guess um it's it's starting by what's your problem and it's like more questions that I have for you. It's like what are you trying to solve? What are

113. 56:01

     you trying to do? Um and and ultimately like the holistic goal here is for us to create more simpler ways to integrate you know more simpler like little packages or little examples that you can like plug and play Lego blocks of you know making it more and more simple for you as a developer to build something and for a user you know abstracting away the complexities of blockchain. I don't really understand and maybe you don't even need to know that you're operating on a blockchain and the developer um can

114. 56:26

     can you know make an application that is giving you the benefits of things and can tell their users hey I'm going to give you you know this is what what what my application will do this is why you know it's secure or you know you know do their own um attraction around um the use case that that they're trying to show but you know don't worry about all these complexities you don't have to manage all this stuff you know I can do this for you kind of thing so absolutely

115. 56:51

     absolely Absolutely. For old, you got something to I have I have a shorter but more abstract answer. Sorry. Be curious. Like if you want where to start, start to be curious and uh you you will find a ways. No, and I I I do think the part of that that goes back to what Trenton was saying, like there's so many things that kind of exist in pieces already that if you want to just go experiment, you know, take a weekend, take it take a couple nights, go experiment with some different things.

116. 57:23

     It's low lift. Uh you can really get into it pretty quickly and without having to code everything yourself. Between that and AI, I mean, you could be off and running pretty quickly uh with no problem. Uh I do want to end on one last story here I think is relevant for builders uh and especially if you're looking around agents but in more so than even just that but you know really looking at um different payment options

117. 57:52

     and near worked with Coinbase on this new standard for internet native payments. Um this is still a you know work in progress. I definitely think if you haven't seen in our episode uh issue number 61, the most recent one, uh it's worth kind of going through reading through this, seeing how it works with the near intense demo. But just again, I think as streamlining more and more

118. 58:17

     payments to me feels like a great way to help bring more non-native crypto users into whatever product you're building, the more opportunities you have, whether it's for an agent or whether it's for something else, the more that you can kind of really leverage that. And they're they're really basing this off of a lot of off USDC, which again I think feels more comfortable to a lot lot more people,

119. 58:43

     right? It's a dollar is a dollar is a dollar type of thing versus what am I speculating on? Stuff like that. You guys have any thoughts around this? Yeah, I do. Uh well, first of all, not not uh the whole world is using dollar, right? Uh just just a reminder.

120. 59:02

     Really? Are you okay? Oh wow. Yeah, thanks for a reminder. I Yeah, I was Yeah. So that that that could be like as equally confusing as as as equally, you know, uh like for some people using dollar could be as confusing using Bitcoin from in their realm. Uh but they the the beauty of uh of the blockchain world that we can basically mimic any uh currency there. Uh and the um what I wanted to say when I first saw the standard I I was like oh so we are

121. 59:42

     um in a way we're going by spiral of uh evolution here because if you remember the early days of the internet we paid per megabyte so we kind of paid per per packets already uh but they were not uh the uh like business lo logic uh driven but just datadriven payments. So like the more data you consume and and send the more you pay. Um and this this is a new iteration of uh opportunities to pay per content per engagement. Uh and there

122. 1:00:19

     are a lot of uh um social platforms that are um bringing this up with uh um pay by like by this uh um um yeah interaction sponsoring your the creators sponsoring the businesses that you are you care about. So this is the nice uh uh improvement and potential change in the uh approach for monetization uh through uh tiny microp payments um imagine you would uh uh sponsor Wikipedia when you're reading

123. 1:00:58

     the article and etc etc. So it's um interesting approach in my opinion and uh we would need to think through the new monetization models for this to leverage. That's something that I wanted to add here. Yeah. Anything else end on that? Strong note strong note to end on. I like it.

124. 1:01:23

     Uh well thank you three uh so much for kind of coming on sharing your knowledge going through what kind of wants to happen in the ecosystem. Uh there is so much uh each and every week we have a full newsletter that comes out to summarize all of this. Uh the subscription link is down below. Uh definitely check that out. You can stay up to date on all of that. We'll continue to go over news things that we think are relevant as well here live. Uh just as a reminder uh again and Josh and

125. 1:01:55

     Trenton kind of hammered this home, but uh if you have questions, if you want to get not sure where to get start building, jump into one of the groups on Discord, on Telegram, ask a question. There'll definitely be somewhere someone who will jump in, not even just us. It will be can be someone from the community as well. It's really helpful community who can jump in and help you

126. 1:02:13

     from there. Uh overall, uh I thought this was this was great. Hopefully everybody learned something and we will be back next week uh same time. Uh we have a few different things planned coming up this over the next month that I think are really great for developers and so we hope to see you back then. But until next week, I'm Joe. These are my wonderful guests and we will see you uh same time next week. Thanks everybody.

127. 1:02:39

     Bye-bye. Thanks everyone. Thanks everyone. Byebye.