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

Solana plugin #15820

Open
wants to merge 7 commits into
base: develop
Choose a base branch
from
Open

Solana plugin #15820

wants to merge 7 commits into from

Conversation

archseer
Copy link
Contributor

@archseer archseer commented Jan 2, 2025

No description provided.

Copy link
Contributor

github-actions bot commented Jan 2, 2025

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

🎖️ No JIRA issue number found in: PR title, commit message, or branch name. Please include the issue ID in one of these.

@huangzhen1997
Copy link
Contributor

Thanks for making this, looks good to me. Do you want to merge this or create it as a base branch ?

break
}
_, exists := keyBundles[family]
if !exists {
Copy link
Contributor

Choose a reason for hiding this comment

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

The previous code had comment "// TODO: Validate that that all EVM chains are using the same keybundle."

Based on that, does it make sense to validate that if a bundle exists for a family, ensure it is same

keyBundleId, exists := keyBundles[family]
if exists {
if keyBundleId != config.KeyBundleID
return deployment.ChangesetOutput{}, new Error("A family is not using the same keyBundle")
}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I resolved the TODO since that's the implicit behaviour we've used for keystone too. A single key is automatically generated for each family (as long as there's a relayer for that family type), so using different ones is unexpected

I'll add that check in 👍🏻

@archseer archseer marked this pull request as ready for review January 3, 2025 11:36
@archseer archseer requested review from a team as code owners January 3, 2025 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants