-
Notifications
You must be signed in to change notification settings - Fork 2k
Add datastore write API for ccip #23600
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
557 changes: 543 additions & 14 deletions
557
deployment/ccip/changeset/cs_orchestrate_changesets.go
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| package shared | ||
|
|
||
| import ( | ||
| "strings" | ||
|
|
||
| chainsel "github.com/smartcontractkit/chain-selectors" | ||
| ) | ||
|
|
||
| // NormalizeAddress lower-cases an address only on families where case carries no meaning. | ||
| // | ||
| // EVM addresses are hex and are commonly written in EIP-55 checksum form, so the same contract | ||
| // can appear in two casings and must compare equal. Solana and Sui addresses are case-sensitive, | ||
| // where folding case would map two different contracts onto one value. An unknown selector is | ||
| // left alone: preserving a distinction that does not exist is harmless, whereas erasing one that | ||
| // does silently merges two contracts. | ||
| func NormalizeAddress(chainSelector uint64, address string) string { | ||
| family, err := chainsel.GetSelectorFamily(chainSelector) | ||
| if err != nil || family != chainsel.FamilyEVM { | ||
| return address | ||
| } | ||
|
|
||
| return strings.ToLower(address) | ||
| } | ||
|
|
||
| // AddressesEqual reports whether two addresses on the same chain refer to the same contract, | ||
| // using the case rules of that chain's family. Use it instead of == whenever an address that came | ||
| // from one source is compared against an address that came from another, since only one of them | ||
| // may be checksummed. | ||
| func AddressesEqual(chainSelector uint64, a, b string) bool { | ||
| return NormalizeAddress(chainSelector, a) == NormalizeAddress(chainSelector, b) | ||
| } |
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a sub-changeset records an address using a semantic qualifier, its legacy address-book entry is also passed to
PopulateDataStore, which creates another ref for the same contract using the syntheticaddress-typequalifier. Merging all of those refs unconditionally leaves two keys for the same chain/type/version/address, so lookups that omit a qualifier become ambiguous and the returned datastore no longer preserves the intended write model. Filter address-book-derived refs whose contract is already represented; the same unconditional merge appears in both Solana E2E variants.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Last PR removes this completely. No need to address individually.