Skip to main content
Version: 1.15.0

Interface: ExplorerVerificationInput

Defined in: cct/evm/operation.ts:54

The deploy-side inputs a block explorer needs to verify a contract's source: its name and ABI-encoded constructor args, captured while deploying with no extra RPC.

Remarks​

A constructor-args companion, not proof of verification — nothing here is read back from the chain or submitted anywhere. A full submission also needs the source/compiler side (standard-json input plus the matching solc version and settings), which this SDK does not vendor; those ship in the @chainlink/contracts-ccip package.

Only available from execute, which deploys and so learns the address. The generateUnsigned* builders return the unsigned tx alone.

Example​

Verifying on Etherscan, whose "Constructor Arguments" field wants the args bare:

TypeScript
const { contractAddress, verification } = await cct.deployTokenPool({ ...params, wallet })
console.log(verification.contract) // 'LockReleaseTokenPool'
console.log(verification.encodedConstructorArgs.slice(2)) // drop the `0x`

Properties​

contract​

contract: string

Defined in: cct/evm/operation.ts:56

Contract name as compiled, e.g. BurnMintTokenPool; unqualified, matching the artifact.


encodedConstructorArgs​

encodedConstructorArgs: string

Defined in: cct/evm/operation.ts:58

0x-prefixed ABI-encoded constructor args, or just 0x when the constructor takes none.