Skip to content

Commit

Permalink
onboarding of new tokens
Browse files Browse the repository at this point in the history
  • Loading branch information
aelmanaa committed Feb 9, 2024
1 parent d134ee3 commit b562ae0
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions src/content/ccip/architecture.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit b562ae0

Please sign in to comment.