save solana pdas in address book

[tt-cll]

Requires

Supports

[github-actions]

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

[yashnevatia]

As discussed offline, I think we should store the chain selectors instead of storing the source/dest PDAs and then add more flexibility in the values instead of having dynamic types

type SolCCIPChainState struct {
 ..
 // list of remote chains
 // type&Version -> RemoteChainSelcs
 RemoteChainSelcs []uint64 // eg: [1,2,3]


 // map of remote chains to tokens configured for billing
 // type&Version -> RemoteToBillingTokens
 RemoteToBillingTokens map[uint64][]sol.PublicKey // billing_1_TokenA, billing_2_TokenB


 // map of remote chains to tokens configured for tokenPools
 // type&Version -> RemoteToPoolTokens
 RemoteToPoolTokens map[uint64][]sol.PublicKey // pool_1_TokenA, pool_2_TokenB
}

when going from addressBook to state:

• we first check the static type using switch case, which we do right now
• we then deserialise the value instead of they dynamic type

[tt-cll]

As discussed offline, I think we should store the chain selectors instead of storing the source/dest PDAs and then add more flexibility in the values instead of having dynamic types

type SolCCIPChainState struct {
 ..
 // list of remote chains
 // type&Version -> RemoteChainSelcs
 RemoteChainSelcs []uint64 // eg: [1,2,3]


 // map of remote chains to tokens configured for billing
 // type&Version -> RemoteToBillingTokens
 RemoteToBillingTokens map[uint64][]sol.PublicKey // billing_1_TokenA, billing_2_TokenB


 // map of remote chains to tokens configured for tokenPools
 // type&Version -> RemoteToPoolTokens
 RemoteToPoolTokens map[uint64][]sol.PublicKey // pool_1_TokenA, pool_2_TokenB
}

when going from addressBook to state:

• we first check the static type using switch case, which we do right now
• we then deserialise the value instead of they dynamic type

will raise this for review after token pool merges

[github-actions]

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.

[cl-sonarqube-production]

Quality Gate passed

Issues
5 New issues
2 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube