remove rmn blessing references and update diagrams

Author: gfletcher-cll

public/images/ccip/ccip-hl-v1.7.png

@@ -186,10 +186,6 @@ export const CCIP_SIDEBAR_CONTENT: SectionEntry[] = [
             title: "Overview",
             url: "ccip/concepts/architecture/offchain/overview",
           },
-          {
-            title: "Risk Management Network",
-            url: "ccip/concepts/architecture/offchain/risk-management-network",
-          },
         ],
       },
       {

public/images/ccip/concepts/architecture/ccip-svm-destination-chain.jpg

@@ -70,19 +70,3 @@ Organizations with specialized expertise in running Chainlink nodes. Each operat
 ## Decentralized Oracle Network (DON)
 
 A **decentralized oracle network (DON)** consists of multiple independent Chainlink nodes. These nodes monitor and retrieve data from specified sources (e.g., a source chain), reach consensus off-chain, and post results to a blockchain (e.g., a destination chain) in a [trust-minimized manner](https://blog.chain.link/what-is-trust-minimization/). For more details on the DONs used in CCIP, refer to the CCIP Offchain architecture page.
-
-## Risk Management Network
-
-The Risk Management Network is a unique architectural feature of CCIP that reinforces system security through a defense-in-depth approach based on established engineering principles such as N-version programming. On blockchains where RMN is enabled, a distinct set of node operators—separate from those of the core CCIP DONs—manages RMN functions.
-
-The RMN runs a minimal, separate implementation of the Chainlink node software using a different programming language than the primary CCIP system. This client diversity enhances robustness and minimizes external dependencies, thereby reducing the risk of supply chain attacks.
-
-On the blockchains where RMN is enabled, the RMN nodes independently verify and attest to source chain actions. The core CCIP components on the destination chain verify these attestations. For more details, refer to the following section.
-
-<Aside type="caution" title="Phased Deployments">
-  Certain blockchains may be integrated with CCIP in a phased approach, with the Committing and Executing DONs deployed
-  first and the Risk Management Network added in a later update. In cases of a phased deployment, merkle roots in
-  relevant Commit Stores are always considered blessed until the Risk Management Network has been deployed for that
-  blockchain. Please see the [CCIP Directory](/ccip/directory) for which integrations utilize a phased approach. Please
-  review [CCIP Service Responsibility](/ccip/service-responsibility) for more information.
-</Aside>

public/images/ccip/concepts/architecture/ccip-svm-source-chain.jpg

@@ -184,11 +184,3 @@ The `ccip::receiver_registry` is a module where developers can register their cu
 ## RMN (Risk Management Network) Remote
 
 The `ccip::rmn_remote` module is a critical security component deployed on every CCIP-enabled chain. Various CCIP modules (like `OnRamp`, `OffRamp`, `Token Pools`) query this component to verify the status of other chains in the network. It maintains an onchain list of "cursed" (i.e., blocklisted) chains. If a source or destination chain is cursed, CCIP transactions involving that chain are halted.
-
-<Aside type="caution" title="Phased Deployments">
-  Certain blockchains may be integrated with CCIP in a phased approach, with the Committing and Executing DONs deployed
-  first and the Risk Management Network added in a later update. In cases of a phased deployment, merkle roots in
-  relevant Commit Stores are always considered blessed until the Risk Management Network has been deployed for that
-  blockchain. Please see the [CCIP Directory](/ccip/directory) for which integrations utilize a phased approach. Please
-  review [CCIP Service Responsibility](/ccip/service-responsibility) for more information.
-</Aside>

public/images/ccip/concepts/architecture/onchain-evm-architecture-registry.jpg

@@ -102,9 +102,6 @@ During the **Commit Phase**, the following steps occur:
 
 1. **Commit Report Submission**
    - The Committing DON calls the `commit()` function on the OffRamp with a Commit Report that includes messages and/or price reports.
-1. **Validation of RMN Blessing**
-   - If the Commit Report includes blessed merkle roots from RMN-enabled source chains, the OffRamp verifies the RMN node signatures onchain via the `RMNRemote` contract.
-   - If the Commit Report does not include RMN signatures, the OffRamp validates that all unblessed merkle roots originate from source chains where RMN is disabled.
 1. **Price Report Staleness Check**
    - The OffRamp validates the staleness of price reports before forwarding the price to the FeeQuoter.
 1. **Cursed Source Chain Check**
@@ -191,11 +188,8 @@ The `setPool()` method can be invoked by a registered CCIP token administrator v
 
 Risk management in CCIP is performed by a separate, independent network that continuously monitors and validates cross-chain operations for anomalous activity, thereby providing an additional layer of security.
 
-With the latest CCIP release, the Risk Management Network (RMN) blessing occurs offchain. In this process, the Committing DON interacts offchain with RMN nodes to obtain a blessing, and the resulting RMN node signatures are included in the Commit Report posted on the OffRamp at the destination chain.
 The RMN Contract is deployed on every chain where CCIP is integrated, even on chains where RMN is not enabled. Its key functions include:
 
-1. **Blessing Verification**
-   - **Verify function**: The RMNRemote contract's `verify()` function is used by the OffRamp to verify RMN signatures for messages originating from RMN-enabled source chains.
 1. **Cursing Mechanism**
    - **Curse Initiation**: When the CCIP Owner manually initiates a curse, the `curse()` function is invoked to mark the appropriate subjects as cursed.
    - **Curse Detection**: Onchain components (such as the Router, OnRamp, OffRamp, and TokenPool) call the `isCursed()` function on the RMNRemote contract to detect global curses or curses targeting a remote chain.

src/config/sidebar/ccip-dynamic.ts

@@ -193,13 +193,7 @@ The FeeQuoter is a central component in Chainlink CCIP that maintains token and
 
 ## Risk Management Network
 
-The Risk Management Network (RMN) adds an additional security layer to CCIP by performing offchain risk validation and maintaining an onchain "cursing" mechanism. The RMN program enables verification of cross-chain messages and can halt message transmission for specific blockchains or globally when security threats are detected.
-
-### Blessing and Verification
-
-- Offchain RMN nodes generate ECDSA signatures over merkle roots representing cross-chain message batches.
-- CCIP programs (such as Router or OffRamp) make CPI calls to the `verify_not_cursed` function to check whether the relevant chain (source or destination) is cursed.
-- The RMN program checks its `Curses` account to verify the subject isn't cursed before allowing the transaction to proceed.
+The Risk Management Network (RMN) adds an additional security layer to CCIP by maintaining an onchain "cursing" mechanism. The RMN program enables verification of cross-chain messages and can halt message transmission for specific blockchains or globally when security threats are detected.
 
 ### Cursing Mechanism
 

src/content/ccip/concepts/architecture/key-concepts.mdx

@@ -19,7 +19,7 @@ CCIP is a cross-chain messaging protocol built on Chainlink and secured by its d
 - **Data Transmission**: Send arbitrary data (i.e., bytes) to a receiving contract.
 - **Programmable Token Transfers**: Transfer tokens along with instructions for handling them to a receiving contract (referred to as a programmable token transfer or PTT).
 
-CCIP supports several token transfer mechanisms—including Burn-and-Mint, Lock-and-Mint, and Lock-and-Unlock—using a common interface. Token developers can enable permissionless cross-chain transfers of their tokens via the Chainlink CCT (Cross-Chain Token) standard (detailed documentation is available here). Additionally, CCIP includes an independent Risk Management Network (RMN) that provides layered security through a defense-in-depth approach.
+CCIP supports several token transfer mechanisms—including Burn-and-Mint, Lock-and-Mint, and Lock-and-Unlock—using a common interface. Token developers can enable permissionless cross-chain transfers of their tokens via the Chainlink CCT (Cross-Chain Token) standard (detailed documentation is available here).
 
 <Aside title="Terminology">
 
@@ -39,8 +39,6 @@ CCIP delivers cross-chain messages from a source chain to a destination chain by
    - Decentralized Oracle Network (DON) with nodes that perform distinct roles:
      - Commit: Observes and validates source-chain events to build a consensus-based report.
      - Execution: Validates pending messages and optimizes them for execution on the destination chain.
-   - Risk Management Network:
-     - Operating independently from the main DON, the Risk Management Network "blesses" the committed messages offchain by generating independent attestations. This additional step enhances overall security with a defense-in-depth design.
 
 1. **Onchain Architecture**
    - Router:
@@ -51,14 +49,13 @@ CCIP delivers cross-chain messages from a source chain to a destination chain by
      - Dispatching the message (data and/or tokens).
    - On the destination blockchain, offramping functionality consists of:
      - Accepting and verifying commit reports from the Committing DON.
-     - Validating Risk Management Network nodes signatures when receiving messages from the Executing DON.
      - Releasing or minting tokens to the receiver.
      - Routing the processed message to the designated receiver.
 
 **Note:** These high-level descriptions outline the core principles of CCIP. The detailed architectures for offchain and onchain architecture—and variations across implementations (e.g., on Solana, the Router incorporates OnRamp functionalities)—can be found in the relevant documentation.
 
 <ClickToZoom
-  src="/images/ccip/ccip-hl-v1.6.gif"
+  src="/images/ccip/ccip-hl-v1.7.png"
   alt="CCIP High-Level Architecture"
   style="display: block; margin: 2rem auto; max-height: 60vh; width: auto;"
 />