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

chore(ICP_Ledger): Add 4th ICP archive canister to list of protocol canisters #4461

Conversation

mbjorkqvist
Copy link
Member

Add the canister ID of the 4th ICP archive canister to the list of protocol canisters.

@github-actions github-actions bot added the chore label Mar 21, 2025
@mbjorkqvist
Copy link
Member Author

See this related forum thread.

@mbjorkqvist mbjorkqvist marked this pull request as ready for review March 24, 2025 11:24
@mbjorkqvist mbjorkqvist requested a review from a team as a code owner March 24, 2025 11:24
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

If this pull request affects the behavior of any canister owned by
the Governance team, remember to update the corresponding
unreleased_changes.md file(s).

To acknowldge this reminder (and unblock the PR), dismiss this
code review by going to the bottom of the pull request page, and
supply one of the following reasons:

  1. Done.

  2. No canister behavior changes.

@max-dfinity
Copy link
Contributor

max-dfinity commented Mar 24, 2025

I have this open in another PR (because I was adding the new Node Rewards canister to this list). So this can be closed to avoid merge conflicts: #4252

@mbjorkqvist
Copy link
Member Author

I have this open in another PR (because I was adding the new Node Rewards canister to this list). So this can be closed to avoid merge conflicts: #4252

Fair enough, thanks @max-dfinity!

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