Beyond Bridges: How the Open Intents Framework Enables Unified Cross-Chain Execution

Transcript

Hello. Hello [clears throat] everyone. Thanks. Thanks for being here. Um today I want to present to you something very inter- interesting. Um which especially if if you are around interop or if you are a developer uh could helps the Ethereum community. It's called Open Intent Framework. Uh well, a little bit about me. I am a software developer. I'm build open source code and I work at Open Zeppelin mostly building up off-chain components.

Um during the last months I have been working directly on OIF, especially the the solver the solver that we will see in a minute. Um well to to begin with what OIF means in in general. Um every time we talk about a framework we know that we are talking about set of tool not for the end users or the end users will be developers and or or agents or uh but not not for final like uh common human human being. So, that's mostly OIF is is infrastructure. Is

something that helps um helps the L2s the developer help help to have something more standardized um that could lead us to to improve the UX. Um in it's uh it's open source like all the components that we have is completely open source is ready to use. In- Intent are the central component of of it. And this facilitate adoption between the different L2s the the mainnet but is not exclusively for for Ethereum.

Um at the end we will see like that we have different reference implementations uh for all the component we would see. Um until we get to understand what this is about we have to start from the first day of the Ethereum. When we um when we decided to go for a roll-up uh roadmap at the beginning we have something like this. We have to use the canonical bridge. We use it we have wait for the finality. If we for example want some ETH on Linea you use like USDC.

Um so you have to do all these sequential steps uh manage the gas and handle failures and wait like minutes um in some cases hours to reach um the the layer two and then and the then do the transaction where we want. And then uh protocols emerge and start using intents and different providers and they solve a little that problem, right? We we use across um some aggregator Li.Fi um all these different uh protocols and they solve that problem. They we do

it like in a minute once just just a few clicks and that's it. We we have like my full transactions uh already done. But what's the problem with this? Um This has great product but but when you wanted to do something like that want to you become a solver we call like provide liquidity um it's a little bit difficult because have this um engineering complexity and isn't open source. Basically you have to ask them to to um put it in the you in the UI and so on.

So So um that's let us to to answer the question. Um we see that's intents resolve that problem. So, what what is intent in in in the first place? Is is what we see before like in a traditional uh way we we have to the um like say specifically and and sequentially we what we want to do. Like use this pool this leap hatch and follow this path. And in intents is a difference. You only express your outcome like I want to swap 100 USDC.

Please give me the best possible ETH. And that's it. It's that simply I I express what I want. And that's is the center of Open Intent Framework. Um what um having said that what we got? Remember we talked about the this different protocols. What what these protocols have is like complete these components uh like completely isolated. If you have you have a a solver specifically specifically for for one protocol and they have their own network and well and they're all in in only one wallet. So, this is

isolated components and with OIF we like take advantage of of these components all together. And if I want to up for example a solver I want to participate. Okay, I use this standard. We I use I simply build on top of it and we have already implementations that you can simple uh run by yourself. And we have we ended up with a really good UXs in their in term of um adoptions in term of liquidity.

And this is a representation of or the step of OIF or the of the flow. Um these are the main components when we use an intent. Uh we initialize with the with the user or the agents uh or the or this entity. This is the off-chain infrastructure and and imagine we we have like a network A and network B. We want to to move funds or do a transaction. Um well, we initialize we quote the solver answer reply with the intent data. We review carefully. Um we we can send directly an off-chain intent by

signature uh or we can do it by by your own like open the in- the intent directly on the network. This go through the input settlement that we also going to see in the minutes because this is a a set of different tools. Of course with the contracts. Um and the input settlement would take care of the of the escrow of your your money or the transactions. And the same solver will be listening or could be a set of solver listening that intent that you put it there.

Uh and of course in a in a security guaranteed way they if if they think that is profitable because they don't of course mostly don't do it for for free with a few fee they fill the intent in the output seller and then start um using oracles. And all of these components are completely adapt- adaptable. So, you can choose between five to 10 oracles right now but we want we want more oracles.

And what is that is done you the the oracle with will send the the thing data to the other network. And then the solver uh in a minutes could like uh validate the proof and get their their money back. That's the the simple flow of OIF of an in- intent. Um but we we can go deeper. What Open Zeppelin is building but also this work is a conjunction with between Li.Fi um across the Ethereum Foundation Wonderland team that he being here.

Uh so this is the most um this is the the most central components that we have right now. We have the smart contracts the solver and the res API res API. Uh we have more components like uh Wonderland have built uh uh SDK that work work with the with the res APIs. We have a a standard uh 7683 that will follow that standard and we we simply have to use the SDK.

Um To begin with the smart contracts as I mentioned is really modular and and extensible. So, you can choose it. You're not tied to one implementation but we have many. Um we have the input and this output settlers that um you know, escrow your money um where you have to use it. We have the callback for composability so you can add more complex um functionality. It's not only like okay, I want just to do a um a swap. I No, perhaps I want to use it in a pool. I only in seconds I could have like a completely cross-chain transaction.

Um we have different score option. We we have like um um wrestle flag from from Uniswap people something called uh oh I forgot the name. Um the compact. And for a score we have for permitted transactions and um so uh it's like 8004 if I'm not wrong. And as I mentioned before we have different oracles. We lastly implemented cross cross-chain broadcaster with the help of Arbitrum Foundation.

That's that's And so you have like the same guarantee as the canonical bridge. Um of course you have Yeah, you can trust uh many actors within that. The solver um when I started the talk I I mentioned the solver. This is a really complex It's like it's the really complex to build. If I want to run something and is is not easy to manage balance, manage different assets, um you know, use different solvers. So we we have built a really modular solver that work with many assets.

Um we have uh [snorts] work of course with the the contracts of OIF are fully integrated. Support multiple tokens and support multi-mode networks. Uh also worth worth mentioning that if I just want to switch one implementation for other I could do it um simple as that. If I for example trust this oracle and I don't want to use this um for five for not five for finality I just go and and change it.

And how we integrate this? Because we needed an standard. So uh again with the help of many partners we develop with a minimalistic API. Uh when we could like quote submit your intent and they gave us that we try to be as flexible as possible but also as minimal as possible. So this like is the is the here of of um of the of OIF.

If we want to like more protocols to integrate OIF this the only thing that they have to use is just uh the first API if if you are building some something by your own. But of course if you are um if you want something like already done we have uh the many reference that you can use. Uh well, when we were building all these components we realized that was really difficult to communicate directly with a sol- with a solver. So what we think is okay. Perhaps I want some aggregator like as a the protocol aggregator we use. But for a solver so we on top of it

we build an aggregator. So that the aggregator do the hard job for you like you only quote you get many quote from the solver and dependent independent or or dependent sorry of the what you want perhaps I do something really fast or perhaps I want to choose really um secure. So depends of what's your desire you choose your your oracle and you send them through the aggregator and then you simply use it.

Um we have also um wallet that we are building. I think um Wonderland people is is working with it. Um it support uh base intent protocols. And and yes, this is an example of the aggregator. You as a client you just get the quote. The aggregator communicates with different um solvers and you just get back with the information and the client used to send the the intent sign it or if they want want to like send directly because this when we when you quote

something you can just sign the intent and and send it directly by to the chain. Okay so once having said that what's OIF really wants right now that we have built like all these components like ready to use because it's all what we have seen is like infrastructure ready to use. We we want more more um L2s we more rollups. We want more protocols using OIF.

We want to expand the the the capabilities of the solver. Uh it's it's it's up to the developers to contribute to to the contracts to the solver to the aggregator. Um so we want that we we want that use of of the community. Because we we have built a really strong product that um is is uh is being audited is secure, is trustful. Um we also want more protocols uh to to be compatible as I mentioned.

This is not only uh use OIF but protocols could use could adapt could use a callback uh to to start using OIF. We more we need more dApps to to integrate intents. We need more oracles. I mentioned we have like five, six, seven I don't remember but there is many other in in interesting protocols wanted to join. Well I at this point I I was about to present a a demo about an intent but I I have bring a problem with my computer.

So uh this is a QR if you want to see the or contribute to OIF. And yeah. Thanks for your time. Any questions? >> [applause] >> Thanks Naim. Um yeah, I was wondering if there is any incentive for running a solver if if there is any fee that users pays to the solver in order to execute an intent. Uh yeah.

Yeah, that's completely up on the it depend on the of of how what Perhaps I am an L2 and just want fast uh instead of instead of people like using the canonical bridge I want people to use because people want like fast finality. I just want to move. So perhaps they want to run that and improve the UX and they don't charge you a fee. But if perhaps I am an other actor I just want to use um gain some fees from doing that I I run a solver.

Um also worth mentioning that OpenZeppelin could like uh they take your your old infrastructure and we will run a solver for you. We are running a solver for for for one L2 and we we can do that for you if you want to like lay offload that responsibility. Any question? Okay. Thank you.

>> [applause]