Canton Validator

A Canton validator is a node that executes smart contracts, stores its view of ledger data, and participates in consensus for the transactions it is actually involved in. It is the primary technical footprint an organization has on the Canton Network.

This page explains what a validator does, why it matters, and how it differs from validators on networks like Ethereum.

High-level definition

A Canton validator is a node that:

• Hosts one or more PartyIDs
• Stores and processes only the contracts and transactions where those parties are stakeholders
• Participates in consensus for those transactions, in coordination with other relevant validators and synchronizer infrastructure

Additionally a Canton validator may run one or more Canton applications, however not all do.

In practice, a validator is your “gateway” into Canton: the node that connects you to the network, runs your Canton applications, and exposes your institution’s private view of the global virtual ledger.

Why validators matter

Validators are the anchor for how institutions participate in Canton.

• Control over data
  Validators only receive and store transaction data that involves their hosted parties. This allows institutions to keep sensitive positions, pricing, and flows on infrastructure they operate, rather than replicating them to a public chain.

• Direct access to applications and liquidity
  Running a validator is required to connect to the Global Synchronizer and interact directly with Canton applications for assets, markets, and payments.

• Alignment with regulatory and operational requirements
  Institutions can integrate validators into existing controls for security, audit, and monitoring, aligning Canton participation with internal risk and compliance frameworks.

• Eligibility for network economics
  A validator is typically a prerequisite for participating in network‑level economics, rewards, or incentives associated with Canton activity.

For stakeholders, a validator is the difference between consuming Canton as a service and participating in the transaction fabric of tokenized markets.

Typical responsibilities and integrations

Validator operations usually include:

• Infrastructure operations (availability, patching, monitoring, maintenance, upgrades)
• Connectivity to Canton synchronization domains and the Global Synchronizer
• Integration into internal systems (treasury, risk, trading, back office)
• Logging, audit, and evidence collection for regulators and internal control functions

Because validators are where Canton meets existing systems, they are often managed jointly by architecture, security, and operations teams.

How Canton validators differ from Ethereum validators

The term “validator” is used on both Canton and Ethereum, but the role and assumptions are different.

Data visibility

• Ethereum validators
  • See all transactions and the full chain state.
  • Replicate and validate every block, regardless of whether their operator is a stakeholder in a given transaction.
• Canton validators
  • Only store and process data for contracts and transactions where their hosted parties are stakeholders.
  • Do not have a full copy of all application state on the network.

Validation scope

• Ethereum
  • A rotating set of validators collectively validate all transactions and maintain a single global state machine.
• Canton
  • Only the validators involved in a particular transaction validate it.
  • Synchronizers provide the shared ordering service for cross‑domain workflows.

Operational implications

• Ethereum
  • Running a validator means tracking all network activity, managing stake, and being exposed to protocol‑level incentives and penalties across the entire chain.
• Canton
  • Running a validator means operating infrastructure sized to your participation and applications, with traffic and storage proportional to your actual business activity on Canton.

For decision‑makers, the key point is that on Canton, validator operations scale with your use cases and counterparties, not with the entire network’s global throughput.