Building with Hyperlane Interoperability Framework I Eda Akturk

Great. I think we are live now. So, I can start. Um, I'm basically going to take 20 minutes, 15 minutes to talk about Hyperlane's open interpability framework. So, if you know about Hyperlane, this will be like a refresher.

If you don't know anything about hyperlane on interperability, that's also not a problem because we will be covering like a from a ground up. So I think it should be fine for anyone with any knowledge of um the blockchain world. So uh for a quick introduction, my name is Eda and I am part of the team at Hyperlane. Uh I work as a developer advocate. So I think this is my third ETH global events with the team and today what I'm going to be doing is giving an overview of the blockchain interoperability ecosystem and then I'm going to be talking about specifically what you can do with hyperlane what tools you can build out and then I will also go over like the bounties we have so then you can have like a good idea for what you can build for the hackathon.

Does anyone here know about hyperlane already or okay we have a small audience but I think it's live streamed so maybe there are more people watching or will watch afterwards but I do want to give a quick introduction so when you think about interropability um what I usually think about is I go to DeFi Lama and I see like there is a whole spread of chains that you can build on today and the question becomes okay like we live in a multi-chain world but which chain do you choose which chain do you work with um and not only are there like multiple chains but there are multiple roll up as a service platforms where you can easily spin up your own chain too. So when there's like a very segmented ecosystem uh what you need is like some kind of glue in between which allows you to talk with different chains. So then you are not like just in your own ecosystem and yeah what does like this sparse ecosystem mean for users? Well, it definitely means that interropability between roll-ups is sparse and highly fragmented. So, this means like you have assets living on one chain but not on the other.

You have a lot of user friction when you need to like change between wallets. You have a lot of disconnected applications. So if you want to build an application on base then that usually like lives on base itself and doesn't connect to like you know the other uh chains and when I look specifically at Ethereum what this means is that when I'm transacting with Ethereum is that I'm switching between networks. So it doesn't really give a best like the greatest user experience when you want to build an application that lives across multiple chains. Like as you can see here like this wallet is connected to like seven networks and whenever you're on which network you have to switch.

So that's kind of like not the best user experience especially when you think about like your own web two banking application which is super easy. You have like PayPal or like other applications which allow you to transact super easily. uh and the goal with all the interpability efforts is to make Ethereum feel like a single chain again. So what we're trying to do is we're trying to provide the tools and infrastructure so that you can like do all the interactions on a single chain and then that will like carry the interactions on the back end to the other chain. So you don't need to worry about like which chain you're on as a user uh or as a developer as well.

If you have like all the tools to easily connect to the other chains then that means you can build like crosschain applications without being limited to a single uh environment and that is exactly where interpability comes in. So uh what we are trying to do with interpability as hyperlane and as you will see like with other interpability players is that we are trying to make it so that you have all the tools and not just tools but you also need like more infrastructure so then you can have like a connected blockchain ecosystem and I'm actually not only talking like specifically Ethereum as well but this means you can connect to like Salana or like Cosmos or other ecosystems as well and that is exactly where a great segue into hyperlane. So what we're doing at Hyperlane is we are building infrastructure for interperability. So tooling and infrastructure to allow you to send messages across chains. And the biggest use case of that today is asset bridging.

And I will get to a bit more details on like the stuff we are building. So then that will be helpful for your hackathon projects I hope. And also introduce the bounties we have so then maybe you can like build through them. I know when I was a hacker that that was the most like interesting part to me. when I came to talks uh but I do want to give a quick overview.

So hyperlane is a permissionless interropability protocol for crosschain communication with modular security. That is a mouthful but I will break down every single point over here. So what I mean by um what I mean by permissionless interperability protocol is that hyperlane is fully open source. You can deploy it to a chain that it's not already on um by free like free of charge. You don't need to do anything.

You don't need to come to us. You don't need to talk to us. Um, but what this means is if you do it yourself, you do need to run your own agents. So, I guess the value out of like Abacus works, which is a team behind, is to allow you to like run all the agents byelves. But for the purpose of the hackathon, like let's say you're working with a chain that doesn't have a hyperlane deployment, you are free to go ahead and do a hyperlane deployment.

All open source. We have the guides to set up on a new chain. Uh that means you also have to need to run your own agents which we will get to in a bit as well. And then crosschain communication I think we covered that quite a bit is you have one chain you have another chain and you want to like send messages between them. As I mentioned the biggest use case is asset transfer but don't like it can be more like general like any kind of message can be sent between chains and then modular security is like most people um especially once they get into interoperability they come to ask they're like okay but how is this like bridge secured like if I send a message does this actually come from this sender or like how do I know that the message was actually like uh untampered and reaching my my you know new chain that is exactly where the modular security which we call ISMs interchange security modules comes in.

Uh so you have different building blocks for ISMs and I will get to that in a bit as well. But yeah so we talked about interpability on any chain or rollup. It's permissionless. You can go ahead and deploy it yourself today when you if you want to see the chains that hyperlane is already deployed on. You can go to the hyperlane registry.

Hyperlane is on over 150 chains um as of today and you can go over there to see the exact number and what chains it is deployed on. You will also see like the mailbox configurations. So if you want to connect to one chain you will need that like contract addresses over there to see which address you need to talk to. Modular security we will talk about it in a bit as well but basically uh it is we do have a default security setting which uses the multisc ISM module but you are allow like not allowed but like you are able to extend that security module or build out new security modules for the hackathon as well for example and simplified crosschain communication. A lot of people want to c communicate crosschain and if a lot of people like do it from ground zero that will take so much time and replicated efforts.

So what we do is we provide those building blocks. So then not everyone has to build it from like ground zero. Um and this includes like our TypeScript SDK if you want to talk with like different you know hyperlane infra infrastructure components. Um as well as the agent infrastructure that we are running modular security. So I touched on this a bit uh but the way security works in hyperlane is that we have these like Lego blocks which you can choose from that are called interchain security modules ISMs.

By default most warp routes today use the multisig ISM but I think actually like building a ISM module is a great hackathon project if anyone is interested in that. And well the default ISM which is the multisc ISM as the name implies it basically checks like for signatures. So it's usually like a two out of three configuration or any kind of configuration you set. Uh but you can be like hey I actually want to use like zk proofs for this. How can I do that?

So that's where you can go in and you can build your own ISM module and kind of submit it as a project and the architecture. So I mentioned mailbox, I mentioned like relayer, I mentioned like validators. How does this actually fit in and what can I build with it is probably like the question like most people think. Um so to talk a bit about the hyperlane architecture overview is basically the origin and destination think two chains let's say like base and ethereum mainets just like for making it a bit more concrete. Um you have the mailbox contract deployed on these like on these chains.

Uh basically mailbox is like your interface into a new chain. Uh when we say when I said like we are on over 150 chains that means that we have like a core hyperlane deployment which includes like the mailbox contracts and like the extra ISM settings for that chain. So once the mailbox is deployed and the other core contracts are deployed that means that all other hyperlink connected chains can talk to them and this is done by a standard mailbox contract. So yeah, the mailbox is I guess you can see it over here as well like the sender sends a message to the mailbox and then likewise when you look at the destination the message is first received at the mailbox like your interface into a new chain is via a mailbox and then so when a message arrives to the mailbox what comes into into play is the relayer. The relayer is like an offchain agent which carries a message from one chain to another.

Now it doesn't do like any security checks. That's where the ISM, the interchange security model which you see over there comes in. But the relayer is like a off-chain agent which takes a message and delivers to the other side. And then once the message is delivered then what what the destination does is destination verifies that the message was actually coming from that sender and that is done via the uh interchange security module. by default as I said like if you look into like a multi-IG ISM over here that would mean you also have like some validators running in between uh that attest like hey okay like this message was from here like send a signature and when you get like a two out of three that's like valid so then it reaches the recipient but yeah this is like I think a good overview of how the hyperlane architecture look like you have core contracts that are deployed most important I guess is the mailbox contract if you have a mailbox and like all the extra gas con like how you pay the relayer etc.

are the contracts we call as IGP then you can talk with multiple chains and yeah what we provide is actually like not just this architecture but we want to make it easy for people to build so we have some tools which you can directly leverage without being like hey I don't want to actually like build any infrastructure components what can I do do you have an SDK you can directly use our TypeScript SDK and okay so I want to talk a bit about the applications right like I mentioned the overview you but like what does this actually mean? What can I do out of the box by ease like just easier? Uh and I guess the main one is hyperlane warpouts. So hyperlane warpouts are leveraging the hyperlane infrastructure that I just talked about for asset transfers. So when you look today the most like used uh application for crosschain communication is asset transfers and hyperlane warp routes are basically like a collection of contracts that make it easy to do that.

So when you deploy this architecture, this doesn't include like the core ERC20 contracts or like standard token contracts where you want to build a bridge like a mint and lock bridge from one end to another. But that is exactly where hyperlane war browses comes in is that there are standard deployments that support various asset most notably like ERC20s for you to transfer assets between chains. We recently not that recent but like been 3 months or so launched hyperlane warpouts 2.0 O which also do native rebalancing. So let's say like you make a hyperlane warp out between base and arbitum.

Uh but now you want to add one more chain. So you're like I want base, I want arbitum and then I want like optimism opt. And then you want like you have collateral on all these chains and you want to natively balance it. That's exactly where hyperlane warpouts 2.0 come in.

But they have like a rebalancer agent which rebalances the collateral between these chains. A cool project is that we currently do rebalancing for USDC uh oni using CCTPv2. So if you are like hey like I want to build like rebalancing on other assets or other chains that would be actually like a cool packet project which I've been telling to people coming to the booth as well. Um but yeah you can totally like build an architecture which does like rebalancing for hyperlane warrats 2.0 know because that's currently not something that exists.

And then hyperlane warp types. Um yeah, you can have like native tokens, collateral back tokens. I'm not going to like go into detail, but you can basically if you want to do like a native token hyperlane war out or a collateral like a USDC token, uh you can do that. You can have like a a version where you have a collateral on one chain and then you mint a synthetic like create the synthetic representation on another chain. So there are different types of hyperlane warpouts that you can leverage.

When I said USDC like it's usually on most the chains already. So that's like a collateral to collateral transfer. But let's say like you have a new chain like I make a new chain called spaceships chain and then that spaceship chain doesn't have you know um a native asset from like doesn't have ETH already. So I can create like a synthetic representation of that spaceship chain or like I can create like a a new asset there. That is exactly what synthetic ERC20 is referred to.

And then yeah there's al actually also like I didn't think of this before but now that I'm looking into the slide there's also specialized hyperlane warp routes which uh one of them we have 5 minutes left I'm getting the warning. Um we have yield routes as well. So when you want to like transfer I assets directly into a vault. So that is like yield yield routes. You can build an architecture which extends the current yield routes we have to like multiple deposits or like multiple yields.

Um this was something I did not think of before but would be a great hackathon project too. And then I'm going to move fast because apparently I have 5 minutes left but this is a simplified hyperlane warp contract flow. The difference you see over here is that you see like there's the EVM hype collateral and then there's also the EVM hype synthetic which is just like examples of the ERC20 contracts which we deploy for making this asset transfer work. So it just like adds like a few more contracts than what you had in the original architecture to make it easier since like most people use asset transfers that makes let's make asset transfers easier with the architecture we have. So that's kind of hyperlane warp routes.

Another feature you can use or application of hyperlane is interchain accounts. These are interchain accounts basically enable a contract on one chain to interact within contract on another chain. So when we want to make like changes to like basically let's say you have like a hyperlane warp route and you want to extend it to multiple chains. So if you have like if you want to directly make it from an interchain account that will make it easier cuz you can just like make that contract interact with all the other contracts on the other chains instead of doing that one by one. So interchain accounts are a cool feature which you can use.

I think it would be pretty cool to like build a hackeron project with them too. Um yeah like they're something which which are more new and more used internally. So it would definitely be a good uh use case to work with interchain accounts. And then ISM I mentioned quite a bit. This is a security modules.

I'm not going to spend more time here since I don't have much time. Uh case study we have like a few case studies on the documentation. You can have a look. Uh well super stops is a really good one because it uses interchain accounts, hyperlane warpouts and open USDT which is like a stable coin for the superchain ecosystem. [applause] Um, but yeah, you can have a look to see how like the architecture leverages Hyperlane for swapping because I mostly talked about bridging, but what Beldum does is they do like swapping with Hyperlane's infrastructure.

And then ETH global, what do we have right now? We have 10K bounties for three categories. I'm going to go to the categories. We will be at the booth all weekend. Uh I think like from 1:00 am to 7 am there might be like online discord support.

So you can join the developers channel for that. Uh we have quite a bit of people from the engineering team. So you can come to us for debugging for like idea help um any kind of questions you have. We will mostly be at the booth. I'm not exactly sure how to explain where the booth is but you can walk around and find us somehow.

And then our bounties uh 10k bounties across three categories. Best use of hyperlane. Best infrastructure. Best interchain app. The best interchain app self-explanatory.

An application that is interchain. Best infrastructure maybe something with the rebalancer with the agents with ISMS. Best use of hyperlane. It's again more general. Um for example, you can also use the TypeScript SDK if you want to like use hyperlink in your DAP or if you want to like build an infrastructure component that would also be cool.

Um yeah, these are three categories we have. If you want deeper um questions, you can definitely come to the booth. Basically, any project that leverages hyperlink in a meaningful way will qualify for a prize. And we are hiring. So, we're hiring for a senior protocol engineer and a senior Rust engineer.

So, if you are interested, we would love to talk to you at the booth as well. Um just want to call out that we are hiring for two roles. And yeah, they're mostly we're mostly looking for people with New York or London preference, but also like looking for remote. But yeah, and that's all for me. I have 2 minutes left.

Uh happy to answer any questions. You can scan the link for our documentation. Um yeah, and you can find me at the booth with other people there as well. And yeah, thanks for coming. Uh if there are any questions happy to answer them um if not maybe it will take some time to process the information and you can come later and I can answer them later on too.

How hard is it to write the security module? I mean that really depends on what kind of security module you want to write and what kind of skill set you already have. Like if you want to write a ZK security module, you can do that. If you have like already expertise in ZK uh but if you don't have any experience with ZK, then that might be pretty hard to do. So um but yeah, it really depends on like how much experience you have in a certain field that you want to write it.

You can actually like look into our documentation to see examples because they also vary a lot. like there's like an offchain it's called like offchain ISM which verifies information that was offchain to make sure that it's correct as well. So there's quite a few things you can do with security modules and um yeah so I wouldn't say like for me to write a zk ISM would definitely take a long time but if you are confident with it you can definitely do it much faster. I think that's all for questions. Um, I guess we can

Yeah, I guess that's all from me today. Thanks, guys.