self-relay-hyperlane-message

You can manually relay a Hyperlane message by invoking the CLI status --relay workflow with a dispatch_tx or message_id. This self-relay operation requires the Hyperlane CLI and a signing key to deliver cross-chain messages when automated relays are unavailable.

Manual delivery of interchain messages is needed during development, troubleshooting, and demonstrations where automated relays are impractical or restricted. It allows operators to validate message origin and delivery status to ensure correct cross-chain messaging behavior during manual tests.

To self-relay a Hyperlane message, you need the Hyperlane CLI installed and a valid signing key. You must also provide either a dispatch_tx or a message_id, including the origin_chain context as needed, to execute the relay operation.

The Hyperlane CLI validates message origin and delivery status by tracking the message via a dispatch_tx or message_id during the status --relay workflow. This ensures correct cross-chain messaging behavior is verified before completing the manual delivery operation.

Yes, you can use a message_id instead of a dispatch_tx to relay a Hyperlane message. The CLI accepts either identifier to initiate the self-relay workflow, allowing flexibility when querying and manually delivering interchain messages across Ethereum-type chains.

Hyperlane messages may stall when automated relays are unavailable or restricted. You can resolve this by performing a manual self-relay using the CLI status --relay workflow with the dispatch_tx or message_id to force delivery across Ethereum-type chains.