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.