Following the release of Hyperlane earlier this year in order to provide the first-ever permissionless interoperability option, this time around, it is the upgraded version, Hyperlane V2. The worked-up version comes with a whole lot of one-of-a-kind and innovative features. Out of the many, these also include a modular security stack, an easy developer experience, and permissionless positioning. It will now be possible to take ownership of, as well as customize the security aspect of one’s own app and permissionless position Hyperlane with virtually any EVM chain.
When it comes to the modular framework of the Hyperlane, it will give the developer the opportunity to plug and play, mix and match, as well as have the option to entirely customize different interoperability stack-related segments. Developers will have the option to personalize their interchain security thanks to the modular security stack known as Sovereign Consensus. Additionally, developers will have the option of selecting from a variety of pre-configured Interchain Security Modules (ISMs) as well as ISMs that may be mixed and matched to create the security stack they need with the help of ISMs. Additionally, Sovereign Consensus will give developers complete control over the selection of security measures.
With permissionless interoperability, a user, with the assistance of Hyperlane permissionless positioning, will be comfortable with the placement of an interoperability stack and bridge choice from the word go. In the present situation, the MVP, in terms of permissionless positioning, provides the opportunity for users to be able to place Hyperlane in any EVM. However, in the imminent future, the plans are to work on the necessary issues and also deliver permissionless non-EVM positionings.
Regarding the overall developer experience, several improvements have been made. The mailbox contracts have been fine-tuned into a single unified mailbox contract. In the present scenario, all that the developers will require is to identify a sole address in terms of sending and receiving messages. There is now no necessity for extended lookups, resulting in a more simplified contract. The Hyperlane Explorer has been brought into V2, along with a fresh lot of APIs, to assist in maneuverability. Also, the domain IDs have been worked on to be in sync with EIP-155 chain IDs.