Canton

CC CMC #24 in the snapshot

Canton connects applications through shared synchronization while limiting transaction visibility to the parties entitled to see it. Its Global Synchronizer coordinates activity across participating ledgers.

Profile checked 14 Nov 2026Asset ranks captured 14 Nov 2026Snapshot & methodology ↗

01 / THE PURPOSE

What is Canton for?

The design targets workflows such as exchanging a tokenized security for payment when counterparties need common settlement but cannot publish every contractual detail. Application access policies remain separate from the synchronization service.

02 / THE ARCHITECTURE

Three questions about the machinery.

How does it agree?

Consensus & security

There are two different agreements. Affected stakeholders validate their views against Daml authorization rules. Synchronizer sequencers order encrypted messages using Byzantine fault tolerant consensus. “Proof of Stakeholder” refers to parties interested in a contract, not simply whoever owns the most CC.

Where do instructions run?

Execution model

Daml contracts express rights, obligations and permitted actions. Participants check their relevant transaction portions; the protocol coordinates a commit or abort across them. It does not require every network node to execute and inspect every business record.

What is the token for?

CC in the system

CC funds non-transferable traffic credits for Global Synchronizer usage and supports operator incentives. Current validator rewards depend on activity, rather than uptime alone. CC balance and transaction records are publicly visible even though other application contracts can be private.

03 / THE DESIGN CHOICES

What comes with the design?

Each architecture makes choices about security, performance, coordination, and who can participate.

Synchronizer governance and the relevant stakeholder set determine trust; owning CC does not grant unrestricted validator access.
Private application data cannot be independently inspected by an arbitrary public observer.

04 / IN PRACTICE

Follow one use.

An institution transfers a bond only if the buyer’s payment also commits. Each side validates its authorized contract view while the synchronizer coordinates the shared outcome.

05 / CHECK THE EXPLANATION

Sources & snapshot.

Network descriptions use the references below. The CoinMarketCap snapshot determines which assets are in scope and their captured rank; it does not assess the quality of a network.

Two-Layer Consensus Canton Network documentation contributors
Canton Coin and the Global Synchronizer Canton Network documentation contributors
Privacy Model Explained Canton Network documentation contributors
CoinMarketCap top 100 snapshot Captured 14 Nov 2026 · See the complete scope audit
Canton (CC) on CoinMarketCap Captured asset rank #24

Profile checked 14 Nov 2026. Network designs and ranked positions can change.