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.

Sign up for GitHub

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 diagram clarifying contract flow by upkeep type #1784

Merged
merged 2 commits into from
Feb 27, 2024
Merged

Add diagram clarifying contract flow by upkeep type #1784

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
130127a
Add migration by upkeep type diagram
thedriftofwords Feb 26, 2024
1a0ced6
Merge branch 'main' into 022624-migration-diagram
khadni Feb 27, 2024
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
Binary file added public/images/automation/v2-migration/v2-upkeeps-by-type.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
9 changes: 9 additions & 0 deletions src/content/chainlink-automation/guides/migrate-to-v2.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,6 +113,15 @@ Your new upkeep has a new [unique forwarder](#unique-forwarder) to increase secu

1. Update your contract to use the forwarder address by following the instructions on the [Forwarder](/chainlink-automation/guides/forwarder) page.

### Forwarders by upkeep type

This diagram shows the flow of different contracts that Automation 2.0 deploys for new and migrated upkeeps. Compared to custom logic and log trigger upkeeps, time-based upkeeps have an additional contract:

<ClickToZoom src="/images/automation/v2-migration/v2-upkeeps-by-type.png" />

- For custom logic and log trigger upkeeps, the `msg.sender` in relation to your contract is the unique forwarder that Automation deploys when you migrate your upkeep.
- For time-based upkeeps, Automation deploys a unique forwarder and a unique CRON upkeep contract. In this case, the CRON upkeep contract is the `msg.sender` in relation to your contract.

## Migration checklist

Before you migrate, be aware of several important changes listed here.
Expand Down
Loading