The next phase of Hyperlane: Permissionless interoperability

Hyperlane makes Permissionless Interoperability a reality by launching the next phase of its vision. The aim is to drive the adoption of different chains, create more liquidity, and eliminate the gatekeeping that clouds interoperability from the first day.

Hyperlane highlights that the update extends the vision of taking the benefits of interoperability to the expanding universe of chains. With Web3 eyeing wide adoption as well, it is safe to assume that Permissionless Interoperability by Hyperlane will be a boon to the industry. The Cosmos IBC Protocol inspires its design.

Hyperlane’s Permissionless Interoperability has a number of new features, such as permissionless deployment, sovereign consensus, and warp routes.

Permissionless Deployment enables users to stack to any EVM chain without requiring assistance from the Hyperlane team. Sovereign Consensus gives power to the users, enabling them to customize the security measures to filter harmful transactions. As a matter of fact, users can go on to build their own security modules for the application.

Warp Routes allow users to wrap and move assets permissionlessly to any chain that Hyperlane supports.

In the time to come, Hyperlane has announced its plans to launch Interoperability-as-a-Service. Since the team cannot deploy on each chain individually, it is looking to connect new chains to the network in a permissionless manner. The process will be potentially streamlined to bring the entire timeline to a single day. Because of out-of-the-box permissionless deployments, users will be able to build and deploy app chains or rollups in a single day.

The proof-of-concept of Hyperlane is already live with Celestia on the testnet. Users can explore the possibilities and launch rollups and interoperability at any time.

Interchain has yet to be explored securely; nonetheless, this remains a top goal, with basic security in place to protect the network and projects built on it. It is known that a significant amount of the issue is derived from the inability to send value to new chains. There is a limit to the risk since users need permission from applications to send a message or perform similar actions.

The risk is currently isolated by Sovereign Consensus by allowing users to specify their own security parameters based on Interchain Security Modules. The default version of the module enables applications to accept communication from well-established network chains in a secure manner.

In other words, users control the extent to which they can communicate with other networks or even if they want to extend the communication.

The ability to filter threatening transactions is more likely to serve the best interest. For instance, a limit can be set to prevent the movement of over 15% of the liquidity. Needless to say, the figure will differ from one app to another.