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

# Upgrade a node

> Move a node onto a newer (or older) client version

<Note>
  A one-click in-UI node upgrade is planned. Until then, delete-and-redeploy is the supported path for moving a node to a different client version.
</Note>

## See a node's current version

Open the node from **Nodes**, then the **Configuration** tab. The **Clients** section lists one card per role (for a single-client chain like Bitcoin that's just `node`; for Ethereum it's the execution and consensus clients), showing the client name and the running version, e.g. `v1.17.3`.

## Move to a different version today

There is no in-place version swap yet, so changing a client version means redeploying:

1. **Delete the node.** On the node detail page, click the **Delete** button (top right), then confirm in the dialog. This tears down the running node; deletion cannot be undone, and the data directory is not preserved.
2. **Redeploy with the new version.** Go to **Nodes** → **Deploy node** and step through the wizard, selecting the version you want. In the **Target** step, each role's version dropdown lists exactly the versions the chosen executor declares for that chain and client — filtered by any per-network constraint, so a network that requires a minimum client version won't offer older ones.

Because the data directory is not kept, the redeployed node syncs again — from genesis or, where the chain supports it, from a checkpoint (Ethereum consensus clients accept a `checkpoint-sync-url`). Plan for the resync time, especially on mainnet.

To roll back a misbehaving release, redeploy the same way onto the older version.

## If the version you want isn't offered

A node can only run what its executor supports — the wizard offers exactly the chains, clients, and versions that executor has declared. If the target version isn't in the dropdown, [upgrade the executor first](/docs/executors/upgrade-executor); newer executor releases ship newer client coverage. You can review what an executor currently supports on the [Executors](/docs/executors/overview) page.

## Coming soon: in-UI node upgrade

A one-click in-UI node upgrade is planned, letting you move a node onto a new version directly from its detail page. Until it ships, delete-and-redeploy is the supported path.

## Related

* [Upgrade an executor](/docs/executors/upgrade-executor) — the in-UI version flow already available for executors.
* [Edit node configuration](/docs/nodes/edit-configuration) — change client config and overrides without a version swap.
* [Deploy a node](/docs/nodes/deploy-a-node) — the wizard you'll use to redeploy.
* [Executors](/docs/executors/overview) — the chains, clients, and versions an executor offers.