LogoLogo
  • ⏩Introduction
    • Hyperlane Introduction
    • Getting started
    • Why Should You Use Hyperlane?
  • Permissionless Interoperability
    • Overview
    • Deploy Hyperlane
    • Warp Routes
      • Deploy a Warp Route
      • Deploy a UI for your Warp Route
    • Modular Rollup Interoperability
  • Build With Hyperlane
    • Quickstarts
      • Messaging
      • Accounts
      • Queries
      • hyperlane-quickstart repo
    • Guides
      • Finding my messages
      • Automatically pay for interchain gas
      • Manually pay for interchain gas
      • Choosing an interchain gas paymaster contract
      • Unit testing
      • Specifying an ISM
      • V2 migration guide
    • Explorer
      • Debugging messages
      • Configuring PI Chains
      • REST API
      • GraphQL API
    • Troubleshooting/Developer FAQ
    • Example apps
  • APIs and SDKs
    • Messaging API
      • Send
      • Receive
    • Accounts API
    • Queries API
    • Warp Route API
    • Interchain gas paymaster API
    • Hyperlane App Framework
      • Example usage
        • HelloWorld
        • Interchain Token
      • Solidity SDK
        • HyperlaneConnectionClient
        • Router
      • NodeJS SDK
        • RPC Providers
        • Deployment
        • Interchain testing
        • Quoting gas payments
        • App Abstraction
    • Hooks API
      • Contract addresses
  • Protocol
    • Overview
    • Mailbox
    • Interchain security modules
      • Interface
      • Multisig ISM
      • Routing ISM
      • Aggregation ISM
      • Optimistic ISM
      • Wormhole ISM
      • Hook ISM
      • CCIP-Read ISM
    • Interchain gas payments
    • Staking and slashing
    • Agents
      • Validators
      • Relayers
      • Watchtowers
    • Warp Routes
    • Implementation Guide
  • Operators
    • Validators
      • Guide
      • AWS setup
      • Monitoring and alerting
    • Relayers
      • Guide
      • Message filtering
    • Agent keys
      • Hexadecimal keys
      • AWS KMS keys
    • Agent configuration
      • Configuration reference
    • Running with docker compose
  • Resources
    • FAQ
    • Glossary
    • Contract addresses
      • Permissionless Deployment Contract Addresses
    • Domain identifiers
      • Permissionless Domain Identifiers
    • Default ISM settings
    • Coming Soon: Hyperlane v3
    • Token sources & faucets
    • Latencies
    • Github
    • Discord
    • Website
Powered by GitBook
On this page
  1. Resources

FAQ

Answering the most frequently asked questions about all things Hyperlane

PreviousRunning with docker composeNextGlossary

Last updated 1 year ago

What is Hyperlane?

Hyperlane is the first universal and permissionless interoperability framework built for the modular blockchain stack.

Anyone can Deploy Hyperlane to any blockchain environment, whether it is a layer 1, rollup, or app-chain, allowing that chain to communicate seamlessly with any other chain on which Hyperlane has been deployed.

What are the benefits of using Hyperlane for blockchain developers?

Hyperlane offers benefits for both blockchain and dapp developers.

For blockchain developers, a Hyperlane deployment expands accessibility to users, assets, and valuable state from other connected blockchains on which Hyperlane has been deployed.

For dapp developers, Hyperlane provides seamless connectivity across multiple blockchains, allowing developers to create interchain network effects and liquidity and users to interact with applications from their preferred chain.

How is Hyperlane secured?

Hyperlane is secured by its modular security stack featuring Interchain security modules (ISMs). Developers can configure various pre-built ISMs, compose them with each other, or even create custom ISMs based on their application's needs.

A modular approach to security ensures that Hyperlane will continue to stay up to the latest industry advances in security models.

Who are the Hyperlane validators?

Hyperlane is secured with a modular security stack featuring Interchain security modules (ISMs).

There is no protocol-enshrined security model, let alone validator set. That said, most Hyperlane deployments are configured with a , which specifies the security model to use if the message recipient has not specified an ISM override. See Default ISM settings for more information

What can I build with Hyperlane?

Hyperlane's Messaging API allows dapp developers to send arbitrary bytes between smart contracts on different chains. This can be used to create interchain applications, dapps which span multiple chains.

For inspiration, take a look at some of the pre-built applications built on top of Hyperlane, including:

  • The Warp Route API, which lets users move tokens from one chain to another

  • The Accounts API, which lets users make interchain function calls

  • The Queries API, which lets users make interchain view calls

  • Other Example apps built on top of Hyperlane

Where is Hyperlane deployed?

A list of known deployments can be found at Domain identifiers

What happens when I send a message on Hyperlane?

See the Send and Receive pages for more details

Summary:

  1. An application calls the dispatch() function on the origin chain, inserting the message into the Mailbox's Merkle tree.

  2. Hyperlane Relayers observe the dispatched messages and assemble metadata for the recipient's Interchain Security Module (ISM)

  3. A relayer delivers the message to the recipient by calling Mailbox.process(). The Mailbox verifies the message with the recipient’s ISM, and calls recipient.handle() to deliver the message.

How can I see the status of a message I have sent?

Paste an address or transaction hash into the search bar of the Hyperlane Message Explorer to view details about a message’s status and history.

If the message has failed to send for some reason, there will be error messages indicating what may have gone wrong. See Troubleshooting/Developer FAQ for more information on how to debug an undelivered message

I can send interchain messages with Hyperlane — does that mean live chat/text?

Hyperlane is a protocol designed to allow smart contracts on different chains to interact with each other.

Is Hyperlane a token bridge?

Not exactly. Hyperlane is a protocol that allows communication between blockchains.

Token bridges are just one of many types of applications that can be built on top of Hyperlane! For more ideas what can be built on Hyperlane check out What can I build with Hyperlane?

I’m a developer. How can my team build with Hyperlane?

If you’re reading this FAQ, you’ve found the docs — this is a great place to start! That said, we know that questions arise during implementation, and we’re happy to help you on your way.

What is Abacus Works?

Abacus Works is the name of a legal identity working on Hyperlane.

You may encounter some references to Abacus in older posts and repositories. Hyperlane rebranded from Abacus to Hyperlane in Fall 2022.

How can I join the Hyperlane community?
I'm interested in working on Hyperlane, where can I see job openings?
How can I contribute to improve this documentation?

When we refer to message-passing, it’s the sending of arbitrary bytes between smart contracts rather than peer-to-peer or text messaging. There are several web3 projects that are suited to the chat use case; consider or for this type of messaging.

The Hyperlane community is regularly active in the . Feedback from developers directly influences the product roadmap.

You join the or follow Hyperlane where you can find a growing community of developers and enthusiasts to chat about the interchain future.

Share the excitement for all things interchain. Check out Abacus Works !

You can make a PR to edit this documentation directly via the

XMTP
Push
Discord
Discord
Twitter
job openings
docs repo
Default ISM