You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* test
* link fix
* exclude ccip directory from internal link checking
* fix internal links
* use dev server
* parallel jobs
* Trigger Vercel deployment
* update urls
* fix ignored files
---------
Co-authored-by: Amine E. <aelmanaa@users.noreply.github.com>
Co-authored-by: aelmanaa <aelmanaa@gmail.com>
Copy file name to clipboardExpand all lines: src/content/ccip/architecture.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -181,7 +181,7 @@ Chainlink CCIP token transfers benefit from rate limits for additional security.
181
181
182
182
You can find the complete list of lanes and their rate limits on the [CCIP Directory](/ccip/directory) page.
183
183
184
-
The rate limits are enforced at both the source and destination blockchains for maximum security. If these rate limits are reached, descriptive errors with detailed information are generated and returned to the sender. This enables CCIP users to gracefully handle these errors within their dApps to preserve the end-user experience. A comprehensive list of errors and their descriptions is available on the [errors API reference](/ccip/api-reference/v1.5.1/errors#ratelimiter) page.
184
+
The rate limits are enforced at both the source and destination blockchains for maximum security. If these rate limits are reached, descriptive errors with detailed information are generated and returned to the sender. This enables CCIP users to gracefully handle these errors within their dApps to preserve the end-user experience. A comprehensive list of errors and their descriptions is available on the [errors API reference](/ccip/api-reference/v1.5.1/errors#rate-limiter-errors) page.
Copy file name to clipboardExpand all lines: src/content/ccip/concepts/cross-chain-tokens.mdx
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -450,7 +450,7 @@ The **Token Pool contract** is responsible for executing the cross-chain token t
450
450
-**BurnMintTokenPool**: Handles the burning, or minting of tokens depending whether it is the source or destination blockchain.
451
451
-**LockReleaseTokenPool**: Handles the locking or releasing of tokens depending on whether it is the source or destination blockchain.
452
452
453
-
For more information on the token pool contracts and their functionalities, refer to the [Requirement for Token Pools](#requirement-for-token-pools) section.
453
+
For more information on the token pool contracts and their functionalities, refer to the [Requirement for Token Pools](#requirements-for-token-pools) section.
454
454
455
455
### Registration
456
456
@@ -548,13 +548,15 @@ The configuration of token pools includes adding new blockchains, setting remote
548
548
-**Usage**:
549
549
- To add a new blockchain, the pool owner provides the remote chain selector, pool address, token address, and rate limiter configurations.
550
550
- To remove a blockchain, the `allowed` flag is set to `false`, and the chain is removed from the list of supported chains.
-**Purpose**: Set the remote pool's address to link the current token pool to a corresponding pool on a remote blockchain.
553
+
-**Purpose**: Adds a new remote pool address for a specific blockchain, enabling support for multiple pools per chain.
554
554
-**Details**:
555
-
- This function is used to establish the connection between token pools on different blockchains.
556
-
- It validates the provided chain selector and updates the remote pool address for the selected chain.
557
-
-**Usage**: This function sets or updates the remote pool address for a specific blockchain.
555
+
- Allows adding multiple pools for a single chain selector, which is crucial during pool upgrades
556
+
- Maintains support for in-flight messages from existing pools while adding new ones
557
+
- Validates chain selector support and prevents duplicate pool additions
558
+
- Each pool address is hashed and stored for efficient lookup
559
+
-**Usage**: This function is particularly useful during pool upgrades, allowing seamless transitions between pool versions while maintaining transaction support.
0 commit comments