Universal Accounts: Smart Contract Wallet for NEAR Intents and beyond

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

1. 0:00

   Heat. Heat. N. Hello and good morning near uh you're tuning in. This is going to be workshop six for the innovation sandbox. Innovation sandbox is the hackathon going on January 26 until February 16th. We are in the last four days. So, this will actually be the the last workshop in our series, but this is going to be a really good one. I'm really excited for it. Uh, let's get a couple of good mornings in the chat. I hope some of you folks are coming in. Um,

2. 1:04

   I've known this team for uh quite a while. I've been following this project for a bit. I think you guys all have too. There bunch of great builders building something really cool. I hope to see that demo today. All right. So without further ado, I'm gonna go ahead and bring him up.

3. 1:22

   Pavl and Pier 2. [clears throat] How's it going, guys? Welcome on. Um, thanks for coming on. I'm going to go ahead and give you guys the stage and then let's get started. Hi everyone. Please take it from here. Hey. Hey. Hey, how's it going? Uh, so uh again as Elliot mentioned I'm Pier 2 and I'm joined here with uh one of our engineers Pavle and we're really excited to talk about universal accounts which is one of our technologies that we've

4. 2:01

   been working on for some time and we're excited to share it with you today. So uh before we dive in just a little bit about us. What is Templar? Templar protocol uh it is the first cipher lending protocol to enable borrowing dollars against Bitcoin or any asset without trusting centralized institutions. So if you're interested you can uh check us out later. But let's dive right in to our example user story here.

5. 2:34

   So, we have Alice and Alice is going along her merry way and she decides that she wants to borrow some USDC on Ethereum, collateralize that with the native XLM, the native Stellar that she has and send it to her centralized exchange account to offramp. Uh, this is a pretty typical user story. And in this case, we're going to throw a little bit of a wrench in and say that Alice only has a Stellar wallet is really only

6. 3:06

   interested in using Stellar and uh maybe she's not too familiar with other crypto platforms. So, what are her options right now? If she doesn't use Universal accounts, the process might look something like this. First, she needs to find an Ethereum wallet that she likes and trusts. She does a little bit of research and discovers there's something like a thousand different options. So

7. 3:36

   wonderful. She goes through, picks one, and then she discovers she needs to purchase Ethereum for gas. Now, this is a problem of course that uh was solved about 2 years ago with metat transactions. Um, but again, she might need to go about uh purchasing some gas.

8. 3:55

   And this requires a signature from somebody, maybe her, maybe somebody else. Uh, maybe she buys it on her centralized exchange and throws it over to her new uh Ethereum account. Regardless, a signature is required. Then she needs to find a DeFi lending protocol on Ethereum that supports uh this particular asset pair that she's looking for. Then she has to bridge over her uh her Stellar to her Ethereum account. This requires at least one

9. 4:27

   Stellar signature. Then she creates the loan on the Ethereum DAP and sends the USDC to her centralized exchange account. And then she does her offramp and all of that. All in all, this requires about four signatures, give or take.

10. 4:42

    And the key thing that I want to look at here is that it's a uh it's not just signatures on her Stellar wallet. In fact, only one of these signatures was from her Stellar wallet. The rest of them required her to do all these signing actions with a different wallet, uh her Ethereum wallet that she's not really so familiar with.

11. 5:05

    What we would really like to switch over to is uh something that looks a little bit more like this. This is our user story with universal accounts and a little bit of near intense magic as well. In this flow, Alice has to simply access the Templar Protocol app, deposit funds, that requires one signature from her Stellar wallet, create the loan, which is another signature from her Stellar wallet, and then withdraw funds, which is a final signature from her Stellar wallet.

12. 5:40

    Notice that we've gone down in the number of signatures by one. And this time all of the signatures were on her stellar wallet. So how do we go about concocting this magical flow? Um I want to go through a couple of our goals here and then some of our non-goals so that we're clear on exactly what our mission is. First of all, um we don't want to require our user to have to create a new wallet or actually any additional wallet at all because this solution, as it turns out, will work

13. 6:20

    with pass keys as well as a variety of crypto wallets. The user doesn't need to purchase gas tokens because we'll have a relayer paying for this in the background. And if necessary, the user still can kind of eject or escape to a near wallet if they really want to. So they're not locked into this solution.

14. 6:42

    And this result is our seamless user experience that we've described. And it should work regardless of the origin chain of the user or honestly even if they don't have an origin chain. They're just operating based on a well, I have my crypto in my centralized exchange.

15. 7:02

    And then we can use a pass key. Here are a couple of our non- goals. We're not trying to do any cross-chain messaging. We're not making the next better or worse wormhole. Uh this is not a multi-IG wallet. Although we might be able to extend this technology to support multisig in the future, but that's not a goal for now. And finally, we're not trying to replace native near accounts at all. This is a different use case.

16. 7:29

    This is a brief overview of the technologies we're going to use in this setup. Metatransactions, as I mentioned before, this is how we're paying for uh gas. Then we're also using global contracts. This was a key unlock for us uh because previously if we wanted to have these smart contract wallets be able to validate this variety of different signatures, it required a lot of code to go into these uh smart contracts. And so they were getting to a point where they were a size where if we

17. 8:02

    wanted to deploy this to thousands upon thousands of users, it would have been kind of expensive. But global contracts allow us to deploy hundreds and hundreds of these wallets for fractions of a penny. And finally, we're adding a little bit of near intense magic on top as well. By the way, if you're noticing that all of these look like they are links, um there are slides that are available. Um there are a couple tweets out there with links to

18. 8:34

    the slides if you want to go and explore these links on your own. Um, so feel free to check those out while the presentation is going on. This is a brief review of the technologies that have done something similar to this previously. There was the NE contract back in 2022. This was before global contracts. And so this meant that in order to get uh Ethereum signatures to work on near at a large

19. 9:02

    scale uh this contract needed to be super minimalistic. So if you go and review this code, you'll notice it's very trimmed down. Uh no near SDK, no uh JSON parsing with Certi, nothing like that. It supported a very limited set of actions, just these five mentioned here.

20. 9:21

    And it was kind of superseded in 2024 by the NEP 518 web3 compatible wallet support uh proposal. And this is where we get those magical seeming uh 0x like native Ethereum account addresses on near. These accounts are getting kind of a special treatment. The wallet contract that supports that RLP execute function that's built into the near protocol itself. So those accounts don't have to

21. 9:53

    deploy it. It's just there automagically. And what we wanted to do is we saw what happened with NP518 and we said what if we could do this for [snorts] basically any signing primitive out there. And that's kind of what we're trying to do here. Um there was an attempt to support pass keys previously.

22. 10:18

    Um but if you see how this implementation worked, we looked at it and decided that um it wasn't quite suitable for our use case. And so that's why we uh didn't go with any of the previously existing solutions and went for one of our own.

23. 10:38

    Here's the workflow that we currently operate with. It's three steps, all pretty straightforward. First, the client signs an action. And this action looks a little bit like a typical Near transaction. Um, but of course, it could be in a variety of different formats.

24. 11:02

    This process actually works for users within your wallet as well. Um, in in which case we just use delegate actions and metatransactions. But that's a little bit less innovative and interesting because that's something that came out 2 years ago. Um, so we're really going to be focusing on how this works for uh non-near wallets.

25. 11:25

    This supports pass keys, so that's built into basically every modern browser these days. Your user won't even need to create a separate crypto account. It works for uh and then we've added support for raw ED25519 uh key pairs. So this works for something like a Salana wallet, SCP 53, that's the stellar standard, and EIP191 signatures, that's for Ethereum and ETH like wallets. Then the relayer takes that action and wraps it in a

26. 11:59

    transaction. So it's paying for those gas fees. So our users don't need to worry about paying for gas fees at all. This really is quite simple on the part of the relayer. All it does is a little bit of validation to make sure that the action looks like it will reasonably succeed. You know, making sure that gas values are set to something that is sane. And then it just calls execute on

27. 12:24

    the smart contract wallet. The contract, it does a basic uh signature and nons validation along with a bit of a domain check as well. Um a domain separator check I should say. and then it runs the action. Note that in this case, because the signature is contained within the payload that the contract is checking, it doesn't need to check the predecessor.

28. 12:50

    Let's take a little more detailed look at the relayer that we talked about in that workflow. It is similar in many ways to the NEP 366 relayer. That's the metatransaction relayer and that's actually where this kind of started. but we expanded it to support signatures of any type and uh of course all of these signature types that the universal accounts contract uh validates as well.

29. 13:19

    One interesting piece is how do we create an account because you know these users they might have accounts on other blockchains or it could be a pass key. So what we went for is a pretty simple solution of a proof of work that's simply signed by the account that we want to create.

30. 13:42

    And then the relayer deploys a global contract which as we calculated is fractions of fractions of a near per deployment. And this allows us to support upwards of 500 deployments per near spent. So this is an extremely lowcost solution. It allows us to uh support tons and tons and tons of users and we barely have to worry about the deployment cost.

31. 14:16

    This is the universal account contracts interface. It's really simple. And that's part of what makes this solution so powerful is that it really in many ways looks a little bit like the interface for querying like the keys off of a normal account. Albeit they're not exactly permissioned in the same way that we have full access versus function call access keys. All of these keys kind of operate like full access keys.

32. 14:52

    The uh interesting thing here is when you deploy a universal account contract, you can execute a few things right away. That's what this execute parameter is doing. That allows our relayer, for example, to automatically add the public key of this account that we're creating to the intense contract. and it doesn't require an additional signature on the part of the user.

33. 15:23

    And then here, this is our execute function that the relayer calls or really anyone could call with an properly signed payload. And of course, that will execute whatever actions are contained within these transactions. There are a few different key management functions here that are marked as private which means that in order to execute these uh you have to go through the execute function here because then of course the predecessor will be set to the contract itself and then a couple of key query functions here.

34. 15:59

    All right, and that brings us to our demo time. So I'm going to hand it over to my colleague Pavle here who has uh some live demo to share with you. Yeah. Hey guys. So uh thanks Pu for uh like explaining how it works and uh I think the best way for users to see this in action is for us to show a demo of uh a use case. Let's say there's a user having some Stellar account. So I just created a Stella account using my freight wallet. I have some XLM but

35. 16:37

    obviously this could be any other wallet like Pasis Salana Phantom wallet uh MetaMask on Ethereum. Uh we we're not limited unless we kind of um provide a matching uh signature support type of wallet. So this one it's a brand new wallet. I have not been using that one that account uh with Templar. So we go to Templar application which is app.mplarify.org. work and uh I can go to my account page. Doesn't matter. I can just log in. So what will happen now if I open I think the network tab. Uh Pavle uh are you sharing?

36. 17:11

    Yeah. Uh I think I am sharing. Uh can you guys see it? Oh, it's the we're seeing the Oh, yep. There we go. Okay, cool. So uh I can log in right now with that account. So I choose Stella wallet my freighter wallet and uh this is like a normal connection to the application with a wallet. So once I do that uh there's a like quick proof of work uh which is allowing me to get some nons and I can sign this message once

37. 17:47

    with my uh stellar wallet again and this will lead us to calling a create method on uh basically calling create endpoint on our re layer. As a result I have a successfully created account. So this is an account that was just created. So what I will do I will go and check on near blocks uh this account which should have been just deployed. Uh if we take a receipt we should see a few seconds ago there was like a new newly deployed near implicit account and now I can use that

38. 18:20

    to basically go and uh borrow some funds right so uh a few things to mention. So let me zoom in a bit so you guys can see this. Uh we did uh make an API call to relay to uh pass the uh type of uh wallet I'm using. Actually this is the type of sign and in this case it's a sep which stands for stellar like signing type and this is my public key. This is my like account on stellar and knowing that we already up front could get the

39. 18:52

    near implicit account address. So basically this is a dress that will control the funds once we get some uh borrow position. So uh let's go and do the following thing. Uh I'll try to borrow funds right now. As you guys can see on my wallet, I do have some stellar. I don't have any USDC. So what I will do, I will go and choose XLM uh stellar. And uh let's use maybe 10 for now. So hopefully I can get something like 0.

40. 19:22

    Let's make it seven. Uh these are the details about the uh position I'm about to create. But I can now use my Stella wallet to deposit these funds. Uh once again, I'm not using any near wallet. So we can see here that uh this is my Stella address and this is my implicit near account ID.

41. 19:42

    So I'll go and try to deposit. This is 10 XLM. So, I'm sending this funds. Boom. That was pretty fast. Uh, let's go and explore. What do we have here? So, we just managed to send uh 10 XLM. Basically, what we're doing right now, we're using uh like intense infrastructure where we uh deposit stellar to our MT balance which stands for multi token balance. And uh hopefully in some time I should get

42. 20:18

    these funds recognized and I could use that amount of stellar uh to use this uh like as a collateral and get some USDC uh as my borrow position. So uh we should wait a bit. Okay, we got this. So we just received this deposit. It's in pending state. I think in a moment it will get uh like resolved state. Boom.

43. 20:38

    Like yes, we have it. So next thing I'm going to actually execute the borrow and what P has mentioned earlier every time the user has to kind of manage his funds there's a process of signing. So I will be signing again using my uh Stella wallet. So this is uh the stuff I'm I'm going to do. Uh I'll just sign it and while we're waiting for relay to process this I'll I'll go and quickly check uh

44. 21:03

    what's going on here. So uh basically this is like housekeeping a bit. The main thing we do send 10 XLM as collateral. So we can kind of uh allow Templar market to know that hey these are the funds we'll be using as collateral and please give us back then uh 0.7 USDC because that's what we want to borrow. Uh so uh happy days. We just got our uh 0.7 USDC on Stellar. We do kind of notify users about some estimated withdrawal

45. 21:37

    fees. So once again, if we go uh to my wallet and we see that we have just uh leftovers of my XLM balance, we don't have any USDC. So what I'm going to do right now, I'm going to withdraw these funds. Again, I'm just using Stella wallet to sign the payload. And uh yeah, what's going on right now? I've signed an intent to withdraw this 0.7 with some minor fee. I should get this as like

46. 22:05

    almost 0.7 to my Stella wallet on Stella chain. And once again, we can swap Stella chain here with Ethereum, Salana, Zcat, like doesn't matter. We kind of uh like this is a crosschain experience the user should eventually get. Uh so uh we're waiting a bit. Hopefully this will not take too long, but eventually once this is processed uh the user will get this uh like funds to to the stell.

47. 22:36

    So we're kind of pulling the status of this transaction. Sometimes it takes a bit longer. So uh yeah like that's kind of when the intent is being executed. Still not there. Obviously this is like a very small amount to to handle but still and here in the like response of relay we can see what was the actual near transaction under the hood that was kind of doing this thing. So I think we did uh successfully kind of uh execute the intent itself. So

48. 23:32

    now it's like to uh intent and I think hotbridge infrastructure to handle that. Uh let me check one last time. Uh it's it's not there yet but obviously I mean it uh it will land eventually on the user stella balance. Uh I mean at this point we've pretty uh obviously demonstrated that uh we can with just the three stellar signatures uh completely conduct all of this within the stellar wallet. And at this point we've just handed it off to Near Intense.

49. 24:04

    Yeah. Yeah. Okay. So uh not to kind of uh waste uh everyone's time, I'll stop my sharing process, but uh with that being said, uh once the funds went, the user can enjoy uh this experience of borrowing using just fellow wallet, just uh XLS collateral. And once again, I I can't stress enough that you can use basically any chain that we support so far. And we we do have a few already and going to expand

50. 24:45

    Yeah, absolutely. All right, so um we're back over here. And if you're interested in uh seeing what one of these transactions look like. I just took a screenshot of one of these uh that just occurred uh yesterday, I think. And so you can see here through just a single signature we can do a lot of stuff uh a lot of stuff interacting with the intense contract interacting with uh oracles interacting with different markets. Um and even down

51. 25:15

    here we're adding a public key to the intense contract. Uh unfortunately obviously uh live demos don't always go completely perfectly. Um, but there's a sample transaction here that you can uh check out if you're interested. Just to go over our future plans for this technology. Uh, I have three bullet points here that we think could be interesting future developments for universal accounts. Obviously, uh, more

52. 25:47

    universality is always going to be good with something that we've labeled as quote unquote universal. Again, we already support a bunch of different uh signature types, including pass keys, and that was a really big one for us because that means that people who don't even have crypto wallets can still use this technology. Uh but then of course, we also support Ethereum and RAW ED25519

53. 26:12

    signatures and uh Stellar standard as well. And as uh as the need arises, of course, we'll add more signature types as well. Second will be uh I think there's an opportunity here with one of these uh NEPs that's recently come in, which is NEP616, deterministic account IDs, if you've had a chance to look at that one.

54. 26:35

    Essentially, it allows you to uh predetermine the address that an account will uh or that a contract will be deployed to given the contract code and a starting state. Right now, we do something. It's kind of like an ad hoc version of this uh with our own infrastructure. So, you may have noticed that the account ID looked something like, let's see if I go back here a slide. Um, uh, well, it's cut off here a

55. 27:05

    bit, but you'll see that it's a a bit of a hash right here. And then, uh, it's like user 0.templ. Is what's, uh, in the background here. And so that's kind of like our it's kind of like a deterministic account ID in that this hash here is determined based on the key that's getting added to this account at its creation.

56. 27:29

    And this will of course reduce the backend infrastructure dependence because we won't need to define that deterministic uh account ID generator on the back end. It will be determined by actually the protocol. Finally, we are looking to reduce the number of signatures required from three to two by using chain signatures to sign intents. So essentially if I uh switch back to one of these earlier slides here

57. 28:05

    um the idea is essentially this withdrawal right here. This is simply signing something that gets sent to uh intents. Well that's part of it. Um, and I we think that we could be able to actually combine essentially these two signatures together by using chain signatures to sign an intent.

58. 28:28

    All right. Are we uh a quick update about the demo? Uh once I stopped screen sharing, I did uh got the funds landed on my Stella wallet. Uh but yeah uh now uh it's just for for the rest of the users to uh trust me on this but you can explore the logs of uh you know uh withdrawal on intense and obviously uh it just sometimes the target chain took uh just wanted to update everyone here that went with that one.

59. 29:00

    That's great news. Uh the technology is still working even if it's sometimes a little bit uh little bit temperamental. So that's fantastic. Thanks for that update. Um and yeah, that is everything that we have prepared for you. Uh again, if you're interested in trying this technology out for yourself, it is live. That demo that Pavle just showed uh showed us was the real app working with real funds. So just go to app.templarfi.org and you can try it out for yourself. the

60. 29:35

    relayer is up and running. You can use an Ethereum account, you can use a Stellar account, uh you can even use a pass key. Um and then of course got to plug the socials. So follow us on X. Uh join our Telegram and star us on GitHub.

61. 29:56

    That is everything. Thanks so much. That was great. That well done guys. genuinely great presentation. I was so excited when I first saw you guys' slides because really you guys are demonstrating something that's incredible. I don't know if you like realize the the gravity of it of what's going on here. Um and uh Pavo, what happened there? That totally uh I I was going to bring you up and I was going to ask if it if it went through by now. I

62. 30:25

    know that intents can sometimes take about a minute to a minute and a half in order to like deposit fully. So I'm going to guess that's that's that's really what was going on there. Uh if you be okay, I'll just screen share. So how for the end users? So like kind of advertise our experience. So I will go to my wallet. Obviously I'll see amount which is not exactly 0.7 but that's uh to the smallest possible fee

63. 30:48

    we kind of notified the user about and eventually the user will see this is withdrawal transaction link. This is uh the actual transaction that is happening on the target chain. In this case it's Stella. So we can go there and see uh yeah like this is the exact amount that was sent to my wallet. Once again I think it's 0.00007 which is the fee. So uh like just double check and that's what we've kind of estimated for the user. We also do have something like uh another approach uh

64. 31:21

    for some chain specifically like to use like omni bridge directly but this is going like too into technical details. I just wanted to share that kind of uh we constantly think of how to make this experience even better. Unfortunately like there are uh like multiple pieces.

65. 31:38

    So from our side you could see the intent was signed quickly. Uh the way it's executed uh hopefully like we can get even a better uh performance sooner or later. But uh yeah like uh definitely understanding all the pieces involved and we will just try constantly to improve the protocol uh make it faster without losing the actual quality that so yeah thanks for giving me opportunity to show that it's actually uh there. So now Ellis can go and use this USDC on

66. 32:08

    target chain and yeah like once uh once the the borrow position is repaid the collateral is returned back as simple as that. Awesome. Yeah, I've tried uh I've tried Templar myself and it's it's a really smooth app. Uh you can use it to borrow against your Zcash, which I think is a really cool thing um out there. But uh thank you guys. The being able to sign a pass key uh or being able to just use a

67. 32:36

    pass key to control multi-chain assets, it's just like amazing. You can eject the pass key too if you want to. I uh want to stay on just for a second just to see if there are any more questions in the chat. Um I did have one question for you guys and I just kind of want to know um so just because it's topical um and we're especially uh with agents I kind of want to get you guys' take on what do you guys think about this with agents using

68. 33:11

    it right now. Something that's that's really hot that's happening right now is ERC. What is it? ERC 8000 something, right? Yes. And 8 and 8128, which is their like message signature is the same thing as NAP 413, I think. Um, but I think that what pass keys, what what's your guys' thoughts? How do you compare about it? What universal accounts for agents versus that type of thing?

69. 33:40

    Uh Bruce, do you want to take this one? Yeah. So, um I guess we have we've been focusing mostly on the uh smoothness of the user experience here. I think that as far as AI agents go, uh this could be something that they could take advantage of as well. as long as they have access to uh you know these signing capabilities it it might make it easier for people to develop uh against this if they only have to worry about

70. 34:11

    say you know managing one kind of secret one kind of signature um we haven't been developing this uh with AI agents as the first class uh target this has been user focused first and foremost we're trying to polish the user experience and make the user flow as smooth as seamless and as secure as possible.

71. 34:35

    Nice. No, that I and you guys done a great job on a user experience, too. I'm excited to integrate this into my own apps. I do think that there is uh I do think that you guys have unlocked something that's pretty great for agents to be honest. I hope that anybody that's tuning into uh this workshop right here, we do have a couple more days into the hackathon. Do check this out. Do you guys have a link to docs that I should share or anything like that?

72. 35:02

    Yeah, absolutely. So, uh just docs.templifi.org. Uh that's our docs link. Let me I got it up here. Yeah, while producing let me also add a bit on top of agents like just thinking out loud the uh those actors could technically go and inspect the market yields for example where you supply the stable coins and let's say if the market conditions change so today I'm supplying for one market tomorrow it's another and obviously like uh doing this in automated fashion if we have an agent

73. 35:38

    that has control over the account it doesn't matter is it universal account is it with just a near account. So having this one maybe you can kind of do some looping and borrow missing assets and kind of see the yield comparisons. Let's say if today there's a gap when you can borrow having lower APR than and like use this to get higher yields just where the imagination can go. So uh yeah, Elliot, if you'll be

74. 36:04

    doing something, please share with us and like I mean we we have our code uh in public space. So yeah, everyone like who is excited about trying this out, please share your results. We'll be happy to kind of uh check that out. Yeah, another thing that I've been thinking about with seeing um some of this activity on Chatter Online with uh these kind of always on AI agents is uh so recently there was a bit of a downturn in the market which of course

75. 36:34

    for people who are collateralizing with an asset such as Bitcoin that can be a bit of a concern because you have to be always on and always checking you know oh what's the price at you know because if suddenly you know the market just has a really bad 18 hours when you're you know at work or sleeping or on vacation or something like that you know what's going to happen to your position. So that might be an option for uh

76. 36:57

    integrating some sort of AI solution where it can evaluate the market and you could have given it some sort of parameters to say hey you know if market looks something like this you know evaluate see what other assets we have in our wallet see if you can you know um recolateralize a little bit on the best position to avoid uh getting liquidated something like that. Um, another product that

77. 37:22

    we're working on is vaults. So that's for like more on the supply side rather than the borrower side. Uh, that's for strategies. Um, which you know if you had maybe an AI curated vault, that could be an investment strategy as well.

78. 37:40

    Interesting. That's great. I hope that uh people anybody that's checking out, please explore these ideas. The docs link is there. There's a lot to explore here on Near. Um, thank you again guys for coming on. Genuinely do more workshops you guys. I could listen to you guys for hours. You're you're really good at the whole thing. It was a great flow. Um, thank you again. Hey, thanks man for us here. Thanks so much for having us on.

79. 38:05

    Yeah, for sure. I'll catch you guys later. See you. Okay, so that one that was great. I'm listen. She could listen to it too for hours. Oh. Um, sorry. Somebody else is in the room, too. Let me just I got to just pull up my one last bit. There we go. Bam.

80. 38:38

    All right. So, that was the last uh workshop in the series, at least until the hackathon goes. Uh, at least until the hackathon ends. Um, who knows, maybe we'll get another one in. If anybody wants uh some some office hours or a last minute uh presentation as we go over this uh last weekend, please reach out, let us know. You got to listen to my spiel one more time. But of course, we are in the last four days of the innovation sandbox. Just looking back,

81. 39:11

    this started January 26, about three weeks ago. Um, we're coming up on this last bit where submissions are going to be J uh February 16th. I don't remember the time off the top of my head. I think it's 20 UTC. Um, and then winners will be announced at a virtual closing ceremony that you should tune in to on February 19th. And then this all culminates in Near Con IRL. That's going to be February 23rd through February 24th. That is in person in San Francisco. Uh you can register

82. 39:44

    online at nearcon.org and find the whole schedule there. Since we're in our last final days, I'm going to be really nailing this in the submission requirements. Um submit to Despot, submit to DevSpot, and you need to do a written project summary, a public repository link, a live deployed URL, and a de a demo video of no more of no more than three minutes. And when you do that, I would

83. 40:14

    encourage you to also post this on socials. Um post it on socials, tag us, maybe do a hashtag nearcon um so that we can amplify it and we can get the whole legion to activate. So once again, the tracks, we got the private web and private life. We're building consumer apps focused on privacy.

84. 40:37

    Near and nearai offer a lot of privacy tools specifically the private cloud cloud. Near AAI uh you can it is a open AI compatible SDK you can integrate into your own app and you can enable private inference unlocks a lot of business use cases. Think about lawyer client confidentiality healthcare uh applications and so on.

85. 41:04

    Also, I want to encourage you, you can take an existing app or you can find an app out there and you can actually just go ahead and integrate the OpenAI compatible SDK and that would be a valid uh submission. Uh we are absolutely open to that second track AI that works for you. So, this is kind of focusing on autonomous agents and aentic payments. So leveraging the cloud, leveraging uh near

86. 41:28

    intents, um maybe taking some of the information that you learned from this this hack, this uh workshop with Templar today to kind of build something that is autonomous that maybe manages your um your lending and your borrowing to make sure that you don't get liquidated as the uh market goes down.

87. 41:50

    Another thing that you could uh tap into is the whole craze with the open claw and the near agentic market. You can go ahead and check it out. If you take your open claw and you send it onto this site market. AI, it will read a skill and then it can know how to bid on jobs and you can win some near. So, uh, not only could you win the bounty by maybe building a project that is, uh, geared

88. 42:15

    towards this, but in the process, as you claim some jobs, you can go ahead and win some gear there, too. And finally, the last track is open society from finest to real world. Uh, this is kind of focusing on real world solutions. So, stable coins, uh, real world assets, tokenized assets, um, using near intents or maybe even, uh, trying to find a application or a solution for your real in-life community.

89. 42:47

    So, and a big uh, part of that that I want you guys to be thinking about is oracles on Near. You can really build uh, oracles very well natively because of a feature called yield resume. So there are projects out there like out layer you can leverage their uh tech uh really easily to kind of build these simple solutions of uh requesting external data on chain.

90. 43:15

    Finally got some prizes $3,500 per track. We're going to have a $2,500 only on bonus. that is the project that leverages the near technology to the best of its ability. There's a lot of really cool near tech talking chain signatures, yield resume global contracts, the uh Pasi signing exactly what we just saw the universal accounts what we saw with uh this presentation today. So, it's going to be a $2,500 prize uh did project that

91. 43:45

    leverages near tech in the most um remarkable way. Of course, two $1,000 crosstrack bonuses and then we have our ecosystem bounties. So all these workshops are available. If you go back, you will find that the second one was with Nova that is a 3K bounty. Nova is uh agent is like a memory solution that leverages near blockchain and uh shade agents TEES.

92. 44:12

    Um they have a bounty out there. Hot pay has a bounty out there for using their hot kit integrating their uh pay with hot which leverages intense. And then also Ping. Ping has a bounty in the same sense as hot um integrate their checkout, their on-ramp, uh their ping links which also leverages intents underneath the hood.

93. 44:37

    This is about that only on near bonus bounty. Yep. The additional recognition for near native capabilities. As we're rounding this out, really pay attention to this. This is how projects are going to be evaluated. The technical execution, so how sound is the architecture? How well is it built?

94. 44:59

    The user experience, how clear is it to use? Uh uh what's the experience like? Is it smooth? Is it uh is it something that you could come back to every single day? Impact and usefulness. Is it solving a real problem? Does it have a credible path to adoption? What's your go to market? Um maybe build a landing page with your projects. That would be a good start.

95. 45:25

    And then the completeness and the functionality. We are looking for live deployed demos or uh live deployed uh applications. We want to be able to use it. We want to be able to explore it. If it's just a GitHub repository, probably not not a whole lot to work with right there.

96. 45:44

    When you're building, everything should uh have a meaningful use of Near. So that includes leveraging the Near AI private cloud that you can find at cloud.near.ai. Near intents, it offers a one-click SDK that you can drop into your uh product immediately and you basically get multi-chain um swaps, deposit, withdrawal across uh a number of blockchains.

97. 46:10

    shade agents which is kind of this idea of of uh running uh running code verifiable execution in a secure environment and then of course the account model chain signatures and global contracts as we saw today there's a lot to explore with the account model and global contracts so do take a look you can find all these resources and more if you scan this QR code here that will bring you to a notion doc you will uh find a load of SDK pays and tools and links and all these type of things that

98. 46:43

    are really here to help you get started as well as the telegram chats. We have a lot of uh uh helpful developer uh devs and uh ecosystem developers here to come and help you to talk to you validate your idea more. If you need near AI credits, we do offer uh $5 worth. So, you just got to scan this QR code and we'll get that sorted for you.

99. 47:13

    Yep. Open to anybody. Uh teams of up to five people 18 years or older. What kind of projects are we looking for? Needs to be capable of running in a real envir environment and should meaningfully rely on Near. And then yes, you can use an existing project or repository, but make sure that uh make sure it uses near and make sure that you made some um meaningful changes within this time period.

100. 47:39

     of course need to give a shout out to PL Genesis. Uh one of our hackathon tracks, AI that works for you is uh we're encouraging builders to continue building. So if you submit to that track, you can also submit to this hackathon that's going on as well. Uh you'll have a chance to uh win a uh a prize as well as access to all the rewards that they have as well.

101. 48:02

     And so without further ado, let's get started or let's get going. We got four days left. Scan this QR code um and go ahead and get building. So, tune in for the last couple days of this coverage. Um and thank you for tuning in for the last workshop.

102. 48:29

     Shout out from the Templar team. Thanks for attending everyone. It was a pleasure. It was a pleasure having you too. Okay, see you guys later. Bye-bye.