Canton Network
permissioned · Canton/Kaleido (DTCC anchor deployment)
No assets on record here yet, so there is nothing to measure.
Assets
No tokenized-asset contract is on record for Canton Network. That is an absence in our register, not a finding that none exist.
What is being used
No activity sample has been read for this chain. That is an absence, not a zero.
How it works
How it works nothing stated — the evidence layer refused
The citation audit has no green verdict for today. Nothing about Canton's mechanics is rendered until the internal primitives evidence audit passes for the current evidence file. An absence here is a statement about our reading, not about the chain.
What changed, in full
S7 §1 (DTCC DTS live on Canton + private Besu per dated 2026-10-28 launch PR; SG $10M tokenized USTs + BNP Paribas intraday lending [vendor page]); promoted wa… 2026-11-11 · doc-derived · from the chain row (no dated diff for this chain yet)
Raw record
In one line: S7 §1 (DTCC DTS live on Canton + private Besu per dated 2026-10-28 launch PR; SG $10M tokenized USTs + BNP Paribas intraday lending [vendor page]); promoted watch->core 2026-11-11 2026-11-11 · doc-derived · from the chain row (no dated diff for this chain yet)
Snapshot note: P1a live rowset (contracts+usage); P0 baseline hash in as_of='2026-11-11' row
Last updated: snapshot 2026-11-18 07:30:00 · usage — (none recorded) · KB as_of 2026-11-11
The full timeline for this chain — contract changes and watch events merged, dated, and linked.
Coming and watched1
What's coming
No public testnet is documented; institutions run their own nodes in production-like environments, and the node-as-a-service model leaves the public endpoint unknown — an honest gap, per the 2026-11-11 record. 1
One watch is armed: the first CIP-56 live token on Canton, pending until competitive cycle 33. 2
- an internal evidence file (canton.network developer surfaces) · 2026-11-11 · secondary · https://www.canton.network
- knowledge.db (read-only) — watches · kb_as_of 2026-11-18 08:37:10
What’s coming — measured on the test cluster not looked at
Nothing on the test cluster has been LOOKED AT for this chain. 0 issuer-owned mainnet addresses would be scanned, and the scanner refused the chain because no endpoint here is proven from the operator’s own documentation. That is a gap in our coverage — not a statement about what the issuer is doing.
An endpoint is proven only after a live response is recorded from this host, dated. A remembered URL is not a proven one, and a scan that guessed one would produce confident nonsense.
Readings0
Per-contract charts
No usage rows recorded for this chain (absent, not zero) — no chart is drawn, because there is nothing measured to draw.
Assets & activity
No contracts on this chain, so no asset rows can join — the absence is inherited from the contracts table (absent, not zero).
Usage history 0 rows
No usage rows recorded for this chain (absent, not zero). Usage metrics are recorded per snapshot; an empty table means none have been recorded yet, not that activity is zero.
How this chain is measuredidentity, capabilities, gaps
Canton is where the DTCC's Tokenization Service runs live: twenty DTC participants since 2026-10-28, and 0 contracts visible from public surfaces to this knowledge base. 12 The homepage claim, fetched 2026-11-12, is a public chain with privacy: private by design, with per-institution instances settling via ZK proofs on a shared observable surface. 34 the internal corroboration source could not be matched by institution name this run, because no institution links are on record for this chain. 5
- DTCC press release 2026-10-28 (re-verified 2026-11-11) · 2026-10-28 · primary · https://www.dtcc.com/press-releases/2026/dtcc-tokenization-service-goes-live · STALE (21 d old, limit 14)
- knowledge.db (read-only) — contracts (zero rows) · kb_as_of 2026-11-18 08:37:10
- canton.network homepage (page undated, fetched 2026-11-12) · 2026-11-12 · primary (vendor, page undated) · https://www.canton.network
- KB chains row + an internal evidence file entity model · 2026-11-11 · secondary · https://www.canton.network
- internal corroboration note, 30-day window
Why built
The homepage claim, fetched 2026-11-12: unlock digital asset liquidity on the only public chain with privacy — the page is undated, so the claim stays vendor-sourced in this knowledge base. 1
- canton.network homepage (page undated, fetched 2026-11-12) · 2026-11-12 · primary (vendor, page undated) · https://www.canton.network
Who is building
No issuer is linked to this chain in the knowledge base — 0 contracts, 0 issuers — so every name here comes from dated external claims. 1
The DTCC Tokenization Service went live on Canton on 2026-10-28 with 20 DTC participants and 17 partners, including Barclays, BNP Paribas, Citi, Fidelity, J.P. Morgan, Morgan Stanley, State Street, and UBS. 2
Société Générale moved $10M in tokenized US Treasuries as collateral, and BNP Paribas runs its own node and does intraday securities lending, per the 2026-11-11 record; the first US tokenized insurance ran in November 2025. 3
Canton is private by design: per-institution instances settle via ZK proofs on a shared observable surface, under the CIP-56 standard, per the 2026-11-11 record. 4
- knowledge.db (read-only) — issuers resolved via contracts on the chain · kb_as_of 2026-11-18 08:37:10
- DTCC press release 2026-10-28 (re-verified 2026-11-11) · 2026-10-28 · primary · https://www.dtcc.com/press-releases/2026/dtcc-tokenization-service-goes-live · STALE (21 d old, limit 14)
- canton.network (re-verified 2026-11-11) · 2026-11-11 · primary (vendor) · https://www.canton.network
- KB chains row + an internal evidence file entity model · 2026-11-11 · secondary · https://www.canton.network
Perspectives
The 2026-11-11 read flags both mentions numbers as stale: the '$100T asset inventory' quote and the DTCC '2H 2026 rollout' quote, both superseded by a service live since 2026-10-28. 1
The rwa.xyz entry — $370.5B against 2 assets — leaves notional versus live unresolved, and the 2026-11-11 read says do not quote it as live value. 2
The discovery rule for this chain, 2026-11-11: vendor sites answer the questions issuer PRs leave open, so a vendor claim stays claimed, not counted, until a second source confirms it. 3
- an internal evidence file (stale-quote audit) · 2026-11-11 · secondary · https://www.canton.network
- an internal evidence file · 2026-11-11 · secondary · https://rwa.xyz
- an internal evidence file · 2026-11-11 · secondary · https://www.canton.network
What we cannot see
No endpoint on this chain is reachable from this host, and no snapshot rowset has been recorded — the census records absence, not zeros. 1
The 0 is a measurement boundary, not a finding: no public RPC path is proven from this host, while the 2026-10-28 record says the DTCC service is live on this chain. 23
- knowledge.db (read-only) — rowset census (contracts, usage, snapshots, watches, kb_meta) · kb_as_of 2026-11-18 08:37:10
- knowledge.db (read-only) — contracts (zero rows) · kb_as_of 2026-11-18 08:37:10
- DTCC press release 2026-10-28 (re-verified 2026-11-11) · 2026-10-28 · primary · https://www.dtcc.com/press-releases/2026/dtcc-tokenization-service-goes-live · STALE (21 d old, limit 14)
What runs on it (measured)
0 contracts recorded for this chain in knowledge.db (kb_as_of 2026-11-18) — 0 — watch-tier access; canton was fully measured by probe ALPHA. 1
Its story here is institutional: dated external claims (Traction · Reported, Who is building), not on-chain measurement.
- knowledge.db (read-only) — contracts (zero rows) · kb_as_of 2026-11-18 08:37:10
Traction
Measured
No usage rows recorded for this chain yet — absent, not zero; the first census lands here. 1
- knowledge.db (read-only) — usage rows · kb_as_of 2026-11-18 08:37:10
Capability set
No capability rows recorded for this chain (absent, not zero). Capabilities are an explicit set per contract — an empty table means none have been recorded, not that capabilities are off.
Standards on this chain
| Standard | Kind | Status | Conformance on our register | Registry read |
|---|---|---|---|---|
| CIP-0112 Canton Network Token Standard V2 - Improvements for Privacy, Performance and Traditional Accounting | token | Proposed — not live | conformance not joined for this row yet — that is an absent join, not a zero and not a measurement | |
| CIP-56 CIP-56 (Canton token standard) | token | Recorded as in force — our reading | conformance not joined for this row yet — that is an absent join, not a zero and not a measurement |
A proposed standard is not a capability. Where a contract here is measured against one, the contract page carries the reading.
Identity
- Type
- permissioned
- Operator
- Canton/Kaleido (DTCC anchor deployment)
- Token standards
- CIP-56
- Gas model
- not probed (no public RPC path proven yet)
- Privacy model
- private by design — little observable from public surfaces
- Agent surfaces
- none proven (docs.r3.com 403 — walled)
- Last proven endpoint
- none — access probe is P3
source: S7 §1 (DTCC DTS live on Canton + private Besu per dated 2026-10-28 launch PR; SG $10M tokenized USTs + BNP Paribas intraday lending [vendor page]); promoted watch->core 2026-11-11 · as_of 2026-11-11 · doc-derived
Honest gaps
- 0 contracts: 0 — watch-tier access; canton was fully measured by probe ALPHA