Skip to main content
Version: 1.15.0

Variable: TokenPoolVersion

const TokenPoolVersion: { V1_5_0: "1.5.0"; V1_5_1: "1.5.1"; V1_6_0: "1.6.0"; V1_6_1: "1.6.1"; V2_0_0: "2.0.0"; }

Defined in: cct/evm/token-pool/contracts.ts:114

Known pool versions, low to high. Value order drives floor-match in resolveEncoder.

Type Declaration​

V1_5_0​

readonly V1_5_0: "1.5.0" = '1.5.0'

V1_5_1​

readonly V1_5_1: "1.5.1" = '1.5.1'

V1_6_0​

readonly V1_6_0: "1.6.0" = '1.6.0'

V1_6_1​

readonly V1_6_1: "1.6.1" = '1.6.1'

V2_0_0​

readonly V2_0_0: "2.0.0" = '2.0.0'

Remarks​

Exact-match allowlist. A pool resolves only if it reports one of these versions verbatim; an unlisted version (e.g. 1.6.2) throws CCTContractVersionUnsupportedError rather than being treated as its nearest lower neighbour. Pool ABIs have changed across minor versions (1.5.0 → 1.5.1 changed applyChainUpdates), so accepting an unseen version could build calldata for a function that does not exist. Floor-match is only how an op picks an encoder among these accepted versions.