Sovereign SDK is the high performance rollup framework for you to build the next Hyperliquid. And it comes with Hyperlane bridging out-of-the-box, so you can start onboarding users and liquidity from everywhere on Day 1. Expansion.

HOW I STOPPED WORRYING AND LEARNED TO LOVE INTEROP The way I see it, hitting the 80/20 of interop requires two solutions: - permissionless bridge infra - permissionless relaying infra Let’s expand on that. You’re a developer. You have a cool app in mind. You want dedicated throughput, and don’t want to deal with a validator set. So, you’re building a rollup. Your app likely requires liquidity to function well. But how do you get it? You can use your rollup framework’s default bridge, but if you’re an OP rollup, that bridge will have significant delays for users bridging out of your rollup. Not ideal. And regardless, you don’t want to be connected only to Ethereum mainnet, but to any other place your users might bridge from. You likely are okay with users going through a lower-security bridge for smaller amounts. So what do you do? You’d ideally deploy a battle-tested, permissionless bridge library that is plug-and-play and supports any execution environment your users might want to bridge liquidity from. That would be ideal. And weird as it is, that library exists, it’s called Hyperlane. It supports EVM, SVM, MoveVM, Cosmos SDK, and now Sovereign SDK. We just had the demo of its integration last week, and it was great. Using it, our users will be able to easily create bridges to whichever chain they want to connect to. Currently, we only support Hyperlane’s multi-sig ISM (interchain security module), which is helpful for setting up simple trusted bridges with low latency — but we’re considering building Fraud-Proof and ZK-Proof–based ISMs for Hyperlane so users can utilize the same Hyperlane integration with different trust assumptions as well. Why am I so excited about this? Bridging is a complex operation. We’ve seen many bugs in bridge implementations that resulted in huge losses. A battle-tested, re-usable bridging library will not only make it easy to connect our rollups elsewhere, but make sure that these connections are robust. P.S. I have no stake in Hyperlane whatsoever, apart from close friends working there. But I think they have the best bridging solution on the market. A permissionless, modular bridging library is extremely useful.