What are Super Validators on @CantonNetwork ? > Canton uses a two layer validation model designed for institutional finance. > At the core of this model are Super Validators. > Super Validators are invited, trusted organizations that operate the Global Synchronizer - the public coordination layer of the Canton Network. > This design allows Canton to be public and interoperable, while preserving institutional-grade privacy. > Current Super Validators: The existing super validator set reflects a cross section of institutional finance and Web3 infrastructure, including: - 5 North - 7Ridge @7RIDGE1 - Angelhack @AngelHack - BitGo @BitGo - Bitwave @BitwavePlatform - Blockdaemon @BlockdaemonHQ - Broadridge @Broadridge - Canton Foundation @CantonFdn - Chainlink @chainlinklabs - Circle @circle - CoinMetrics @coinmetrics - Copper @CopperHQ - Cumberland @CumberlandSays - Dfns @dfnsHQ - Digital Asset @digitalasset - DTCC @The_DTCC - Elliptic @elliptic - Figment @Figment_io - Hypernative @HypernativeLabs - IntellectEU @IntellectEU - Kaiko @KaikoData - Kiln @Kiln_finance - LayerZero @LayerZero_Core - Ledger @Ledger - Liberty City Ventures @LCVentures - Lukka Inc. @Lukka - MPCH - Obsidian Systems @obsidian_llc - Proof Group @proofgp - Quantsamp @Quantstamp - SBI digital asset holdings @SBI_DAH - Taurus @taurus_hq - Tradeweb @Tradeweb - TRM @trmlabs - Zerohash @zerohashx Note: This is not a retail validator set - it’s intentionally composed of entities already embedded in global financial infrastructure. How Super Validators differ from Validators: Super Validators: > They are responsible for: - Run the Global Synchronizer - Validating every Canton Coin ($CC) transfer - Running shared public utilities - Governing upgrades to core code and services - Acting as a trust-minimized message layer between private Cantons (without seeing private transaction data) Validators (Canton nodes at the edge): - Validate business logic inside a specific Canton - Execute smart contracts (written in Daml) - Can be private, permissioned, or institution specific - Do not operate the network-wide synchronization layer In short: Validators handle private execution. Super Validators handle public coordination. How one becomes a Super Validator > Unlike most L1s, Canton does not use staking or capital-based selection. > They are chosen based on: - Operational contribution - Infrastructure reliability - Ecosystem value > This avoids: - Validator centralization via capital - Misalignment with institutional incentives How this model differs from other L1s: > Most public L1s: - Secure the network through capital staking - Treat all validation as homogeneous - Optimize for openness over confidentiality > Canton: - Separates execution from coordination - Optimises for privacy - Uses a public network only where shared trust is required - Aligns governance with real-world financial operators Takeaway: Canton’s Super Validator model is not designed for maximal decentralization, it’s designed for credible neutrality in institutional finance. That enables: - Atomic settlement across institutions - Interoperability without data leakage - A public network institutions can actually use
