# Cloud Sign 1.13.0

We are pleased to announce Cloud Sign version 1.13.0.

## Key features

### Co-signer liveness checks

Liveness checks let you verify the connection between Wallet-as-a-Service and your co-signer, so you can catch a disconnected co-signer before it holds up signing. Liveness checks are available for cloud-hosted co-signers running CloudSign 1.13.0 and above.

CloudSign nodes on this version report a heartbeat to Wallet-as-a-Service every 30 seconds. The console uses these heartbeats to show a connection status for each CloudSign device, in both the device list and quorum pairing views:

| Status | Meaning |
|  --- | --- |
| **Online** | The device reported a heartbeat within the last 2 minutes. |
| **Offline** | The device hasn't reported a heartbeat for more than 2 minutes. Check that the container is running and has outbound network access. |
| **Unknown** | The device has never reported a heartbeat. Devices running CloudSign versions older than 1.13.0 don't send heartbeats and can't show an Online or Offline status. |


The device details page also shows when the device was last seen, the CloudSign version it's running (with a **Latest** badge when it matches the newest release), and self-reported build metadata such as build date, MPC engine, and platform.

The heartbeat interval is controlled by the `HEARTBEAT_INTERVAL_MS` environment variable (default `30000`). Don't disable it — without heartbeats the console can't report the device's connection status. See [Set up and run CloudSign](/products/wallet/user-interface/devices/set-up-and-run-cloudsign) for the full configuration reference.

### Reliability improvements

This release also improves signing-session queue handling for high-throughput workloads and refreshes message-broker credentials automatically, so long-running nodes stay connected across credential rotations.

## Upgrading

No migration steps are required. Upgrade nodes one at a time so the quorum keeps enough online members to sign.

Reported binary version
Cloud Sign 1.13.0 is built from the same image as the 2.0.0 beta line. The binary's own version output (for example, in container logs) reports `2.0.0-beta19`, while the console displays the stable version 1.13.0. This is expected.