Putting Intents and Users Together by Abhimanyu Shekhawat | Devcon SEA

[Music] hello everyone I hope I'm audible yeah all right uh I a Manu and co-founder of ok protocol and I'll be simply talking about how we can make intents actually approachable for end users so to start with I'll simply tell you like what intents actually are and to put it simply like in the easiest way if you want to do something or achieve something on the chain and you don't know how to do it or you are not sure how to do it in like a most optimal or efficient way you can find an in solver who can do it for you and once they have optimal solution you can simply get it executed now the problem here is if you give something totally different to the end users they are very reluctant to try it out V P protocol tried to like give different user flows through and users we did a lot of user experimentation and the conclusion was if we give a user flow that is not uh standard or what user is not familiar with they won't try it so how do we solve for it then well part of it is like already work in progress like we get intents being used in existing user flows uh you can take a look at like Unis swop x c swap or across where you already see like intents are being used but a user may or may not realize it but it improves the efficiency or like the rates that they are getting the Second Step should be or can be something like improving existing flu or simplifying existing flu I'll give example for this but I'll just cover the third Point as well first uh creating completely new intent based application that should be the last step where there are totally different flows and which are using like declarative input as a new paradigm but now coming back to like reduce steps and simplified flows so for this one let's take example like there can be a dab that requires a very specific token on a very specific chain and you simply have something like die on optimism and you don't know how to get to that very specific chain or get that very specific token so how you do it uh you can start with something as simple as putting a button in the dab saying hey on board my user in or bring my user in the right State and behind the scenes all these erc's and EIP would be used to get it executed just like how it happens like in normal transaction like you click on a button you see a m popup saying sign it and you can be done with it but behind the scene what should be happening or like how you can orchestrate the entire thing is you can start with the IP 7702 that would go live really soon where a user can leverage any smart contract wallet implementation without actually deploying it to their address through eoa like they can send the transaction through their normal metamask or like the normal wallet they usually use and they don't have to transfer their assets out to another smart contact wallet they don't have to deploy anything to another smart like deploy another smart contact wallet they can just start readily be using it you can abstract gas and all the other complications using like efficient transaction burnd Ling through that comes with 4337 you can also make the entire thing interoperable like if a user wants to use a safe implementation or a ion implementation or something else you can use 7579 what 7579 does is it gives you a plugin standard that can work across multiple dabs so multiple wallets so what a dab can do is create a plugin and that can work with c and byon wallet or the zero Dev wallet and dab can just whenever user comes inep can just plug in their plugin to the wallet and uh have no vendor lock in at all and lastly when your intent requires something like a cross chain execution there is ERC 7683 DS from unisoft and across which defines like how the standard of across chain message should look like uh if there are multiple intent solvers working on both sides of the chains or like all the chains that intent is supposed to be interacting with uh this defines like a clear structured object that says hey this is supposed to be done on this chain and this is supposed to be done on this chain and that can be leveraged to uh get an intent executed across all the chains so to wrap it up for the users The Experience would be as simple as uh just clicking on a button and saying uh I want to use my diet to get this very specific asset and as soon as user clicks on it and hits sign all the intent solvers do their work and lastly it's all gets executed through a very any specific smart contact wallet implementation using 7702 uh well that's pretty much [Applause] it thanks a Manu all right we got time for questions please raise your hand if you'd like to ask one this is lightning talks you got to think on your feet or I guess you're sitting down think on your butts all right ready and go almost so about that hi one question on wallet interoperability you said that you could expect DS through 7579 to interact with the contracts but each smart contract account is developing their own SDK with different capabilities so is that possible and also how can we expect apps to create their own custom plugin to interact with different contracts and connected to that this would any way achieve interoperability but not portability of the same account across DS so I was us these two aspects thanks yes uh the way I think that it this can be easily done is something like a DB can create their own plug-in so if you as a user come with a safe wallet dab simply puts their plug-in into your wallet and then dap knows what the interface for the wallet is going to be because they can get those transaction executed through their own uh API not AP end points but contract functions so uh they can just start calling the contract functions they know from the plugin but if a user comes with let's say byon me wallet next time they can just plug the same plugin into the byon me wallet as well and they can expect the same interface again so it's sort of like you create your own interface how you want to call the smart contract wallets and whatever wallet implementation a user comes in with you just plug your plug-in into it and execute whatever you want and that's it you don't have to worry about yes you can do it without going through SDK you can simply make the smart contract calls it uh I think it's e your other option is getting totally vendor logged like with 4337 with 467 users got like dabs got completely vendor loged if dab wanted to interact with safe wallet they had to like interact with explicitly with safe wallet and if a user with with bonom wallet would come they would know how how to interact with it perfect all right do we have another question somewhere in the audience I know you're all curious people you want to know more yes okay what do you can you hear me yeah I think okay what do you what do you think the kind of substrate is going to be where intents actually get posted and propagated too so that solvers can find them M there are a few different players who are working around this thing uh we are working around the same thing uh there is anoma there is khani the idea here is one one of the solvers gets an intent and they propagate it to entire network with the Hoops of there will be more intent solvers who can solve parts of it or like the entirety of it so with us it's just like one solver getting it and propagating throughout the network and all of them putting in their solution with something like a num khani it's like a solver fulfills partially and puts it out on the network and others can pick it up and solve the rest of it but it's a work in progress yeah got to think