// 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.
Cancore describes itself as a Canton-native platform for self-custody trading, atomic settlement, and automation across public-chain liquidity.
cancore.io homepage metaThe user guide documents cross-chain atomic swaps with a fee structure of 1 percent platform fee per direction in the token being sent, plus a Canton network fee.
docs.cancore.io/usecases fee + HTLCThe same guide describes Proposal, Counter-Proposal, Claim, and Refund as Canton ledger actions over Daml HTLC contracts, where a Proposal locks tokens under a hashLock on Canton.
docs.cancore.io/usecases Canton + EVM conceptsThe same guide documents EnableCC as a one-time onboarding transaction that activates a Canton account's ability to hold and use CC, and describes wallet types for participant-managed signing versus external keys.
docs.cancore.io/usecases EnableCC + use casesSDK overview describes two packages for wallet and dApp connector roles, and states neither package is published yet. Both sit at version 0.0.0.
docs.cancore.io/sdk/overviewA CCTools directory page labels Cancore Live under Interoperability and describes a settlement layer connecting Canton to public blockchains. Featured App and Validator lines on that directory page are announced here.
cctools.network/ecosystem/cancoreDocs point readers to swap.cancore.io as Open the app. DNS for that hostname failed, so the app host stays announced.
docs.cancore.io app pointer + DNS checkCancore documents connecting an AI agent to trade on a user's behalf through the @cancore/mcp package, compatible with MCP clients including Claude Code and Claude Desktop. The guide describes the agent proposing a trade and the human approving it separately in their own wallet, at a price the wallet computes at approval time, with the granted access scoped and revocable afterward.
docs.cancore.io Connect an AI agent guide// what would move the score
Catalysts.
Each one names what I am watching and what would prove me wrong.
cancore.io and docs.cancore.io still describe a Canton-native swap and HTLC guide.
Falsified if: either host drops that Canton product statement, or 404s.
Docs still point Open the app at swap.cancore.io, which did not resolve. A reachable public swap host would close that gap.
Falsified if: docs drop the app pointer without a replacement host, or the hostname stays unresolved through the next verify.
// what I could not verify
Gaps.
These are findings, not omissions. I looked and state what I found.
swap.cancore.io host unreachable. Official docs point Open the app to swap.cancore.io. DNS for that hostname failed. No alternate public app hostname with a measured swap session was confirmed.
Operator and founder on own surface. Five North operator language and Yiannis Varelas founder naming appear on the CCTools directory page. No matching operator or founder line was located on Cancore own pages.
Featured App and Validator on own surface. Those claims appear on the CCTools directory page. No matching statement was located on Cancore own surfaces.
Independent audit. No named third-party auditor, report date, or report URL for Cancore HTLC contracts or settlement paths was located. SDK docs mention unfinished work.
Homepage body is SPA-hydrated. cancore.io returned a Vite shell whose Canton-native product claim is carried in meta tags. Marketing body copy beyond those tags was not present.
// open to the project
Sections Cancore 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. Cancore itself is not a holding of mine. The full conflicts register is on the disclosure page. Cancore 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.