Initialize CCT SDK with setPool#273
Conversation
| validateAddress(OPERATION, 'tokenAddress', params.tokenAddress) | ||
| validateAddress(OPERATION, 'poolAddress', params.poolAddress) |
There was a problem hiding this comment.
Should we go deeper and validate whether the address is a token or pool contract through typeAndVersion?
There was a problem hiding this comment.
Thinking of a generic abstract class, e.g. Operation that defines function signatures for validate, generate and execute. What are your thoughts?
| abstract readonly chain: Chain<F> | ||
| } |
There was a problem hiding this comment.
Should we add the function signatures for the chain-agnostic operations, i.e. generateUnsignedSetPool and setPool?
| "types": "./dist/all-chains.d.ts", | ||
| "default": "./dist/all-chains.js" | ||
| }, | ||
| "./cct/evm": { |
There was a problem hiding this comment.
Exposed under the subpath /evm for now; we probably want to expose just /cct with a barrel export
|
You must have Developer access to commit code to Chainlink Labs on Vercel. If you contact an administrator and receive Developer access, commit again to see your changes. Learn more: https://vercel.com/docs/accounts/team-members-and-roles/access-roles#team-level-roles |
1 participant
What
@chainlink/ccip-sdk/cctEVMTokenManagerwithgenerateUnsignedSetPool(build unsigned tx) andsetPool(sign + submit)setPooloperation module: validates params, encodessetPool(localToken, pool), discoversTokenAdminRegistryvia routerTokenManagerbase, submit action, address validations, and error typesWhy
ccip-contracts. This adds a first-class SDK path for CCT admin ops so consumers (partners / dapp team) can build and submit txs server-side with consistent validation and error handlingTesting
Notes