[trustless://eil] Ofir Eliasi - Abstract the Hard Parts: A practical demo of Stitch

Transcript

Firasi, chief builder at Stitch, giving us a demo. Everyone, big round of applause. >> I'm off. Okay, you got this. I don't see my stuff.

Okay, good. Thank you. Hello everybody. Um, so my name is Afil. As already mentioned, I'm chief blockchain officer at Keros uh that secures 250k users uh for already three years. Uh besides that I recently um helped the foundation team the account abraction team uh with the EIL project um and did like some kind of u uh design partner building some real DAP on on the the platform. Um just a bit about me as a context. Uh exposed to

account obstruction couple of years ago as a um strategic researcher with by economy. Got bullish on account obstruction. Then it all out uh it told out after that as a startup building intent solution for uh for users based on account obstruction. But there also I suffered from a lot of uh bad behaviors experience uh that later solved with EIL and eventually as I said um helped the team um fine-tune and test the project properly um that is actually mean building the product uh as um EIL from my point of view dealing with DeFi and

also involved with a lot of user experience and engineering The idea for uh uh it's actually to have something with way better capabilities and in a way that is abstract stuff uh completely make it very easy to build on blockchain um removing all kind of obstacles that deals with uh um execution on chain and especially when it comes to uh crosschain execution um and of course as I said it's mostly involved with my experience bu trying to build something like this before that handling a lot of account obstructions user experience and to be honest failed um and I think here you're going to see

something that will be much more uh efficient so first I'm going to start with a live demo just to show you what we actually managed to build part of having um um such kind such kind of a solution So stitch is actually an app and I know you have and also um Shahov mentioned that EIL is not um an intense solution but what it does it makes it very simple uh to build such thing in a way that some sometimes people can get confused. So we built something that get the user a very smooth experience considering EIL with a

single uh signature for crosschain multi multi-step execution um in a way that it actually doesn't feel like this. So, just a short connection. I have my app over here uh uh my wallet connected and I'm going to pick something uh for my wallet like USDC and I I can pick what here on this DA like generally uh some funds or like a specific chain. I'm going to pick something from optimism and like 10 USDC on optimism and let's say I want to get get something.

Mhm. Okay. Now it's the outrage happening. We know we know that exactly. Let's try once again. Mhm. Okay.

Stitch up. Yeah, it's messed up. So, I'm going to show it later. Anyway, I'm going to try one more time in a couple of minutes. If not, we have a backup uh issue in that we have issues with the um network generally worldwide, you know, the outreach. So what we did building stitch EL provides an SDK that involved with uh creating an action means any step any execution on chain having a voucher in and out um want to uh uh navigate funds crosschain and a

batch that actually contains multiple steps into it. What we did building stitch is actually creating an additional layer uh extending the EL SDK having more uh uh uh blocks uh like building blocks into it that allow us to do D5 uh actions more smoothly. So you can do a deposit withdrawal and so on on any protocol and extending that. By the way, tomorrow we're going to have a workshop to show how easy is it to integrate or to implement a new protocol, a new action. And on this case, by the way, the efficiency of having such a good developer experience is because or by having uh the ability to solve uh things and walk around stuff

when you need for example um uh to wrap and unwrap stuff uh around wrapped ether and all kind of navigation around u limitation of blockchains. So we managed that very easy. Tomorrow we're going to talk about that. Um and eventually on top of it as I said you build some kind of we build some kind of a logic that user can pick whatever you want on the funds to allocate some funds and decide what will be the the end goal or like the the the the target uh the destination of it funds that can be any D5 protocol on any chain that is supported EVMS for now and it means also from and to those state

destin ations. Okay. So, I'm going to try once again. If not, I'm going to see a video on that. But the idea is to have something like this. It's not working. Okay. Let's do like this. Mhm. Okay.

I don't think I don't think that's the case, but we can try. Mhm. No, I'm going to show a video and I'm going to tomorrow we're going to have something like this. So having such a solution

get you into the place when you actually can do something like this. So the idea is we can as I want to do of course connect my wallet and on some point getting some funds allocated into this. um we want to show um USDC uh case working. So we're going to pick something that is related to USDC Once we did that, uh this was recorded

this morning. So once once we did that and we picked some balance into it, we can now go and pick a destination. Um on this demo I picked a and I want to have like a wrapped ether into it. So now you can see that I'm going to go from USDC on optimism interrupt ether over uh Ethereum. Um you get the full path and then you're going to get some uh you're going to get executed. Uh what you see right now is actually loading the the exact u um code and now it's going to get into uh wallet signature. You can see two user hops. That means we have one for uh source chain and one destination chain. In that case now execution goes on this side. You can see

that on logs optimism execute is executed first and then it's a it's on the destination chain Ethereum and boom you have funds uh secured on destination chain deposit deposited into a um part of it is having the ability to see also on logs that you have voucher created used and eventually executed. You can also see here the supply on Ethereum that is actually the the action of having a D5 involved into that and of course getting into that um in place. So what else um I want to

show here and you can see we created some kind of like a basic explorer over here that you can see that when you have for this transaction what we just uh saw you you can see the us the user ops executing. Okay, according to what we did and also v voucher created um this is like on uh the destination chain and you can see the source chain getting into that that is the user of of uh swapping before and um the voucher that is created afterwards. Um, besides that, uh, the point of we're going to have another demo and

we're going to try one more time, but it seems like you're still off. One second. Anyway, in the meanwhile, what we did is actually to to get this thing in place is the ability to have this buildings blocks involved getting all the options available for the logic and on that case you can just pick what the exact path you want to have. Um for example, if you

want to go from um one token to another on a different chain, that's involved with uh also with swapping. So you can integrate into that any swapping mechanism. We picked one um uh random one, but it can actually have like multiple of those. This idea gives us gives you the the option of getting into any path and uh like actually chain any execution into a single uh into into a single uh signature and on that case having a full path of that involved into uh DI um uh executing into supply on this case into a single chain. Um, so I'm going to see I'm going to show you

like the next one that is like more on the more on the comp complex side of it. So in this case, we're going to do something like a bit more complex. So in this case we again we want to do like something like as I said more advanced. So we're going to pick couple of uh assets on different chains. On this case, we're going to have wrapped E from multiple. I can do it like by just clicking wrapped if uh but on this case since we want to do all of them and not let the the system decide for us, we're

going to pick three uh chains uh wrapped ETH, Ethereum, Optimism, and Abital. And as a destination, we want to have um we're going to pick limitless. In this case, we picked one question random one like uh one more time whatever uh or blue valentine. So you can pick any kind of uh those available onchain uh scene on uh on limitless and you will get the exact uh thing involved with like the amount and so on. So once you have that and we can see all the details over here and stuff is is actually defined we're going

to get the full path of execution like this and I'm going to stop over here just to explain what we are seeing over here as I said um EIL is based on batches that means a batch uh is an execution uh involved multistep on a sing on a single chain in other If I want to have wrapped ETH from Ethereum into uh uh base and I want to make it also USDC. So I'm going to do a swap from W E to base and then to create a voucher. Okay. Uh by the way I can also do the same of having the swap on the destination chain. on this case on

this case we picked the to do the swap on the source chain but it also means I'm going to have the same batch or or a batch like this for optimism and arbitum can be different uh type of tokens different type of amount but each one I can say that each one each one of those arrows actually represent a batch so executing such thing can be like uh happens in a way that is um once I'm signing You're going to see the execution goes and on some point it's going to move into the this is the the sign-in process of course and you can see also here that

we're going to sign four user ops that is actually one per chain that eventually You see some of them already executed and then once they're on the same chain, this is like the destination chain execution. Um, sorry. Okay. Got into this and now you can see like a full path of execution involved with multiple chains. So you can see at the beginning that optimism, Ethereum and arbitum are kind of running in

parallel and then once they are done the base uh batch is waiting for all of them to to be executed and then he claims the voucher and keeps executing the the target chain batch until we get the funds into a limitless um um um protocol. Besides that, what we can also see over here that if I'm going to pick any of those um that actually give us more detailed information about what happens inside it. So you can see the user op you can see the transaction and you can also see the status of the execution when it come when it's actually processing.

So um bottom line what we get on on this uh kind of execution or what we learn by implementing adapt a DAP aggregator based on EIL first we know that we want to get a better user experience a single signature for multiple uh chains and also involve with a very simple uh way and experience for the user that's for sure but what we learned more than that is how easy it to develop on top of EIL based on the SDK or actually to extend SDK, the modularity of what we got or the ability to extend that and create more steps, more building blocks and more um uh path like to combine them into like different path is actually

something that we can um say confidently that was make developers um less involved with bits and bites uh less involved with failures and actually simplify or abstracting the the process for them makes it safer but also easier and faster to develop. Um by the way about that about the capabilities once you have such building blocks and you're involved with um uh simple execution it's actually get you the ability to do stuff that before wasn't available for us from my experience trying that without EIL put me in a position when I can do like stuff like crosschain and swap and also supply very easy and and

safe. That's it, I guess. >> Thank you for that awesome demo. Um, while I get the questions up, I want to invite everyone to make sure they've scanned the QR code here and put your questions in. Uh, if you don't have a specific question, feel free to scan and also look through the questions that have been proposed. You can upvote them and get them higher in the queue.

Give me a moment here. All right. Um, and with Cloudflare. All right. While we wait for technology to do its thing, does anybody have a question that they want to ask out loud? OG status with like a real microphone. All right, I'll hop down. >> Yeah. So, the the UI looks great. Um, thanks for the presentation. Um just one question about I see that in in most cases you did three operations or or three kind of like events or sequence of events. First of all was the origin chain like the liquidity in the origin chain then the destination chain and

then there is some action related to lending or uh depositing something like that. I was wondering if the way it works is like you you send tokens from origin chain to destination chain and then deposit to some liquidity provider or don't some defy protocol. I I didn't understand that part. Could you okay >> kind of explain that? Yeah. >> So on EIL or like mostly SDK terminology you have actions in that case any um transaction or actually on account of suction any user is an action. So, and the basic SDK provides you some of the the actions like creating a voucher, claiming an a voucher and the basic call uh into a contract and even um um ERC20 uh approval. So, you got the basic stuff

over there. Part of what we did by the way, it's going to be uh uh published as a as an open source is to take the base uh uh action and to override it into any D5 protocol that we need and make different types of actions. So supply to a is an action and buying something on on um limitless is an action but also wrap and unwrap wrapped ETH is also an action and of course swaps and so on. So the idea is once you have all these building blocks in place you just combine them into your path um uh into a batch that each batch represent uh an execution on a specific chain and on that case you can have all the batches um into execution and the SDK actually

manage that for you. It's get you it's actually waiting for the batches to be executed and then move to the uh destination chain of execution. It can be involved with multiple uh batches, multiple chains actually. And you can do like more uh complex stuff into it. But what you saw over here is like the ability to create a full path involved with multiple chains into a single execution into a single signature actually. >> All right. Thank you for that awesome question. We have another one. Um from a user point of view, what's the difference between EIL and OIF?

>> And OIF. Okay. Yeah, I like this one. Um but I will explain. Um I think like already said and I also mentioned that that EL is not actually um get you um the full solution of intents. It's actually a way to build easily. What we did is actually creating some mechanism that involved with the intents in a way that user can say I want to go from here to there and uh and execution goes according to what the the engine or the logic decide. So in that case what we actually the way I see EIL is actually enables a lot of concepts a lot of um um uh user experience uh available out there in a way that is more simple you

know you don't even on some cases you don't like need to be like deep into stuff uh regarding blockchain so it simplify the process shorten it and actually makes it more safe >> thank you I'm just checking any other ones have come in what's next for Stitch Well, that there a couple of stuff that we uh see as next step. Uh what you didn't see over here is to have the ability to go from D5 to D5 and I mean like I'm having funds on a um on specific chain let's say uh optimism and I want to I want to take those into a on a different chain. Okay. So that's something that is I think going to take on development uh um um uh perspective

something around like a week or something like that. So extending that can be easily done and on that case you can go uh from um many to many and also from D5 to D5 and also involved with DI to wallets or transfers and so on. So imagine the concept of having a destination that can be your wallet or someone else wallets any D5 protocol uh dexes and so on. And the same goes for the uh source chain source uh um um um state when you can have also defy wallets and so on as a source and on that case you can actually navigate anything to anything on any path. There are more advanced paths that can be uh

uh involved that we thought about having but it's probably not for a short demo is for example how to do like circles. I want to leverage stuff and I want to be like I want to lend and borrow and lend and borrow once again and once again that's also available. We just need to uh put the logic in place and in that case you're going to have it. >> And for anyone that wasn't here earlier can you explain how vouchers work? Okay, about vouchers. Um, so I guess someone else will do that like even better than I. But the idea of voucher is um to get some kind of do like very obstructive and I said like voucher are the ability to set uh to deposit some amount on one chain. Okay. And define what will be the destination chain and get it on the

destination chain uh um the way you want it. So on that case you you need to create um a voucher on the source chain and to claim it on the destination chain and and the magic happens by EIL. >> Awesome. And this one may not be for you but it is in the chat. Um timeline for EIL and mainet >> timeline. >> No it's going to be more of a EIL team thing. Um so in that case big round of applause for that amazing demo. >> Thank you.