Hyperliquid ccip (#2771)

* network specific limits

* remove tooltip trial

* detail desc for SEO

* nit

* nit

---------

Co-authored-by: Amine E. <[email protected]>
Co-authored-by: aelmanaa <[email protected]>

Author: gfletcher-cll

src/config/sidebar.ts

@@ -1109,6 +1109,10 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
               title: "SVM",
               url: "ccip/service-limits/svm",
             },
+            {
+              title: "Network Specific",
+              url: "ccip/service-limits/network-specific-limits",
+            },
           ],
         },
         {

src/content/ccip/service-limits/index.mdx

@@ -3,13 +3,14 @@ section: ccip
 date: Last Modified
 title: "CCIP Service Limits"
 metadata:
-  description: "Learn about the operational limits for Chainlink CCIP across EVM and SVM blockchains, including message size constraints, execution resources, and token transfer limitations."
+  description: "Complete guide to Chainlink CCIP operational limits across all blockchain architectures. Covers EVM and SVM service constraints, network-specific limitations, message size limits, execution resources, and token transfer restrictions for cross-chain applications."
 isIndex: true
 ---
 
 This section outlines the operational limits for Chainlink CCIP across different blockchain architectures.
 
 - **[EVM Service Limits](/ccip/service-limits/evm)**: Service limits for Ethereum and other EVM-compatible blockchains.
 - **[SVM Service Limits](/ccip/service-limits/svm)**: Service limits for Solana and other SVM-based blockchains.
+- **[Network-Specific Limits](/ccip/service-limits/network-specific-limits)**: Documented network-specific limitations (all blockchain families).
 
 Understanding these limits is essential for building reliable cross-chain applications that operate within CCIP's intended parameters.

src/content/ccip/service-limits/network-specific-limits.mdx

@@ -0,0 +1,17 @@
+---
+section: ccip
+date: Last Modified
+title: "Chainlink CCIP Network Specific Limits"
+metadata:
+  description: "Comprehensive guide to network-specific limitations and risks for CCIP cross-chain applications. Covers HyperEVM/Hyperliquid data availability issues, RPC synchronization problems, and mitigation strategies for developers and blockchain teams."
+---
+
+This page describes known network-specific limitations that may result from the design of a particular network. End users, application developers, blockchain development teams, token developers and others should read and understand these risks when considering interacting with these networks on CCIP.
+
+## HyperEVM
+
+**Risk**:
+[Hyperliquid Data availability](/ccip/service-responsibility#blockchain-development-team-responsibilities): If a HyperEVM RPC is out of sync or offline for 10+ minutes, missing logs from during the downtime are only available through a centralized resource that is hosted and maintained by Hyperliquid. In the event that logs related to specific CCIP messages are irrecoverable, those CCIP messages can become stuck or fail.
+
+**CCIP Mitigation**:
+Hyperliquid has provided a workaround to serve logs through a [dedicated resource](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/raw-hyperevm-block-data) in case their network is inaccessible from RPC providers. CCIP is utilizing Hyperliquid's data source to backfill missing logs. In addition, CCIP Node Operators have implemented additional defense, using an multi-RPC approach, allowing for detection of out-of-sync or offline RPCs and an automatic fallback. If all configured RPCs are unavailable for a period of 10+ minutes AND the Hyperliquid data source does not provide them, logs may not be recoverable.

src/content/ccip/service-responsibility.mdx

@@ -14,7 +14,7 @@ import { Aside } from "@components"
   disclosures. By using Chainlink CCIP, you expressly acknowledge and agree to accept these terms.
 </Aside>
 
-The Chainlink Cross-Chain Interoperability Protocol (CCIP) is a secure, reliable, and easy-to-use interoperability protocol for building cross-chain applications and services. The use of CCIP involves application developers, blockchain development teams, token developers and Chainlink node operators, among others. These participants share responsibility for ensuring that operation and performance match expectations. Please note that CCIP support of a particular blockchain, application, or token does not constitute endorsement of such blockchain, application, or token.
+The Chainlink Cross-Chain Interoperability Protocol (CCIP) is a secure, reliable, and easy-to-use interoperability protocol for building cross-chain applications and services. The use of CCIP involves application developers, blockchain development teams, token developers and Chainlink node operators, among others. These participants share responsibility for ensuring that operation and performance match expectations. Please note that CCIP support of a particular blockchain, application, or token does not constitute endorsement of such blockchain, application, or token. Please review the [CCIP Service Limits](/ccip/service-limits) which provides important additional information.
 
 ## Application Developer Responsibilities
 
@@ -40,6 +40,7 @@ Blockchain development teams are responsible for the correctness, security, and
 - **Fixes and upgrades:** Blockchain development teams must communicate availability of fixes immediately and announce planned upgrades as much in advance as possible so blockchain validators and application developers can prepare themselves accordingly.
 - **Incident management:** Blockchain development teams are responsible for clearly articulating and communicating any security, reliability and availability incidents to their community. This includes root cause analysis, post-mortem details and a clear plan of action to recover and prevent from happening in the future.
 - **Blockchain liveness:** Blockchain development teams must take appropriate action to ensure their blockchain maintains a high degree of liveness and aligns with set expectations towards their community members and applications developers.
+- **Data availability**: The blockchain network must ensure that complete historical data remains consistently accessible through standard RPC interfaces. This includes block headers, transactions, and emitted logs. This includes ensuring that nodes can serve past blocks and logs even after temporary downtime or restarts. Failure to provide reliable access to historical logs can result in stuck or failed transactions.
 
 ## Token Developers Responsibilities