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

CCIP Guide - Send multiple messages in a single txn #2052

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

khadni
Copy link
Collaborator

@khadni khadni commented Sep 2, 2024

No description provided.

Copy link

vercel bot commented Sep 2, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
documentation ✅ Ready (Inspect) Visit Preview Sep 13, 2024 2:30am

Copy link
Collaborator

@thedriftofwords thedriftofwords left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor editorial review


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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants