Skip to content

Clear Signing coverage tracker Bridges

Circle CCTP

11 contracts of Circle CCTP on Ethereum, Base, Arbitrum One and OP Mainnet, checked against the Clear Signing registry and their recent transactions.

Status
Uncovered
Website
circle.com

Contracts

0 of 11

contracts here have a descriptor in the registry

  • 0 covered
  • 0 partial
  • 11 uncovered

Recent traffic

0%

of recent transactions a wallet could clear-sign

0% of recent senders

Transactions count every call. Senders count each address once per function, so a relayer bot counts once however many calls it sends.

Registry at ef582c2, committed 4 November 2026On-chain reads 6 November 202612,698 transactions a day across 11 contractsThe data, as JSON
Contracts

11 contracts, busiest first

For each: its address and where it came from, the registry's descriptor for it, the functions it formats, and which of its recent calls a wallet could clear-sign.

Arbitrum One

CCTP MessageTransmitterV2

Mint USDC on the destination chain (receiveMessage) when the user completes a transfer themselves

Uncovered
Address
0x81D4…4B64MessageTransmitterV2 · v2
Descriptor
None in the registry
Functions
No verified ABI to count them
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 6 November 2026 · 4,607 a day
Sourcify
Not verified
Address from
registry.npmjs.org

Most-called functions

  1. 0x57ecfd28100%Not formatted · name not known · 78 sendersTry it: a real call of 0x57ecfd28 in the playground

Base

CCTP MessageTransmitterV2

Mint USDC on the destination chain (receiveMessage) when the user completes a transfer themselves

Uncovered
Address
0x81D4…4B64MessageTransmitterV2 · v2
Descriptor
None in the registry
Functions
0 of 18 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 6 November 2026 · 2,392 a day
Sourcify
Verified, exact match
Address from
registry.npmjs.org

Most-called functions

  1. receiveMessage(bytes,bytes)100%Not formatted · 135 sendersTry it: a real call of receiveMessage(bytes,bytes) in the playground

Ethereum

CCTP MessageTransmitterV2

Mint USDC on the destination chain (receiveMessage) when the user completes a transfer themselves

Uncovered
Address
0x81D4…4B64MessageTransmitterV2 · v2
Descriptor
None in the registry
Functions
0 of 18 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 6 November 2026 · 2,094 a day
Sourcify
Verified, exact match
Address from
registry.npmjs.org

Most-called functions

  1. receiveMessage(bytes,bytes)100%Not formatted · 158 sendersTry it: a real call of receiveMessage(bytes,bytes) in the playground

Arbitrum One

CCTP TokenMessengerV2

Burn USDC to bridge it natively (depositForBurn, depositForBurnWithHook)

Uncovered
Address
0x28b5…cf5dTokenMessengerV2 · v2
Descriptor
None for this deployment
Described elsewhere
calldata-TokenMessengerV2.jsonFor the same address on Polygon; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 20 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 6 November 2026 · 1,345 a day
Sourcify
Verified, exact match
Address from
registry.npmjs.org

Most-called functions

  1. depositForBurnWithHook(uint256,uint32,bytes32,address,bytes32,uint256,uint32,bytes)72%Not formatted · 517 sendersTry it: a real call of depositForBurnWithHook(uint256,uint32,bytes32,address,bytes32,uint256,uint32,bytes) in the playground
  2. depositForBurn(uint256,uint32,bytes32,address,bytes32,uint256,uint32)28%Not formatted · 111 sendersTry it: a real call of depositForBurn(uint256,uint32,bytes32,address,bytes32,uint256,uint32) in the playground

Base

CCTP TokenMessengerV2

Burn USDC to bridge it natively (depositForBurn, depositForBurnWithHook)

Uncovered
Address
0x28b5…cf5dTokenMessengerV2 · v2
Descriptor
None for this deployment
Described elsewhere
calldata-TokenMessengerV2.jsonFor the same address on Polygon; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 20 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders891 transactions, 5 – 6 November 2026 · 910 a day
Sourcify
Verified, exact match
Address from
registry.npmjs.org

Most-called functions

  1. depositForBurnWithHook(uint256,uint32,bytes32,address,bytes32,uint256,uint32,bytes)50%Not formatted · 74 sendersTry it: a real call of depositForBurnWithHook(uint256,uint32,bytes32,address,bytes32,uint256,uint32,bytes) in the playground
  2. depositForBurn(uint256,uint32,bytes32,address,bytes32,uint256,uint32)50%Not formatted · 140 sendersTry it: a real call of depositForBurn(uint256,uint32,bytes32,address,bytes32,uint256,uint32) in the playground

Ethereum

CCTP TokenMessengerV2

Burn USDC to bridge it natively (depositForBurn, depositForBurnWithHook)

Uncovered
Address
0x28b5…cf5dTokenMessengerV2 · v2
Descriptor
None for this deployment
Described elsewhere
calldata-TokenMessengerV2.jsonFor the same address on Polygon; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 20 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 5 – 6 November 2026 · 722 a day
Sourcify
Verified, exact match
Address from
registry.npmjs.org

Most-called functions

  1. depositForBurn(uint256,uint32,bytes32,address,bytes32,uint256,uint32)74%Not formatted · 242 sendersTry it: a real call of depositForBurn(uint256,uint32,bytes32,address,bytes32,uint256,uint32) in the playground
  2. depositForBurnWithHook(uint256,uint32,bytes32,address,bytes32,uint256,uint32,bytes)27%Not formatted · 185 sendersTry it: a real call of depositForBurnWithHook(uint256,uint32,bytes32,address,bytes32,uint256,uint32,bytes) in the playground

OP Mainnet

CCTP MessageTransmitterV2

Mint USDC on the destination chain (receiveMessage) when the user completes a transfer themselves

Uncovered
Address
0x81D4…4B64MessageTransmitterV2 · v2
Descriptor
None in the registry
Functions
0 of 18 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 4 – 6 November 2026 · 474 a day
Sourcify
Verified, exact match
Address from
registry.npmjs.org

Most-called functions

  1. receiveMessage(bytes,bytes)100%Not formatted · 46 sendersTry it: a real call of receiveMessage(bytes,bytes) in the playground

OP Mainnet

CCTP TokenMessengerV2

Burn USDC to bridge it natively (depositForBurn, depositForBurnWithHook)

Uncovered
Address
0x28b5…cf5dTokenMessengerV2 · v2
Descriptor
None for this deployment
Described elsewhere
calldata-TokenMessengerV2.jsonFor the same address on Polygon; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 20 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 24 October – 6 November 2026 · 74 a day
Sourcify
Verified, exact match
Address from
registry.npmjs.org

Most-called functions

  1. depositForBurn(uint256,uint32,bytes32,address,bytes32,uint256,uint32)98%Not formatted · 178 sendersTry it: a real call of depositForBurn(uint256,uint32,bytes32,address,bytes32,uint256,uint32) in the playground
  2. depositForBurnWithHook(uint256,uint32,bytes32,address,bytes32,uint256,uint32,bytes)2%Not formatted · 13 sendersTry it: a real call of depositForBurnWithHook(uint256,uint32,bytes32,address,bytes32,uint256,uint32,bytes) in the playground

Ethereum

CCTP TokenMessenger V1

Legacy CCTP V1 burn (depositForBurn); Circle phases V1 out from 2026-10-31 to 2026-12-01

Uncovered
Address
0xBd3f…3155TokenMessenger · v1
Descriptor
None in the registry
Functions
0 of 12 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 12 October – 6 November 2026 · 40 a day
Sourcify
Verified, partial match
Address from
registry.npmjs.org

Most-called functions

  1. depositForBurn(uint256,uint32,bytes32,address)>99%Not formatted · 231 sendersTry it: a real call of depositForBurn(uint256,uint32,bytes32,address) in the playground
  2. depositForBurnWithCaller(uint256,uint32,bytes32,address,bytes32)<1%Not formatted · 1 senderTry it: a real call of depositForBurnWithCaller(uint256,uint32,bytes32,address,bytes32) in the playground

Arbitrum One

CCTP TokenMessenger V1

Legacy CCTP V1 burn (depositForBurn); Circle phases V1 out from 2026-10-31 to 2026-12-01

Uncovered
Address
0x1933…E08ATokenMessenger · v1
Descriptor
None in the registry
Functions
0 of 12 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders968 transactions, 4 October – 6 November 2026 · 29 a day
Sourcify
Verified, partial match
Address from
registry.npmjs.org

Most-called functions

  1. depositForBurn(uint256,uint32,bytes32,address)100%Not formatted · 347 sendersTry it: a real call of depositForBurn(uint256,uint32,bytes32,address) in the playground

Base

CCTP TokenMessenger V1

Legacy CCTP V1 burn (depositForBurn); Circle phases V1 out from 2026-10-31 to 2026-12-01

Uncovered
Address
0x1682…8962TokenMessenger · v1
Descriptor
None in the registry
Functions
0 of 12 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders10 transactions, 5 – 6 November 2026 · 10 a day
Sourcify
Verified, partial match
Address from
registry.npmjs.org

Most-called functions

  1. depositForBurn(uint256,uint32,bytes32,address)100%Not formatted · 7 sendersTry it: a real call of depositForBurn(uint256,uint32,bytes32,address) in the playground
Reading it

What these numbers say, and do not

  • Covered means the registry has a descriptor for the deployment and it formats at least 95% of what recent senders called. Partial means a descriptor formats less, or its reach could not be measured. Uncovered means the registry has no descriptor for it.
  • Described elsewhere means the registry has a descriptor for another deployment of Circle CCTP, on another chain or at another address, with functions this contract's recent senders call. It does not list this contract, which stays uncovered, and whether it fits is for its owner to check.
  • By transactions, every call counts. By senders, each address counts once for each function, so a relayer bot counts once however many calls it sends.
  • A descriptor is not an audit, and wallets decide which descriptors they trust.

How we measureWhat the tracker does not claimAll protocols

Get covered

Get Circle CCTP clear-signed

Of the 11 contracts of Circle CCTP here, 11 have no descriptor in the registry. We write, test and submit descriptors.