> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digitalasset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Onboarding process, architecture, security, and support.

## Overview

The **Covalidation Service (CVS)** is a managed infrastructure solution for the Canton Network that eliminates single points of failure for wallets and applications. By multi-hosting parties and distributing validation responsibilities across a redundant, high-availability network, CVS helps ensure services remain secure, available, and resilient without requiring organizations to operate every aspect of the infrastructure themselves.

***

## Key Operational and Security Benefits

The Covalidation Service is designed around resilience, redundancy, and operational security.

<Columns cols={2}>
  <Column>
    <Card title="2-of-3 Confirmation" icon="star-circle">
      Transactions require confirmation from multiple validation nodes, protecting operations against individual node failures or compromises.
    </Card>

    <Card title="Availability and Redundancy" icon="siren-on">
      Validators are deployed across multiple cloud providers and infrastructure environments to reduce operational risk and improve availability.
    </Card>
  </Column>

  <Column>
    <Card title="Data Retention" icon="database">
      Historical ledger data is retained for **30 days**, enabling rapid recovery following infrastructure failures or disaster recovery events.
    </Card>

    <Card title="Key Management" icon="key">
      All validator cryptographic keys are managed using a Key Management Service (KMS), reducing operational risk and improving security.
    </Card>
  </Column>
</Columns>

***

## Getting Started

To join the Covalidation network, please should contact Digital Asset

**Become a Node Operator**
[https://www.digitalasset.com/contact-us](https://www.digitalasset.com/contact-us)

***

### Onboarding

The onboarding process consists of the following high-level steps.

```mermaid theme={null}
flowchart LR

A[Choose Third Node Operator]
--> B[Exchange Validator IDs]
--> C[Configure DAR Repository]
--> D[Configure Topology]
--> E[Validate Transactions]
--> F[Manage Ongoing Configuration]
```

### 1. Choose a Third Node Operator

* Select a third-party node operator that will host parties on an additional validator.

### 2. Exchange Configuration

* Validator operators exchange validator IDs so that each covalidator can be configured correctly.

### 3. Configure the DAR Repository

* Create a shared repository from which all participating covalidators synchronize DARs.

### 4. Configure Party Topology

* Whenever a topology transaction is created to multi-host a party, participating covalidation nodes automatically approve the transaction if it matches the agreed-upon topology.

### 5. Validate Transactions

* When a multi-hosted party submits a transaction, confirmation nodes independently validate the transaction against the synchronized DARs before confirming it.

### 6. Manage Configuration Changes

* As applications evolve, new DARs and topology changes can be introduced through the established governance process.

***

## Support

<Card title="Contact Support" icon="help" href="https://digitalasset.atlassian.net/helpcenter/DASupport/">
  If you encounter an issue or have a technical question, submit a support request through the Digital Asset Support portal.
</Card>

### Installation and Operational FAQ

<Columns cols={3}>
  <Column>
    <Card title="Installation" icon="siren-on" href="install">
      Installing Covalidation Service on Kubernetes
    </Card>
  </Column>

  <Column>
    <Card title="FAQ" icon="database" href="troubleshooting">
      Frequently asked operational questions
    </Card>
  </Column>

  <Column>
    <Card title="Monitoring and Alerting" icon="key" href="monitoring">
      Guidance including recommended metrics and alerting thresholds.
    </Card>
  </Column>
</Columns>