> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/participant-and-keys.md).
# Participant & Keys
## Participant
The deepest health view in the console. When something is wrong at the Canton level rather than the Kubernetes level, this is the tab that tells you. The heading carries the participant **Version** beside it.
### While initialising
If the node has not finished initialising, the tab shows only:
* **Initialized** — `false`
* **Active** — `Yes` / `No`
* **Waiting for** — what the node is blocked on
{% hint style="info" %}
**Waiting for** is the single most useful field during onboarding. A participant that sits here for a long time is usually waiting on the synchronizer or on network onboarding to complete, not failing.
{% endhint %}
### Once initialised
| Card | Meaning |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active** | Whether this is the active instance |
| **Uptime** | Live-ticking, formatted `1d 2h 3m 4s` |
| **Connected Synchronizers** | One row per synchronizer, with its ID (copyable) and health. This is where a lost synchronizer connection shows up first. |
| **Topology Queues** | The depth of the **Manager**, **Dispatcher**, and **Clients** queues. Sustained non-zero values mean topology changes are backing up. |
| **Identity** | The participant's **UID**, its **Endpoint**, and the **Protocol Versions** it supports. |
| **Ports** | The ports the node exposes. |
| **Components** | The participant's internal health components, each with a status and description. Component names are truncated after the `::` separator, with the full name in the tooltip. |
### Health values
The status values are Canton's own, colour-coded by the console:
| Value | Reading |
| ------------------------------ | -------- |
| `ok`, `healthy` | Healthy |
| `degraded` | Degraded |
| `failed`, `fatal`, `unhealthy` | Failed |
| anything else | Unknown |
### States
| Situation | What you see |
| -------------- | ------------------------------------------------------------------------ |
| Loading | *Loading participant status…* |
| No status | **No participant data** — *The participant has not reported status yet.* |
| Request failed | **Failed to load participant status**, with the error |
{% hint style="info" %}
This tab is entirely read-only. There is no restart, reconnect-synchronizer, or pruning action. For participant-level administration, use the [Canton console](/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/canton-console.md).
{% endhint %}
***
## Keys
The public keys held in the participant's key vault.
| Column | Contents |
| ------------ | ------------------------------------- |
| **Name** | The key's name, or `—` |
| **Purpose** | `signing` or `encryption` |
| **Key Spec** | The cryptographic algorithm and curve |
| **Usage** | One badge per declared usage |
| **Format** | The key's encoding |
### What this tab tells you
It is the quickest way to confirm that KMS integration is working. With a KMS configured, the participant's operational keys are created and held in the key vault rather than in the participant database — and they appear here either way, so use the **Key Spec** and your KMS provider's own console to confirm where the private material actually lives.
### States
| Situation | What you see |
| -------------- | -------------------------------------------------------------- |
| No keys | **No keys** — *The participant vault returned no public keys.* |
| Request failed | **Failed to load keys**, with the error |
{% hint style="info" %}
Read-only. Key generation, rotation, import, and export are not exposed in the console — they are participant and KMS operations. See [Key Management Service (KMS)](/catalyx-blockchain-manager/canton-network/version-2.0/validator-management/kms-integration.md).
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/participant-and-keys.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.