We operate a validator on the Canton Network MainNet.

InfoDive Labs runs its own validator node on the Global Synchronizer, the production network of the Canton Network, and has since July 2026. Our engineers keep it upgraded, backed up and in sync.

Network
MainNet
Live since
July 2026
Role
Validator
Deployment
Splice, Docker Compose
Operated by
InfoDive Labs

What a validator is on Canton.

Not a block producer racing others for rewards. On Canton a validator is the node through which an organisation holds and transacts on the network, and the privacy model shapes everything about running one.

Only its own transactions

On Canton, only the stakeholders of a transaction see, validate and record their parts of it. A validator holds its parties' data, not the whole ledger.

Source

Outbound only

A validator needs no inbound connectivity. It needs outbound access on port 443 to every Super Validator.

Source

Its own backups are the record

Super Validators do not retain transaction details from applications they are not part of, so a validator's backups are the only way to recover that data.

Source

Getting onto MainNet.

MainNet is permissioned at the network edge. There is no sign-up form that ends in a running node; there is a sequence, and it is the same for everyone.

Validator onboarding docs
  1. ApprovalMainNet access is approved by the Tokenomics Committee, with a Super Validator as sponsor.
  2. Egress IP allowlistedThe node's static egress IP goes to the sponsor. Super Validators usually take 2 to 7 days to add it to their allowlists.
  3. Onboarding secretThe sponsor issues a one-time secret by hand. It expires after 48 hours.
  4. Rehearse, then MainNetNew versions reach DevNet, then TestNet, then MainNet. MainNet is never reset; DevNet and TestNet are, periodically.

What running one involves.

Onboarding happens once. Operating never stops. These are the duties that decide whether a node stays healthy, each linked to the documentation it comes from.

Run the node

The Docker Compose deployment runs a Canton participant, the validator app, the wallet and name service UIs, Postgres and an nginx proxy.

compose.yaml

Replace default auth

The Compose deployment's default authentication is insecure by design. A production node is configured with an OIDC provider.

validator_compose

Upgrade on the network's schedule

Replace the full release bundle, never only the image tag, and never delete databases or change secrets along the way.

validator_upgrades

Follow synchronizer upgrades

Since Splice 0.6.2, hard migrations are gone. Protocol upgrades run as logical synchronizer upgrades that participants follow automatically, if they are on a compatible release in time.

release notes

Back up, off the host

Node identities go to a secure location outside the host. Postgres is backed up at least every 4 hours.

validator_backups

Keep restores possible

A full restore needs a database backup under 30 days old, because sequencer pruning stops older participants from catching up.

disaster_recovery

Watch ingestion lag

A healthy validator ingests new data every round. Lag above 20 minutes means it is falling behind.

validator_health

Onboarding to Canton, or building on it?

Talk to the engineers who run our node: onboarding, the deployment, the upgrade routine, or the application you want to put on it. The long version of this page is in What It Takes to Run a Canton MainNet Validator.

Talk to an engineerBlockchain services

Canton and Canton Network are trademarks of Digital Asset. InfoDive Labs is an independent validator operator and is not affiliated with or endorsed by Digital Asset or the Canton Foundation.