// the evidence
Claims, and where each one stands.
Every claim on this page carries its evidence tier. Nothing is smoothed over, and nothing a project told me is presented as something I checked.
Copper's developer changelog for 13 November 2025 lists, under New features, an entry for new transaction types for accepting or rejecting deposits on-chain.
developer.copper.co changelogThe BlockchainTransactionType enum defines accept-deposit as accepting an incoming deposit that requires explicit on-chain acceptance, and names Canton as an example.
developer.copper.co BlockchainTransactionTypeClearLoop Introduction says ClearLoop is an off-exchange settlement solution for institutional investors, and that it allows Copper clients to settle on Copper infrastructure.
developer.copper.co ClearLoop introductionCopper markets ClearLoop as a Collateral Mobility Network, with copper.co stating that ClearLoop connects custodians, exchanges, and venues on one network.
copper.co ClearLoop NetworkThe homepage describes Copper as unifying traditional and digital asset markets through a single infrastructure for custody, trading, and settlement.
copper.co homepageThe About page says Copper has been building infrastructure for digital asset markets since 2018, and that it launched in London that year with MPC-based custody.
copper.co/company/aboutA CCTools directory page labels Copper Live Custody and describes institutional custody and a Canton Network validator. Super Validator and Foundation-member lines on that directory page are announced here.
cctools.network/ecosystem/copper// what would move the score
Catalysts.
Each one names what I am watching and what would prove me wrong.
The developer portal still defines accept-deposit with Canton as an example.
Falsified if: that enum page drops the Canton example, or 404s.
CCTools still labels Copper live custody with a Canton validator role. A dated Copper own-surface Super Validator statement would let that directory line move off announced.
Falsified if: the CCTools Copper page drops those labels, or 404s.
// what I could not verify
Gaps.
These are findings, not omissions. I looked and state what I found.
Super Validator on own surface. Super Validator and Canton Foundation member lines appear on the CCTools directory page. No matching Super Validator statement was located on copper.co or the developer portal.
ClearLoop-on-Canton client live claim. Own-surface evidence shows Canton deposit and allocation API types. A dated Copper marketing or product page stating ClearLoop client settlements live on Canton was not located.
Directory treasury figures. CCTools Role on Canton copy names a Tharimmune / Canton Strategic Holdings treasury custodian figure. That directory figure is not restated here.
Leadership roster on About. CCTools Team copy names Amar Kuchinad as CEO. The About page did not expose a matching named leadership roster in the static text extracted, so CEO naming stays directory-side.
// open to the project
Sections Copper can fill.
These stay empty until the project supplies them. Anything supplied is labeled as supplied, dated, and never rendered as something I verified. Declining changes nothing else on this page.
Architecture
How the product is built, in the team's own words.
Audit
Any audit, review or internal security practice not published today.
Roadmap
What ships next and when, so the catalysts above can carry real dates.
Usage figures
Published usage with a methodology, so a count can move off announced tier.
// conflicts
Position.
Position disclosure. I hold $CC and $CNTN. This page covers a Canton-native product, which triggers disclosure under my map. Copper itself is not a holding of mine. The full conflicts register is on the disclosure page. Copper has no commercial relationship with Canton Catalyst, and nothing here was requested, reviewed or paid for.
// corrections
Correction log.
No corrections recorded. First published 16 September 2026.