Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add link to onboarding-new-tokens #1902

Merged
merged 1 commit into from
Apr 23, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 11 additions & 9 deletions src/content/ccip/architecture.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -115,15 +115,17 @@ The mechanism for handling tokens varies depending on the characteristics of eac

</Aside>

<Aside type="note" title="Onboarding New Tokens">
Supported tokens for each lane are listed on the [CCIP supported network pages](/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>
<section id="onboarding-new-tokens">
<Aside type="note" title="Onboarding New Tokens">
Supported tokens for each lane are listed on the [CCIP supported network pages](/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>
</section>

#### Risk Management Network contract

Expand Down
Loading