From b562ae0793261d37cf522b12237114cb7d7ea87f Mon Sep 17 00:00:00 2001
From: aelmanaa <aelmanaa@gmail.com>
Date: Fri, 9 Feb 2024 12:44:41 +0100
Subject: [PATCH] onboarding of new tokens

---
 src/content/ccip/architecture.mdx | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/content/ccip/architecture.mdx b/src/content/ccip/architecture.mdx
index 6614dcf4b3f..1aaa37dea6a 100644
--- a/src/content/ccip/architecture.mdx
+++ b/src/content/ccip/architecture.mdx
@@ -97,6 +97,16 @@ Each token has its own token pool, an abstraction layer over ERC-20 tokens that
 
 Token pools provide rate limiting, which is a security feature enabling token issuers to set a maximum rate at which their token can be transferred.
 
+<Aside type="note" title="Onboarding New Tokens">
+  Supported tokens for each lane are listed on the [CCIP supported network page](/ccip/supported-networks). Expanding
+  support for additional tokens is an ongoing process to help ensure the highest level of cross-chain security. [Token
+  pool rate limits](/ccip/architecture/#token-pool-rate-limit) are configured per-token for each lane. These rate limits
+  are set together with token issuers where applicable. Rate limits are also selected based on various factors, such as
+  the unique risk characteristics of the token and the intended use cases. The onboarding process for adding new tokens
+  also helps ensure that dApps and users interact with the correct token version, reducing risks within the cross-chain
+  ecosystem.
+</Aside>
+
 #### Risk Management Network contract
 
 The Risk Management contract maintains the list of Risk Management node addresses that are allowed to bless or curse. The contract also holds the quorum logic for blessing a committed Merkle Root and cursing CCIP on a destination blockchain. Read the [Risk Management Network Concepts](/ccip/concepts#risk-management-network) section to learn more.