Beyond Bridges: Advanced Approach to Build Multichain Apps | Pauline Barnades - Wormhole Foundation

are we good all right hi everyone um let me put this right so um my name is Pauline I am the developer relation engineer at wall and um so today we're going to have a little walk through not just wal is but also what kind of interrupt solution we have out there and one of the thing that um came quite important to me when I started in interrupt is that people assume that interrupt is only Bridges right like this is the main the main idea you have when you're like okay I need to cross I need to go cross chain and uh basically I'm going to use a bridge and I'm going to wrap an asset and that's what I'm going to get well uh there's a lot more solu and interrupt and actually that is really not what I want to deconstruct but I think we should stop making assumption that people fully understand how interrupt uh work and just try to yeah just like start from the beginning and really understand what we're trying to do so yeah that was the intention so be on Bridges and advanced approach of building a m chain app um so these are the goals so basically what's the state of interoperability today and why you might want to build a multi-chain app uh this is one part of my job as a Deval is also to do all the integration support and uh we have very recurrent um question actually when people come and they wonder whether or not they can integrate and also what basically are the best solution um are there so we also going to talk a little bit about that what are the trade-off of using a r assets and uh yeah I mean wmal is definitely also a bridge so I I am not saying having a RP asset is not a good solution I'm just saying this is not the only solution and based on what you trying to achieve in your app uh you might actually have um a much uh most suitable solution and uh how one more product addresses uh interoperability challenges we can have a quick walk through so yeah that's basically what the state of interrupt today so today you have about 40 version of usdc right so um n need to say the liquidity fragmentation is an issue but the ux is an issue um before working at warm Hall I used to work for a layer two op pack protocol and also you had um rapping I mean you had the bridging uh and it was always very confusing for users for people for developer so this is something that has been a ongoing challenge right in in the whole crypto uh World why interrupt well first cross-chain messaging operate at scale and just I don't know if you guys know but um warhall is basically the main cross-chain provider for Black Rock today so um when we mean at scale we mean like institutional scale okay um so just so you see today uh we have about 1 billion messages so when we talk about interrupt we we talk also about cross-chain messaging uh 1 billion is about what has been gone uh through warhole uh 50 billion is the value that's been facilitated by the bridge uh so that is not a small Market I think actually I was looking into some stats and I think combining all the different interrupt protocol we have uh we are about like six like 75 billion uh of um of value that has been facilitated through uh interrupt so uh this is a very important part of this um ecosystem chestin also cross chain messaging is everywhere the idea that you might want to use a bridge just to send your token across uh two chains is definitely a a valid use case but you you see it everywhere there token transfer borrow and lending protocol use it nft use it oracles uh to have actually on chain uh quaring data on chain is very important across many ecosystem uh governance we have uh the Unis swap governance f s is uh going through Wormhole um so that's also very important for voting uh Power uh I mean swap you you name it so it's not just I'm a user and I want to uh transfer my fund um like that there's many many more um use cases uh so yeah why you might want to go M to Chin when you build a uh a product so first is the user growth right you might want and I'm talking by experience because as uh as Dar previously in a in ecosystem usually ecosystem strongly encourage developer to I mean they're basically one native app right they want this app to be fully native in the ecosystem so and then maybe later go cross chain but that is really what every protocol is trying to do now why would you want to make this step so unless it is uh um let's say unless it's uh something that is very important for your application from the beginning which is not always the case and most likely it's not the case but at some point it's very important you understand that your users and the the the audience you're trying to get is probably not on the only chain that you deploy your application in right so user grow scalability tvl grow is very very important and this is why most of the people wants to go cross chain right you want to go where your user are but you also want to go where the money is so if you are deployed on a uh chain and you cannot go anywhere else uh because you're stuck on that ecosystem well at some point you you you might need to to make the move right so these are the most common um question I get usually in a day-to-day basis and I just wanted to make sure people understand clearly that difference and what it what it takes to use ibridge and create wrapped assets rather than deploying token natively multi chain so basically it depends what your project needs do you want to keep a full control of your token contract do you want to keep um uh every single parameter every single like the design the original design you made for your token do you want to preserve that do you want to keep ownership do you want to be able to upgrade uh do you have authority over your your token all of these question are very relevant because most of the people when they come to us they're like oh yeah I just want to use the W Mall Bridge because I want my token up there and I want this to be facilitated uh by the protocol which is a good use case but what happen under the hood when you delegate um your token contract via a for like a bridge like a token bridge and not just warm hole any bridge is that the token Bridge contract will create a wrapped version of your asset which mean that you delegate the ownership of your token to the Token Bridge contract right so basically in a nutshell what it means is that you do not have ownership of your token once you have a wrapped asset it doesn't mean that the token natively that you have deployed previously is not yours it just mean the wrapped asset version that is going to be locked and then minted and different chain this belongs to the bridge because I mean it belongs it it is owned by the token Bridge contract okay so a rra asset version of your token is not owned by you so if you later on decide to change um the metadata for instance of your token what you cannot do because you don't own that you don't own the WRA asset version like that's very important to understand so that is one of the limitation of the asset so if you end up with i talken that you want to keep full control full ownership be able to upgrade any sort of security settings then you cannot I mean it's not that you cannot it's just like you have to know the tradeoff um so this is this is one of the thing we we go over and over at wul and uh I know uh that other colleague in other interrupt solution also have the same question so I just want to make sure that you understand that the best case for you to use a the tok a token Bridge contract for instance is that you have a token you want to make sure that in a few minutes you can deploy it and have it up and running on our portal bridge and then you can transfer that across 40 plus chain very quickly with zero friction and it has taken you very little time and no particular implementation then you use a wrapped asset uh token Bridge uh solution now is this not what you are looking for and you need a bit more specific you have different needs then I can walk you through what kind of solution exists out there okay so what is WL so basically the core messaging primitive is what WL is built on so everything we build on top of warhole is based on this core messaging primitive but the idea the main idea we have is actually to build a very modulous stack so think of warhole a bit like a bit like Stripe Right like when you go to stripe you have many different products right you don't have to use them all but you can combine them all it's very important that if you're a developer our main goal is not to lock you in with wmal like we have no intention of making developer come to us and then they're only able to use our stack and only able to use further products because they cannot do anything uh outside our own uh our on um uh stack you actually can use whatever you want from wal everything is compatible if you want to use for instance native token transfer with connect you can't if you don't need to use connect then you don't like that's basically our philosophies is that the developer use what they need and nothing else so these are the main part I will go through the main one which are the native token transfer which is the main alternative to a token bridge for instance and then I will quickly go over the wormal settlement because it's literally been released about two hours ago and I think it's a it's our new intent uh protocol and it's very cool so let's say you are a developer who is um who is in need you want to deploy a token um n L uh multi-chain and you must keep all authority you want to maybe specify the rate limiting uh you might want to add verifier for instance uh so you cannot really go through the token Bridge basically the token contract because you have different needs um then in that case you will use what we call entity entity is a native token transfer so it's not a token standard that also is very important to understand other interrupt solution out there have their own token standard that you have to basically convert to to be able to use the uh cross chain uh protocol we made the decision to not do this so entity is a very uh flexible framework and you don't need to change anything from your token design right you keep your token design exactly as it is entity will preserve token ownership upgradability and custom customization so basically anything you will want to change after deployment you can also do it right everything goes through a CLI uh if you want to you don't have to but it's uh it's the easiest way and so um you will own the deployment so you own obviously the you have the ownership of your token but you also have full ownership of every uh deployed uh contract with entity okay so security control access role rate limiting post cling Global accounting all of this you can also configure it and I think one thing that people are often surprised with and it's re it's worth mentioning is the flexible verification so what basically is flexible verification is that um to be able to use um any sort of cross-chain messaging obviously we verify that every transaction is valid okay but you can use the standard WL verifier if you want that is not a problem uh however some people for whatever reason often security reason might want to use uh external verifier right that is very important that there's no lock into to Wormhole if tomorrow you want to run your own verifier or you want to run a third party verifier let's say you want to use another protocol that has verifier like axela you can combine that you would just have a different threshold so instead of having only warhole verifying your transaction you can make a okay your threshold is two and two okay like the transaction needs to be verified by Wormhole and by Accel actually um the R Steak E from Lio use that that combo so what they do is that they have the verifier from Walmart but they also have the verifier from Aela so actually it's like very enhanced security there's two main deployment model but again you can add your own if you if you decide so but these are the most common ones so you choose your deployment model either you have a burn and mint model which is the purest form of bridging really so you will burn from on chain a you'll burn your token and then uh it will be minted again on chain B okay this vary pretty much everyone who has a new token use this burn and Min model however there is another one that is um usually most frequently used by by existing token so is the Hub and Spark and uh Hub and Spark is very similar to a lock and mids let's say but what it does is it's better for people who have uh who want to upgrade their original contract like that is a is a better solution for them as I say the modular stack so you can use anything if you want to use H connect is a small widget that we have uh that basically Leverage The Entity uh Tech if you want your own front end you don't have to use it uh everything is is built like this with one home I would just I have four minutes I really want to go over at the the end of the uh presentation so I would just skip that page um we have SDK of course I just want to talk quickly on three minutes about what we just released today so basically we released today uh warmal settlement so it was live about 2 hours ago um so it's the Next Generation suit of intent protocol so what it does is basically if you I don't know if you are familiar with intent so intent protocol is very similar to what across does for instance or uh the bridge and um intent referred to a transaction where a user simply States the intent without having to worry about the details and a solver which also is commonly um called the market maker but in intent we use uh the name solver facilitates the intent abstract away everything else that is involved basically what you are able to do with intent is you can go across chain swap a swap plus an action or and it abstracts also all the chains so it is the fastest today the fastest way to make any sort of transfer cross chain plus action so let's say you go and you want to um make a uh transfer this kinda is very stressful sorry like um so you want to make a transfer from Bay to Solana uh and you want to first um make a cross chain transfer but in the same transaction so in in one click okay you will have to make a cross chain transfer then maybe you want to make a swap because you want for whatever reason uh uh make a swap and then you would have to deposit on a certain um prod like steak let's say uh you would do all of this in one G basically that's what would happen and what it would use is something that we call faster than finality and basically it means that the solver in the middle take a bid accept the bid process the bid before your the finality on the original chain is uh completed um the problem with finality is that it can be very long right on ethereum fense is 7 minutes so when you deal with actually uh defy application you do not have the time uh to wait for those 17 minutes for many reason like slipage and what and so what what you do with intent is that basically you go faster than finality and the solver take the bid it takes the risk and then it take a small trans like fee transaction uh so this is what uh we have uh like basically go live today with so and also if you are a developer we have hackathon bounties so entity is what I just presented uh and also we have any use any build uh multichain dab build with uh typescript SDK or the SDK or any sort of um actually direct core contract interaction will go um and then queries queries is like a very interesting Pro product we have and it's basically for having um quiring data on chain but extremely fast under one second so that is super super interesting if you want to build any sort of that then need like aggregator for instance so anything you need for a full cross like full onchain data uh and it's powered by Wormhole and is it's very easy to use all right so if you are a DA and you want to see any sort of tutorial you can uh uh scan this QR card this is where most of those implementation are done by guide and a tutorial and uh yeah you can find I would also be judging the hackathon and I would also be uh the main person to support uh any hackers so if you have any question uh please feel free to to get my telegram or um time is up okay on my Twitter and I will definitely get back to you thank you very much