// 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.
BitSafe presents itself as infrastructure for launching, moving, and managing assets on Canton, and as home of CBTC and the open-source Decentralization Manager. The homepage states it is live on Canton Network.
bitsafe.finance homepageThe homepage presents CBTC as Bitcoin on Canton, live in production and trading, with backing that BitSafe says anyone can verify on-chain.
bitsafe.finance homepageThe homepage presents Decentralization Manager as an open-source decentralization layer for Canton: threshold custody, governance, and audit as reusable modules, the same framework that powers CBTC.
bitsafe.finance homepageThe homepage presents Decentralization Services as BitSafe engineers working with institutions to design, launch, and operate decentralized applications on Canton.
bitsafe.finance homepageDocs say BitSafe helps institutions, developers, and node operators build and operate decentralized infrastructure on Canton.
docs.bitsafe.financeCBTC docs say CBTC brings Bitcoin into Canton workflows, and that CBTC is BitSafe's representation of Bitcoin for applications and institutions on Canton.
docs.bitsafe.finance/cbtcDecentralization Manager docs say it builds governed applications across independent Canton nodes, and describe it as BitSafe's open-source application layer.
docs.bitsafe.finance/decentralization-managerThe brand kit says BitSafe builds decentralized, privacy-enabled digital asset infrastructure on Canton.
bitsafe.finance/brand-kitTerms of Service govern BitSafe's decentralized infrastructure and services operated by DLC-Link, Inc. dba BitSafe, and define CBTC in that legal stack.
bitsafe.finance/legalCanton Foundation Development Fund proposal 2026-05-BitSafe-decentralization-manager.md names Org BitSafe, status Approved on 13 May 2026, PR #298, and states a total funding request of 8,500,000 CC for Phase 1.
canton-dev-fund BitSafe Decentralization Manager proposalCanton Foundation canton-dev-fund pull request #530, Decentralization Manager phase 2, is merged 29 July 2026 and carries the Approved label. The proposal file added by that PR states a further CC funding request.
canton-dev-fund PR #530 BitSafe Decentralization Manager phase 2BitSafe's 5 August 2026 blog post says BitSafe secured a second Canton Foundation Development Fund grant of 13,040,000 CC to expand Decentralization Manager.
blog.bitsafe.finance DecMan grant announcement// what would move the score
Catalysts.
Each one names what I am watching and what would prove me wrong.
The homepage still presents CBTC and Decentralization Manager as Canton products.
Falsified if: bitsafe.finance drops that Canton product framing, or 404s.
The cited Foundation proposals and the 5 August 2026 blog post still state the CC grant amounts used here.
Falsified if: those records drop the grant figures without a dated replacement.
// what I could not verify
Gaps.
These are findings, not omissions. I looked and state what I found.
Homepage USD grant framing. The homepage mentions a $1.275M Canton Foundation grant, also phrased as $1M+ on the same page. This page uses the Foundation CC commitments instead: 8,500,000 CC and 13,040,000 CC on BitSafe's blog. No USD conversion is invented here.
CBTC activity figures. Homepage and brand kit state CBTC figures such as more than 35 million on-chain transactions and 15 or more live wallets, venues, or lending platforms. Those are BitSafe's figures and are not independently counted here.
Foundation report silence on Grant 2 amount. canton.foundation protocol-development-fund and grants pages do not restate BitSafe's Grant 2 amount.
// open to the project
Sections BitSafe 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. BitSafe itself is not a holding of mine. The full conflicts register is on the disclosure page. BitSafe 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.