CCIP Guide - Send multiple messages in a single txn #2052
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
khadni
requested review from
dwightjl,
aelmanaa and
thedriftofwords
as code owners
thedriftofwords
requested changes
Sep 20, 2024
|
|
||
| This tutorial will teach you how to send multiple messages to different chains within a single transaction using Chainlink CCIP. You will learn how to send messages immediately without storing them in the contract's state, and how to register messages first and dispatch them later, which can be useful for scenarios like scheduled or automated message sending. | ||
|
|
||
| **Note**: For simplicity, this tutorial demonstrates this pattern for sending arbitrary data. However, you are not limited to this application. You can apply the same pattern to programmable token transfers. |
There was a problem hiding this comment.
add link to "programmable token transfers"
|
|
||
| - This tutorial assumes you have completed the [Send Arbitrary Data](/ccip/tutorials/send-arbitrary-data) tutorial. | ||
| - Your account must have some testnet LINK and AVAX tokens on _Avalanche Fuji_. Both are available on the [Chainlink Faucet](https://faucets.chain.link/fuji). | ||
| - Learn how to [Fund a contract with LINK](/resources/fund-your-contract). |
There was a problem hiding this comment.
Suggested change
| - Learn how to [Fund a contract with LINK](/resources/fund-your-contract). | |
| - [Fund your contract with LINK](/resources/fund-your-contract). |
|
|
||
| - Immediate dispatch (`dispatchMessagesDirect`): This method is ideal for users who want to send multiple messages within the same transaction quickly, and without storing them in the contract's state. | ||
|
|
||
| - Registered dispatch (`registerMessage` and `dispatchMessages`): This method is suitable for use cases where messages need to be stored and sent later, possibly triggered by an external event or at a specific time (e.g., using [Chainlink Automation](/chainlink-automation)). It is useful for scheduling and automating message sending. |
There was a problem hiding this comment.
Suggested change
| - Registered dispatch (`registerMessage` and `dispatchMessages`): This method is suitable for use cases where messages need to be stored and sent later, possibly triggered by an external event or at a specific time (e.g., using [Chainlink Automation](/chainlink-automation)). It is useful for scheduling and automating message sending. | |
| - Registered dispatch (`registerMessage` and `dispatchMessages`): This method is suitable for use cases where messages need to be stored and sent later, possibly triggered by an external event or at a specific time (for example, using [Chainlink Automation](/chainlink-automation)). It is useful for scheduling and automating message sending. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.