Fix issue 1405

builders/interoperability/protocols/hyperlane.md

@@ -10,9 +10,52 @@ categories: GMP Providers
 
 [Hyperlane](https://hyperlane.xyz/){target=\_blank} is a security-modular cross-chain communication protocol for Web3. Hyperlane enables dApp users to interact with any asset or application, on any connected chain, with one click. It supports general asset transfer as well as custom cross-chain messaging.  
 
-Using [Interchain Security Modules (ISMs)](https://docs.hyperlane.xyz/docs/protocol/ISM/modular-security){target=\_blank}, Hyperlane allows developers to configure the method by which messages are sent and validated across chains. Hyperlane is composed of validators, relayers, and watchtowers. [Validators](https://docs.hyperlane.xyz/docs/protocol/agents/validators){target=\_blank} will watch for and confirm cross-chain messages. [Relayers](https://docs.hyperlane.xyz/docs/protocol/agents/relayer){target=\_blank} spend the gas to send messages across chains. [Watchtowers](https://docs.hyperlane.xyz/docs/protocol/agents/overview){target=\_blank} perform checks to ensure that validators are good-faith actors, securing the protocol. Take a look at the tech stack diagram and their [protocol documentation](https://docs.hyperlane.xyz/docs/protocol/protocol-overview){target=\_blank} for more details.
+Using [Interchain Security Modules (ISMs)](https://docs.hyperlane.xyz/docs/protocol/ISM/modular-security){target=\_blank}, Hyperlane allows developers to configure how cross-chain messages are verified on the destination chain. Hyperlane is composed of validators and relayers. [Validators](https://docs.hyperlane.xyz/docs/operate/overview-agents){target=\_blank} observe the origin chain and sign messages according to the rules defined by the configured ISM. The ISM then verifies those signatures on the destination chain to determine whether a message is valid. [Relayers](https://docs.hyperlane.xyz/docs/operate/overview-agents){target=\_blank} deliver the signed messages to the destination chain and pay the required gas fees. Take a look at the tech stack diagram and their [protocol documentation](https://docs.hyperlane.xyz/docs/protocol/protocol-overview){target=\_blank} for more details.
 
-![Hyperlane Technology Stack diagram](/images/builders/interoperability/protocols/hyperlane/hyperlane-1.webp)
+```mermaid
+flowchart TB
+
+  %% ORIGIN
+  subgraph Origin
+    direction TB
+    Sender["Sender"]
+    Step1["1. dispatch(destination, recipient, body)"]
+    MailboxO[(Mailbox)]
+
+    Sender --> Step1
+    Step1 --> MailboxO
+  end
+
+  Step2["2. emit dispatch(sender, destination, recipient, body)"]
+  Relayer(("Relayer"))
+  Step3["3. process(metadata, message)"]
+
+  MailboxO --> Step2
+  Step2 --> Relayer
+  Relayer --> Step3
+
+  %% DESTINATION
+  subgraph Destination
+    direction TB
+    MailboxD[(Mailbox)]
+    Step4["4. interchainSecurityModule()"]
+    Step5["5. verify(metadata, message)"]
+    ISM["InterchainSecurityModule"]
+    Step6["6. handle(origin, sender, body)"]
+    Recipient["Recipient"]
+
+    MailboxD --> Step5
+    Step5 --> ISM
+
+    MailboxD --> Step6
+    Step6 --> Recipient
+
+    MailboxD -.-> Step4
+    Step4 -.-> Recipient
+  end
+
+  Step3 --> MailboxD
+```
 
 The Hyperlane APIs provide a rich suite for developing Web3 applications, ensuring that developers have the tools they need for building. With these tools and APIs, developers can use the Hyperlane protocol and its APIs to write dApps that can be easily deployed across all Hyperlane-connected ecosystems.
 
@@ -22,13 +65,14 @@ The Hyperlane APIs provide a rich suite for developing Web3 applications, ensuri
 
 There are a couple of resources to get you started building cross-chain applications with Hyperlane:
 
-- **[Developer documentation](https://docs.hyperlane.xyz/docs/get-started-building){target=\_blank}** - for technical guides
-- **[Hyperlane Explorer](https://explorer.hyperlane.xyz){target=\_blank}** - to track cross-chain transfers
+- **[Developer documentation](https://docs.hyperlane.xyz/){target=\_blank}**: For technical guides
+- **[Hyperlane Explorer](https://explorer.hyperlane.xyz){target=\_blank}**: To track cross-chain transfers
 
 ## Contracts {: #contracts }
 
 See the list of Hyperlane contracts deployed to Moonbeam, and the networks connected to Moonbeam through Hyperlane.
 
-- [MainNet and TestNet Contracts](https://docs.hyperlane.xyz/docs/reference/addresses/validators/mainnet-default-ism-validators#moonbeam-1284){target=\_blank}
+- [MainNet Contracts](https://docs.hyperlane.xyz/docs/reference/addresses/validators/mainnet-default-ism-validators){target=\_blank}
+- [TestNet Contracts](https://docs.hyperlane.xyz/docs/reference/addresses/validators/testnet-default-ism-validators){target=\_blank}
 
 --8<-- 'text/_disclaimers/third-party-content.md'

llms-files/llms-gmp-providers.txt

@@ -83,9 +83,52 @@ categories: GMP Providers
 
 [Hyperlane](https://hyperlane.xyz/){target=\_blank} is a security-modular cross-chain communication protocol for Web3. Hyperlane enables dApp users to interact with any asset or application, on any connected chain, with one click. It supports general asset transfer as well as custom cross-chain messaging.  
 
-Using [Interchain Security Modules (ISMs)](https://docs.hyperlane.xyz/docs/protocol/ISM/modular-security){target=\_blank}, Hyperlane allows developers to configure the method by which messages are sent and validated across chains. Hyperlane is composed of validators, relayers, and watchtowers. [Validators](https://docs.hyperlane.xyz/docs/protocol/agents/validators){target=\_blank} will watch for and confirm cross-chain messages. [Relayers](https://docs.hyperlane.xyz/docs/protocol/agents/relayer){target=\_blank} spend the gas to send messages across chains. [Watchtowers](https://docs.hyperlane.xyz/docs/protocol/agents/overview){target=\_blank} perform checks to ensure that validators are good-faith actors, securing the protocol. Take a look at the tech stack diagram and their [protocol documentation](https://docs.hyperlane.xyz/docs/protocol/protocol-overview){target=\_blank} for more details.
-
-![Hyperlane Technology Stack diagram](/images/builders/interoperability/protocols/hyperlane/hyperlane-1.webp)
+Using [Interchain Security Modules (ISMs)](https://docs.hyperlane.xyz/docs/protocol/ISM/modular-security){target=\_blank}, Hyperlane allows developers to configure how cross-chain messages are verified on the destination chain. Hyperlane is composed of validators and relayers. [Validators](https://docs.hyperlane.xyz/docs/operate/overview-agents){target=\_blank} observe the origin chain and sign messages according to the rules defined by the configured ISM. The ISM then verifies those signatures on the destination chain to determine whether a message is valid. [Relayers](https://docs.hyperlane.xyz/docs/operate/overview-agents){target=\_blank} deliver the signed messages to the destination chain and pay the required gas fees. Take a look at the tech stack diagram and their [protocol documentation](https://docs.hyperlane.xyz/docs/protocol/protocol-overview){target=\_blank} for more details.
+
+```mermaid
+flowchart TB
+
+  %% ORIGIN
+  subgraph Origin
+    direction TB
+    Sender["Sender"]
+    Step1["1. dispatch(destination, recipient, body)"]
+    MailboxO[(Mailbox)]
+
+    Sender --> Step1
+    Step1 --> MailboxO
+  end
+
+  Step2["2. emit dispatch(sender, destination, recipient, body)"]
+  Relayer(("Relayer"))
+  Step3["3. process(metadata, message)"]
+
+  MailboxO --> Step2
+  Step2 --> Relayer
+  Relayer --> Step3
+
+  %% DESTINATION
+  subgraph Destination
+    direction TB
+    MailboxD[(Mailbox)]
+    Step4["4. interchainSecurityModule()"]
+    Step5["5. verify(metadata, message)"]
+    ISM["InterchainSecurityModule"]
+    Step6["6. handle(origin, sender, body)"]
+    Recipient["Recipient"]
+
+    MailboxD --> Step5
+    Step5 --> ISM
+
+    MailboxD --> Step6
+    Step6 --> Recipient
+
+    MailboxD -.-> Step4
+    Step4 -.-> Recipient
+  end
+
+  Step3 --> MailboxD
+```
 
 The Hyperlane APIs provide a rich suite for developing Web3 applications, ensuring that developers have the tools they need for building. With these tools and APIs, developers can use the Hyperlane protocol and its APIs to write dApps that can be easily deployed across all Hyperlane-connected ecosystems.
 
@@ -97,14 +140,15 @@ The Hyperlane APIs provide a rich suite for developing Web3 applications, ensuri
 
 There are a couple of resources to get you started building cross-chain applications with Hyperlane:
 
-- **[Developer documentation](https://docs.hyperlane.xyz/docs/get-started-building){target=\_blank}** - for technical guides
-- **[Hyperlane Explorer](https://explorer.hyperlane.xyz){target=\_blank}** - to track cross-chain transfers
+- **[Developer documentation](https://docs.hyperlane.xyz/){target=\_blank}**: For technical guides
+- **[Hyperlane Explorer](https://explorer.hyperlane.xyz){target=\_blank}**: To track cross-chain transfers
 
 ## Contracts {: #contracts }
 
 See the list of Hyperlane contracts deployed to Moonbeam, and the networks connected to Moonbeam through Hyperlane.
 
-- [MainNet and TestNet Contracts](https://docs.hyperlane.xyz/docs/reference/addresses/validators/mainnet-default-ism-validators#moonbeam-1284){target=\_blank}
+- [MainNet Contracts](https://docs.hyperlane.xyz/docs/reference/addresses/validators/mainnet-default-ism-validators){target=\_blank}
+- [TestNet Contracts](https://docs.hyperlane.xyz/docs/reference/addresses/validators/testnet-default-ism-validators){target=\_blank}
 
 <div class="page-disclaimer">
   The information presented herein has been provided by third parties and is made available solely for general information purposes. Moonbeam does not endorse any project listed and described on the Moonbeam Doc Website (https://docs.moonbeam.network/). Moonbeam Foundation does not warrant the accuracy, completeness or usefulness of this information. Any reliance you place on such information is strictly at your own risk. Moonbeam Foundation disclaims all liability and responsibility arising from any reliance placed on this information by you or by anyone who may be informed of any of its contents. All statements and/or opinions expressed in these materials are solely the responsibility of the person or entity providing those materials and do not necessarily represent the opinion of Moonbeam Foundation. The information should not be construed as professional or financial advice of any kind. Advice from a suitably qualified professional should always be sought in relation to any particular matter or circumstance. The information herein may link to or integrate with other websites operated or content provided by third parties, and such other websites may link to this website. Moonbeam Foundation has no control over any such other websites or their content and will have no liability arising out of or related to such websites or their content. The existence of any such link does not constitute an endorsement of such websites, the content of the websites, or the operators of the websites. These links are being provided to you only as a convenience and you release and hold Moonbeam Foundation harmless from any and all liability arising from your use of this information or the information provided by any third-party website or service.

llms-full.txt

@@ -19176,9 +19176,52 @@ categories: GMP Providers
 
 [Hyperlane](https://hyperlane.xyz/){target=\_blank} is a security-modular cross-chain communication protocol for Web3. Hyperlane enables dApp users to interact with any asset or application, on any connected chain, with one click. It supports general asset transfer as well as custom cross-chain messaging.  
 
-Using [Interchain Security Modules (ISMs)](https://docs.hyperlane.xyz/docs/protocol/ISM/modular-security){target=\_blank}, Hyperlane allows developers to configure the method by which messages are sent and validated across chains. Hyperlane is composed of validators, relayers, and watchtowers. [Validators](https://docs.hyperlane.xyz/docs/protocol/agents/validators){target=\_blank} will watch for and confirm cross-chain messages. [Relayers](https://docs.hyperlane.xyz/docs/protocol/agents/relayer){target=\_blank} spend the gas to send messages across chains. [Watchtowers](https://docs.hyperlane.xyz/docs/protocol/agents/overview){target=\_blank} perform checks to ensure that validators are good-faith actors, securing the protocol. Take a look at the tech stack diagram and their [protocol documentation](https://docs.hyperlane.xyz/docs/protocol/protocol-overview){target=\_blank} for more details.
+Using [Interchain Security Modules (ISMs)](https://docs.hyperlane.xyz/docs/protocol/ISM/modular-security){target=\_blank}, Hyperlane allows developers to configure how cross-chain messages are verified on the destination chain. Hyperlane is composed of validators and relayers. [Validators](https://docs.hyperlane.xyz/docs/operate/overview-agents){target=\_blank} observe the origin chain and sign messages according to the rules defined by the configured ISM. The ISM then verifies those signatures on the destination chain to determine whether a message is valid. [Relayers](https://docs.hyperlane.xyz/docs/operate/overview-agents){target=\_blank} deliver the signed messages to the destination chain and pay the required gas fees. Take a look at the tech stack diagram and their [protocol documentation](https://docs.hyperlane.xyz/docs/protocol/protocol-overview){target=\_blank} for more details.
 
-![Hyperlane Technology Stack diagram](/images/builders/interoperability/protocols/hyperlane/hyperlane-1.webp)
+```mermaid
+flowchart TB
+
+  %% ORIGIN
+  subgraph Origin
+    direction TB
+    Sender["Sender"]
+    Step1["1. dispatch(destination, recipient, body)"]
+    MailboxO[(Mailbox)]
+
+    Sender --> Step1
+    Step1 --> MailboxO
+  end
+
+  Step2["2. emit dispatch(sender, destination, recipient, body)"]
+  Relayer(("Relayer"))
+  Step3["3. process(metadata, message)"]
+
+  MailboxO --> Step2
+  Step2 --> Relayer
+  Relayer --> Step3
+
+  %% DESTINATION
+  subgraph Destination
+    direction TB
+    MailboxD[(Mailbox)]
+    Step4["4. interchainSecurityModule()"]
+    Step5["5. verify(metadata, message)"]
+    ISM["InterchainSecurityModule"]
+    Step6["6. handle(origin, sender, body)"]
+    Recipient["Recipient"]
+
+    MailboxD --> Step5
+    Step5 --> ISM
+
+    MailboxD --> Step6
+    Step6 --> Recipient
+
+    MailboxD -.-> Step4
+    Step4 -.-> Recipient
+  end
+
+  Step3 --> MailboxD
+```
 
 The Hyperlane APIs provide a rich suite for developing Web3 applications, ensuring that developers have the tools they need for building. With these tools and APIs, developers can use the Hyperlane protocol and its APIs to write dApps that can be easily deployed across all Hyperlane-connected ecosystems.
 
@@ -19190,14 +19233,15 @@ The Hyperlane APIs provide a rich suite for developing Web3 applications, ensuri
 
 There are a couple of resources to get you started building cross-chain applications with Hyperlane:
 
-- **[Developer documentation](https://docs.hyperlane.xyz/docs/get-started-building){target=\_blank}** - for technical guides
-- **[Hyperlane Explorer](https://explorer.hyperlane.xyz){target=\_blank}** - to track cross-chain transfers
+- **[Developer documentation](https://docs.hyperlane.xyz/){target=\_blank}**: For technical guides
+- **[Hyperlane Explorer](https://explorer.hyperlane.xyz){target=\_blank}**: To track cross-chain transfers
 
 ## Contracts {: #contracts }
 
 See the list of Hyperlane contracts deployed to Moonbeam, and the networks connected to Moonbeam through Hyperlane.
 
-- [MainNet and TestNet Contracts](https://docs.hyperlane.xyz/docs/reference/addresses/validators/mainnet-default-ism-validators#moonbeam-1284){target=\_blank}
+- [MainNet Contracts](https://docs.hyperlane.xyz/docs/reference/addresses/validators/mainnet-default-ism-validators){target=\_blank}
+- [TestNet Contracts](https://docs.hyperlane.xyz/docs/reference/addresses/validators/testnet-default-ism-validators){target=\_blank}
 
 <div class="page-disclaimer">
   The information presented herein has been provided by third parties and is made available solely for general information purposes. Moonbeam does not endorse any project listed and described on the Moonbeam Doc Website (https://docs.moonbeam.network/). Moonbeam Foundation does not warrant the accuracy, completeness or usefulness of this information. Any reliance you place on such information is strictly at your own risk. Moonbeam Foundation disclaims all liability and responsibility arising from any reliance placed on this information by you or by anyone who may be informed of any of its contents. All statements and/or opinions expressed in these materials are solely the responsibility of the person or entity providing those materials and do not necessarily represent the opinion of Moonbeam Foundation. The information should not be construed as professional or financial advice of any kind. Advice from a suitably qualified professional should always be sought in relation to any particular matter or circumstance. The information herein may link to or integrate with other websites operated or content provided by third parties, and such other websites may link to this website. Moonbeam Foundation has no control over any such other websites or their content and will have no liability arising out of or related to such websites or their content. The existence of any such link does not constitute an endorsement of such websites, the content of the websites, or the operators of the websites. These links are being provided to you only as a convenience and you release and hold Moonbeam Foundation harmless from any and all liability arising from your use of this information or the information provided by any third-party website or service.