Building with Hyperlane's Interoperability Framework I Eda Akturk

[Music] Hi everyone. Uh excited for the last workshop of the day. Hopefully not everyone's super tired because the hackathon didn't start yet. But um what I'm going to do is I'm going to give a oops I should stand near the microphone, right? Okay, perfect.

So, uh, what I'm going to do is I'm going to give like a 20 minute overview of Hyperlane, what you guys can be building, and then explain basically like some housekeeping rules for the hackathon, where you can find us, some support. Um, and I know that some people it's their first hackathon, so it will be like more overview and kind of um, explaining like the idea behind Hyperlane and how we got to where we are today. Um and hopefully it'll be like a compact presentation for 20 minutes give you an idea of what you can build and yeah without further ado let's directly get started. So a bit about me is I'm part of the team building hyperlane called abacus works. Uh I do developer relations.

Uh I've been in the web3 ecosystem for quite a while. It's been four years now. Uh and actually my first hackathon was ETH global New York in 2022. That's when I transitioned like full-time into the industry. I was working more as a software developer now more as an educator but yeah I hopefully like you guys will really enjoy your hackathon experience here as well.

Um and so to talk about hyperlane hyperlain is a framework for building open like interoperability applications and the way like the way we look at the blockchain landscape today is that we live in a multi-chain world where there are different layer 1 blockchains and different layer 2s. Uh so Ethereum ran into some scalability issues. So then that's why we see like the rise of all these roll-ups uh like optimism base um any different rollup as well and also with like rollup as a services getting more like easy to build with you also see the rise of rollup as a service platforms. So this is kind of the reality of the blockchain ecosystem today. And when you look at like how many different networks exist is that it kind of makes a lot of sense to have like some protocol to talk between them.

And that is exactly where hyperlane fix uh fits in. And just even like to explain the like core problem is that when you have all these multiple networks, what you see between them is that there are a lot of disconnected apps. there are fragmented assets like your assets can live on one chain but you want to make like a interaction on another chain. So what you usually do is you go through like multiple hoops on like one network to transfer your assets first and then swap to another like there are a lot of like fragmented assets and yeah this causes like a lot of user friction uh moving just slightly past faster keeping track of time and this is kind of like an average experience like how it looks like transacting on Ethereum multiple networks kind of confusing swap between everything um and the goal is to make Ethereum feel like a single chain again and I actually kind of want want to go even beyond the sentence and say that make the whole blockchain ecosystem feel like a single chain. So then you're not only connecting Ethereum layer 2s but also like you can connect to different layer 1 networks as well.

Uh that is exactly where interpability comes in. So uh I hope now it's not just a buzzword but there's some meaning behind what interpability means and why we kind of need interpability to make Ethereum or like in general the blockchain ecosystem feel more connected again. And um I think I'm walking like talking slightly fast so I'm going to go slower. I know this is 20 minutes so I'm kind of rushing myself. Uh but this is exactly where hyperlane comes in.

So hyperlane is a framework for building open interoperability applications. So what this means is that if you want to build an application that talks between different layer 2 networks and also major layer ones, you can use hyperlanes tooling and infrastructure. So let's say you're going to build like a DeFi application that wants to talk across like five six different networks. That's exactly where you would be like oh like let me use hyperlane and uh yeah so to kind of I will walk through like the components that make it possible as well. So it's not just like an abstract uh definition but simply put Hyperlane is a permissionless interoperability protocol for crosschain communication with modular security.

This is a mouthful so I'm going to break it down. Uh so first of all I said permissionless uh permissionless means that anyone can run the infrastructure and everything is open source at hyperlink. So you can completely like uh host every infrastructure component yourself and run the tooling as well. So um the second component is modular security. So hyperlane has this building blocks called interchain security modules.

We call them ISMs and basically they are kind of like le uh modular building blocks and you can plug and play according to your security risk tolerance. So you don't have to go with the default security option but you can build different security options depending on like uh how you want your application to work and maybe just to make like this a bit more concrete in like if you're building like a game you might want speed and like less security for example. um so then you might opt in for something more fast but if you're building like a financial application then obviously like it has to be like some more security so it might take like a bit of longer time um and then the last step is simplified crosschain communication so yeah as we mentioned like hyperlink gives you out of the box tools and infrastructure to move assets between chains and to allow general message passing and I'm going to talk a bit more about how the infrastructure is broken So I kind of want to double click on modular security because I think it's a very cool one and we specifically have an infrastructure track where you can kind of experiment with building an ISM module yourself. Um but these are like hyperlink security logos as we call them and they're essentially like simply put like smart contracts that verify that the message was sent from where it's where it is told that it's been sent. So in a more like uh in a different way to explain it is basically was this message actually sent by this person.

So you can kind of use like different security mechanisms to verify it. Uh you can use like uh multisig modules you can use like zk security etc. Um and basically we don't have like a specific implementation which everyone has to use but we allow like the applications to choose their own security preferences and the architecture how does this work and probably more importantly what can I build with it. So hyperlane overview uh hyperlane today is connected to over 150 chains and you might be like what does it mean to be connected to 150 chains? This means that the base core uh contracts are deployed in all these chains.

So you have an entry into these which we call the mailbox contracts. So if you're like I'm building an application between base and optimism, you can go to the hyperlink registry, see the networks we're connected with and both of these networks are in there. So you basically have like a like the mailbox essentially like an API and access into that network itself. So you can see over here over here as well you have the mailbox contracts on both chains. So they are your interfaces into all these different networks where hyper where hyperlane is deployed means like where the mailbox contracts are deployed and where the relayer runs.

Um and you can view all this in the hyperlane registry on the documentation. And secondly, uh I want to kind of double click on the relayer component that is an off-chain agent which uh carries the messages from one chain to another. Uh it's open source. So you can either use like uh hyperlane's hosted relayer service or you can like deploy one yourself if it's like not running on a certain chain. You can like it's available to run by anyone who wants to and then so essentially what happens is that a sender sends a message to the mailbox on one chain.

It's carried by the relayer to the destination chain. Um and we are given that. So the mailboxes are like basically smart contracts deployed. Uh the relayer is the offchain agent that carries the message. the recipient gets the message and then there is the interchain security module which basically verifies that the message is like uh adhering to the security requirements of that chain.

So uh interchain security modules might also use like some other agents like validators if you're using like a multi-ig module you can like use proofs of validators to verify that message was sent from a certain chain. uh but it can also like do basic computation like anything which you kind of want to configure. Um so this is kind of like an architecture overview of how hyperlane looks like and I kind of want to double click on a few tools and components that you can use or more like more the features that we built out because after we built this architecture we realized okay most people want to do like similar use cases. So we should have like easier building blocks for people to do these kind of similar use cases such as asset transfers. Uh so that is where like the different hyperlane features will come in and one of them is hyperlane warpouts.

Um so hyperlane warp routes are essentially what you can use for asset transfers between chains. So simply put they're like a collection of smart contracts to route to like route tokens between chains. Um on top of what we saw in the previous diagram I think there's another diagram here. Okay, perfect. So, there are like a few extra smart contracts that are deployed directly when you deploy a hyperlane warp route.

So, um you can transfer like a token like make an asset transfer and ERC20 token transfer between one coll like one chain to another chain and depending on the hyperlane warp route type you choose. It can be like a collateral to synthetic route. It can be a native to synthetic route. Like you have the different options which you can choose. And um so what this allows you to do is that let's say you have like your token on on a certain network let's say base since I gave the same example a bit earlier and you want to have like it on polygon as well.

So you can create like a hyperlane warp route to have your collateral token from base to also be represented in polygon or optimism or like almost all the chains that hyperlain is already deployed on. And just to make sure I don't miss anything. Yeah, these are they support various assets including ERC20 and ERC uh 721 tokens for certain compatible chains. I do want to mention that hyperlane warp routes are not just for EVM chains but you can also do SVM based warp routes for like a Salana transfer or an EVM to SVM transfer as well. So something which you can use if you will be building crosschain applications uh any kind of tokenized assets you can have representing on different chains and yeah this is hyperlane warp routes as I mentioned there are different types of hyperlane warp routes from native token transfer collateral backed synthetic etc you can go to our docs to see I do want to make a addition I don't have the slide here but there is also hyperlane warp routes 2.

0 O, which I think are a cool option to be building with at the hackathon as well. What they basically do is they allow you to have multiple uh chains as your origin and destination as well. So in this example, what we see is there's like one Ethereum and one base. Ethereum is a collateral chain and base is the synthetic chain. So let's say you want to have like two uh like two origins for a certain token, like two pools of certain tokens.

you want both base um like or ethereum and optimism and then you also want to connect to bass. So you can basically have like balancing between all these different pools with hyperlane warpouts 2.0 and again you can check the docs for that. They're available under the hyperlane warpout section but I just want to make a specific call out that it's not just like one to one chain to one chain transfer but basically you can have like two chains going to like settling on a certain um chain to make the transfer as well. Uh the issue before was when we worked on it is that when you have like two different uh liquidity where you want to source it from is that you need to somehow like balance the tokens between them in case there's like a rebalancing like let's say you have like Ethereum and Optimism but on one the tokens are finished because they're all like transferred to the other chain for example.

So Hyperlane Warpouts allows for like native rebalancing. So once there's a rebalance it will automatically trigger like a call to swap certain assets. Um yeah, so like they're like uh something we recently launched. I think it's been like over a month and you can check the docs to build something with it. It's the first time at this hackathon with Hyperline Warpaths 2.

0. So might be something cool to do. And then secondly, interchain accounts. Um so I'm basically talking about like the different building blocks of what you can use with Hyperlane. And the second one I want to mention is Hyperlane interchain accounts.

Now I'm not going to go into super much details because I also want to do like a hyperlane warpout demo if I have time. Uh but interchain accounts are another uh tool set which you can use and basically what they do is they enable a contract on one chain to interact with any contract on another chain. So when you want like you can use them for crosschain execution enabling contracts to trigger function calls on different remote chains. Um it's worth noting that hyper interchain accounts are on EVM only at the moment. So uh you can definitely use it to make sure like you like so that it allows you to run a function call on a destination chain without having to like go through the hassle of like building all the infrastructure yourself.

Um I'm going to give a case study in the end which uses interchain accounts. uh Velum super swaps they recently launched and they use interchain accounts to actually like make the swap single click for a user which basically swaps the assets and make the transfer your for you as well. Uh but hopefully that case study will also make it more clear and give you like some idea of what you can build with interchain accounts. grab my water and then again I kind of want to like call out ISMs one more time. Um I'm not going to so much be here for much details but basically ISMs are responsible for verifying that the messages are secure and it's a key component to hyperlane.

So you can definitely build something around ISMs, build a new custom ISM. We have uh we have an ISM marketplace on our hyperlane documentation which shows you what are the available ISMs. Uh essentially they're basically like some smart like standard ISMs that were developed by the hyperlane team. Uh but then there are also like community built ISMs which you can see there as well. uh you can see the status and you can see kind of what are the ISMs available what you can do with them um and yeah so ISM are not just something which the core team builds but anyone can actually build and use them for according to their security requirements and the case study so I do have three minutes left but uh I have the well I don't have the link here but once you Google uh drum supers swaps you'll basically see it on their website and on hyperlane blog as well.

But what they use is I think this is a cool case study because it doesn't just use a single hyperlane tool but it uses interchain accounts hyperlane warp routes and open USDT which is another one which I didn't mention but open USDT is a stable coin launched by hyperlane chain nick and cello. It's basically an interoperable uh stable coin that allows you to transfer yeah USCT between the different chains it's deployed on. Um and that's what drum supers swaps uses. So it uses hyperlane uh warp routes. The HWR is hyperlane warp routes to bridge assets uh to different chains.

It uses interchain accounts to reduce multiple transactions. So like swapping and like to execute like a remote contract call on a different chain into a s single flow. And it also uses open USCT which is a spa stable coin that facilitates all this. And that's why I think it's a cool study cuz you can see like different hyperlane uh features used in a single example. And yeah, it's pretty recent.

Highly suggested to look into it. I think it can give you like really good ideas on what to build for the hackathon. Um it's on the hyperlink blog. And yeah, um just want to call this out. And for ETH global New York, what do we have?

Uh we have 10K bounties uh separate across three categories. Uh we'll be here for in real life support. We have a booth downstairs. I don't exactly know how to explain but I think it's like actually like just down here or like in the end. Uh we'll be there for uh in real life support and then we also have remote discord support.

So you can join the hyperlane discord under the developers section. You'll see ETH global New York hackathon. If we're not here we'll try to be active at the discord. So please do feel free to ask your questions to come to us and uh yeah we'll for sure like try our best to work there and then you can scan the QR code. I believe it goes to the documentation if I'm not mistaken.

And I do have two minutes left. One minute. Can I do two minutes?

Really? I actually didn't realize that. Well, I guess the core like problem we're both trying to solve is the same. So, interoperability between chains. I think there are like different routes we took in like the infrastructure decisions.

I guess like what I can say is hyperlane is on uh over 150 chains which I believe like layer zero is more like on not as many chains from my knowledge. Um and we have most like all our like not just most but like all our components is open source. So you are able to like run the relayer yourself. You can have a bit more custom configuration from uh what I know. And um yeah, I guess it's kind of up to the use case you want to do or like how many chains you want to reach or like how much like different uh building blocks you want to switch in and out, but yeah, kind of I didn't know it was just before.

Um that's funny. So I I know I have so little time yet, but I kind of want to show how to deploy hyperlane warp routes. Can I do that or do we close?

I guess I can't unless someone tells me. So you can use the hyperlane CLI to do this. So all I need to do is I do a for hyperlane warp in it which initializes a hyperlane warp route for me. Uh you can go onto the docs to see like the hyperlane CLI which you might want to use to build like a hyperlane warp routes or if you want to use a hyperlane TypeScript SDK you can do that if you're building like a crosschain application. Uh for interchain accounts, you'll directly need to talk to the contract.

So like all this information is available in the docs. Uh and if you can't find the information, you can find me and I'll show you where it is. So I'm going to select mainets. Now let's say I'm not actually going to deploy this because of time. Let's say I choose base and then I choose like what network should we choose?

Like let's just choose something like well let's choose Ethereum. I'm not going to deploy this because it's I don't want to deploy to mainet but then I click yes and then I need to like choose an address for this. I'm just going to stick to no. Um and then it asks me so like as we said we need the types for the hyperlane war routes right. So what I'm going to do is I'm going to select like a synthetic token on base and that will like a sorry not a synthetic but a collateral token meaning a token that is already like an ERC20 deployed on base and then I'm going to create like a synthetic representation on it on the second network which we chose Ethereum because of time constraints but we're not actually going to deploy this so that's fine.

So I choose collateral and then I need to enter the existing token address on base. So what I'm going to do is I actually have like a workshop on GitHub for this. So I know because of time limitations we're not able we're not going to be able to finish this. But if you go over here to the hyperlane developer workshop I have over here already the FI token I believe. So I'm just going to copy this.

You can go over here. I have like a developer workshop of hyperlane warp routes to see how it works. If the link is avail not available, I can post this on the discord as well. So you have you'll have access to it and then I just simply paste this address. I enter the desired owner address.

It's this address. I'm going to click no for this um to move fast. So what I did was I said like hey I want to use like this collateral token that is already on base to be the root and then I'm going to like create like a synthetic representation on another chain. So I click synthetic for the second one and it asks me hey is this correct? I click yes.

Basically it created like all the configuration for my hyperlane warout. Uh I did it by running hyperlane warp in it. I believe the next command we run is hyperlane warp deploy and this will ask for the conf like the settings of what you need to deploy and it will automatically deploy all the like warp routes um contracts that we saw on the second image. This is going to ask me for my token like my private key. Uh it asks me I believe this was like fi Ethereum.

I think it's at the end and then it asks me for my private key. Now I'm I'm not going to continue to deploy this because I know I'm already past time. But basically you need to ensure that you have the gas to pay for this. And then all it does is it directly deploys you your hyperlane war routes. And then what this means is that now you have one collateral token on like you basically it creates you a lock box which locks your collateral tokens and then mints synthetic representations on another chain.

And let me actually like head over to the hyperlane docs to see to show you where you can find more information as well. So if you go to the hyperlane docs you'll have everything I talked about. You have over here under applications hyperlain warp routes and the interchain accounts. I basically just followed this guide on hyperlane warp routes. I think it's like get started bridge a token guide.

Uh and all I had to do was once I have the hyperlane cla I can create create like an asset bridge between any chains that hyperlain is deployed on. If hyperlane is not deployed on that chain well then you can actually go to the guy to deploy Harperane on your own chain to deploy it first. So let's say you're building with a network which doesn't have a hyperlane deployment, you are definitely able to do that as well. Perfect. I think I'm a bit past time, but benefits of being the last one presenting, right?

[Music]