01
Network key management
Stronghold-KMS protects Canton root namespace, namespace intermediate, signing, encryption and sequencer authentication keys. Controls reflect each key’s role, separating cold root authority from operational key use.
NETWORK
MPCH INFRASTRUCTURE
YOUR KEYS.
YOUR NETWORK.
YOUR CONTROL.
Key management and managed infrastructure for institutions building on Canton.
HUMAN AUTHORITY. CRYPTOGRAPHICALLY ENFORCED.
Pause motion
BUILT INTO
CANTON NETWORK
Founding infrastructure provider
Global Synchronizer super validator operator
01 / CANTON OPERATIONS
CANTON INFRASTRUCTURE SERVICES.
The infrastructure is only part of the job. MPCH brings key management, secure access and operating controls together, so your institution retains authority over its Canton operations.
02
Operate with resilience
Managed validators, secure network access and shared-validator support for institutional operations.
03
Security & governance advisory
Define who can authorize key use, how approval policies are enforced and what evidence demonstrates control. MPCH advises on security architecture, governance, separation of duties and recovery planning.
02 / THE KEY AUTHORITY LAYER
PROTECT THE KEYS.
CONTROL THEIR USE.
A validator and the authority behind it should not share the same point of failure. Separate root authority from day-to-day operations.
STRONGHOLD-KMS / CONTROL ARCHITECTURE
CLIENT-OWNED KEYS. POLICY-GOVERNED USE.
Watch Stronghold-KMS for Canton
ISOLATE THE ROOT
Keep the highest authority
off the operating node.
Root namespace keys stay offline, separate from the validator. Protected key operations require independent approval.
- Offline root authority
- Client-defined policy and quorum
- Controlled delegation to operational keys
CONTROL KEY USE
A request is not
an authorization.
Protected signing operations must satisfy the configured policy and quorum. Key-use controls and records of approvals support institutional oversight.
- Independent authorization
- Signing controls and intervention
- Evidence of requests and approvals
PLAN BEFORE AN INCIDENT
Recovery is an
operating discipline.
Plan how to restore service and re-establish signing authority. Recovery procedures must reflect the key type, operating model and scope of the incident.
- Defined recovery procedures
- Reviewable approval records
- Namespace migration where required
Transaction content, destinations and limits remain in the client policy layer.
IN DEVELOPMENT · TARGET Q1 2027
A DEDICATED NETWORK.
YOUR ECOSYSTEM.
Bring your participants and applications together on dedicated Canton infrastructure, operated by MPCH.
We are developing managed sub-networks for institutions that want their own operating environment and traffic economics.
YOUR INSTITUTION
Your ecosystem
MPCH-OPERATED INFRASTRUCTURE
Dedicated managed sub-network
Operations
Key authority
Traffic pricing
01
Participants
02
Applications
03
Workflows
Illustrative architecture. Scope, traffic pricing and rollout timing are subject to technical and commercial agreement.
03 / BEFORE WE BEGIN
BUILT AROUND
YOUR OPERATIONS.
Start with the responsibilities, controls and infrastructure your institution needs.
Who owns and controls the keys?
Your organization owns the keys and assets. MPCH operates the key-management layer under your instructions, with policy-defined approval controls.
Are dedicated sub-networks live today?
Dedicated managed sub-networks are in development, with a target of Q1 2027. They are not presented here as live deployments. Scope, timing and traffic pricing are confirmed through technical and commercial discussions.
Can a compromised root key simply be rotated?
No. Canton root namespace keys cannot simply be rotated. A compromised root can require a new namespace and migration. This is why separating and protecting root authority matters.
Read Canton key-management guidance ↗How do we define the right operating model?
Begin with your Canton deployment, key responsibilities, approval requirements and recovery needs. MPCH can then scope the key-management and infrastructure services around that model.
DISCUSS YOUR OPERATING MODEL
BUILD ON CANTON.
KEEP CONTROL.
Talk to MPCH about key management,
network operations or a dedicated ecosystem.