The short answerHyperlane lets any chain or application connect without waiting for a bridge team, and lets each choose its own interchain security module — from a simple multisig to economic staking. The freedom is genuine and so is the consequence: a route is only as safe as whoever configured it, and most integrators choose cheaply.
Best forPermissionless deployment to new chains
Trust assumptionsweight 30%
7.0avg 7.2
Exploit historyweight 25%
9.5avg 8.8
Settlement speedweight 15%
8.0avg 8.3
Chain coverageweight 15%
8.0avg 8.1
Costweight 15%
8.0avg 8.2
this service category average across 15Score = Σ mark × weight. Recommendable to most readers, with stated caveats. Methodology.
| Criterion | Mark | What we found | Source | Checked |
|---|
| Trust assumptions | 7.0 | not sourced yet | not sourced yet | — |
| Exploit history | 9.5 | not sourced yet | not sourced yet | — |
| Settlement speed | 8.0 | not sourced yet | not sourced yet | — |
| Chain coverage | 8.0 | not sourced yet | not sourced yet | — |
| Cost | 8.0 | not sourced yet | not sourced yet | — |
What we liked, and what fell short
Liked- Permissionless deployment without waiting for the bridge team
- Applications pick their own interchain security module
- No protocol exploit to date
Fell short- Security is delegated to whoever configures the module
- Younger protocol with less value secured than the incumbents
Why the marks landed where they did
Traditional bridges decide which chains to support, which creates a gatekeeping problem for new networks. Hyperlane made deployment permissionless: anyone can deploy the contracts to a new chain and start passing messages immediately.
Interchain security modules
Each application defines how incoming messages are verified — a multisig of chosen validators, an economically staked set, an optimistic scheme, or a combination. This is honest architecture: it makes explicit the security choice that other bridges make on your behalf and rarely disclose. It also means the burden of choosing well falls on integrators, and cheap defaults are common.
What that means for users
Before using a route, the practical question is which security module the application configured. That information is on-chain and almost never surfaced in a user interface, which is a gap between the design's honesty and users' ability to act on it.
Record and coverage
No protocol exploit to date, growing deployment across many chains including several with no other bridge support, and active development on economic security modules.
Who should use it
Builders wanting to connect a new chain without permission, and users of applications built on it who can determine the security configuration in use.
FAQ
What is an interchain security module?+
The verification scheme an application chooses for incoming messages — multisig, staked validators, optimistic challenge or a combination. Hyperlane makes this an explicit choice rather than a hidden default.
Can anyone deploy Hyperlane?+
Yes. Deployment to a new chain is permissionless, which is its main advantage for networks that other bridges have not prioritised.
Is Hyperlane safe?+
The protocol has no exploit on record, and any given route's safety depends entirely on how the application configured its security module.
How do I check a route's security?+
The configuration is on-chain but rarely surfaced in interfaces, which is a practical gap between the design's transparency and users' ability to use it.
