> For the complete documentation index, see [llms.txt](https://service.block-pro.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://service.block-pro.net/mainnet/celestia/validator-node/upgrade.md).

# Upgrade

Update celestia-app and its matching Fibre binary with the existing validator home.

**Mainnet Beta · `celestia` · v11.0.0 · Linux x86-64**

Install the v11 multiplexer ahead of the coordinated network activation. It embeds app v10.6.0 for pre-activation blocks. Active validators also upgrade Fibre and [signal for v11](#signal-for-app-v11). [Official release](https://github.com/celestiaorg/celestia-app/releases/tag/v11.0.0)

| Component | Systemd unit            | BlockPro executable          | Home                      |
| --------- | ----------------------- | ---------------------------- | ------------------------- |
| Consensus | `celestia-appd.service` | `/root/go/bin/celestia-appd` | `/root/.celestia-app`     |
| Fibre     | `fibre.service`         | `/usr/local/bin/fibre`       | `/var/lib/celestia-fibre` |

Run as root on the existing BlockPro hosts. The prebuilt multiplexer requires glibc 2.38 or newer. Run each block in order and stop on errors. For a consensus-only RPC node, follow the **consensus** steps and the query checks. The Mainnet validator and public consensus deployments both use the consensus executable above. On other installations, use the path and home from `ExecStart`.

## Check the service paths

On the consensus host, check the current binary, home and service flags.

```bash
systemctl show celestia-appd.service -p ExecStart --no-pager -l
```

On the Fibre host, check the corresponding service.

```bash
systemctl show fibre.service -p ExecStart --no-pager -l
```

### Custom ABCI address

For a custom app socket, check `--proxy_app` in the service and `proxy_app` in the consensus config. A command-line flag takes precedence.

```bash
grep -nE '^[[:space:]]*proxy_app[[:space:]]*=' /root/.celestia-app/config/config.toml
```

The multiplexer requires the ABCI client address (`--proxy_app` or `proxy_app`) and server address (`--address`) to match. If your unit uses a custom address, carry it forward on both sides. If you need to edit a unit or drop-in, keep its full `ExecStart` and existing flags, set both ABCI addresses to the same configured local endpoint and run `sudo systemctl daemon-reload` before starting. [Celestia ABCI configuration](https://github.com/celestiaorg/celestia-app/blob/main/docs/release-notes/release-notes.md#proxy_app-and-address)

## Prepare the release

Use the official Linux x86-64 binaries. The published checksums are also available in [checksums.txt](https://github.com/celestiaorg/celestia-app/releases/download/v11.0.0/checksums.txt).

### Consensus

Create a staging directory and open it.

```bash
mkdir -p "$HOME/celestia-v11.0.0/app" &&
cd "$HOME/celestia-v11.0.0/app"
```

Download the Mainnet archive.

```bash
curl -fL --retry 3 -o celestia-app_Linux_x86_64.tar.gz https://github.com/celestiaorg/celestia-app/releases/download/v11.0.0/celestia-app_Linux_x86_64.tar.gz
```

Verify SHA-256 before extracting. Stop on a mismatch.

```bash
printf '%s  %s\n' '838fe33955eab14ac6ff666fced29c851e5f5d8083528cf7f71b7e0a06dda32f' 'celestia-app_Linux_x86_64.tar.gz' | sha256sum --check - &&
tar --no-same-owner -xzf celestia-app_Linux_x86_64.tar.gz
```

Confirm the staged binary runs and reports `11.0.0`.

```bash
./celestia-appd version
```

### Fibre

Create a staging directory and open it.

```bash
mkdir -p "$HOME/celestia-v11.0.0/fibre" &&
cd "$HOME/celestia-v11.0.0/fibre"
```

Download the Mainnet archive.

```bash
curl -fL --retry 3 -o fibre_Linux_x86_64.tar.gz https://github.com/celestiaorg/celestia-app/releases/download/v11.0.0/fibre_Linux_x86_64.tar.gz
```

Verify SHA-256 before extracting. Stop on a mismatch.

```bash
printf '%s  %s\n' '4b00bd767fdc66cc73f2121d29163cdd48e0aba1e33efa9a19a907874ff898d7' 'fibre_Linux_x86_64.tar.gz' | sha256sum --check - &&
tar --no-same-owner -xzf fibre_Linux_x86_64.tar.gz
```

Confirm the staged binary runs and reports `11.0.0`.

```bash
./fibre version
```

## Install and restart

Stop Fibre first on the validator's Fibre host.

```bash
sudo systemctl stop fibre.service
```

On the consensus host, stop consensus and install the verified binary at its service path.

```bash
sudo systemctl stop celestia-appd.service &&
sudo install -m 0755 "$HOME/celestia-v11.0.0/app/celestia-appd" /root/go/bin/celestia-appd
```

On the Fibre host, install the matching binary at its service path.

```bash
sudo install -m 0755 "$HOME/celestia-v11.0.0/fibre/fibre" /usr/local/bin/fibre
```

Start consensus with the existing database, home and configuration. Follow the logs until blocks advance, then press Ctrl+C to exit the log view.

```bash
sudo systemctl start celestia-appd.service &&
sudo journalctl -u celestia-appd.service -n 30 -f -o cat
```

After consensus is healthy, start Fibre with its current home, signing connection and storage.

```bash
sudo systemctl start fibre.service &&
sudo journalctl -u fibre.service -n 30 --no-pager -o cat
```

## Verify the running processes

On the consensus host, check the executable systemd is running. Expect `11.0.0`.

```bash
systemctl is-active --quiet celestia-appd.service &&
sudo "/proc/$(systemctl show celestia-appd.service -p MainPID --value)/exe" version
```

On the Fibre host, expect the same binary version and confirm Fibre readiness. [Readiness checks](https://service.block-pro.net/mainnet/celestia/validator-node/fibre.md#health-and-readiness)

```bash
systemctl is-active --quiet fibre.service &&
sudo "/proc/$(systemctl show fibre.service -p MainPID --value)/exe" version
```

## Check tally and activation

Use your synchronized Mainnet consensus RPC. This example uses the standard local port. Substitute your configured port if needed.

```bash
CONSENSUS_RPC="http://127.0.0.1:26657"
```

Check the chain and current height. Expect `celestia` and `catching_up: false`.

```bash
curl -fsS "$CONSENSUS_RPC/status" | jq '.result | {chain: .node_info.network, height: .sync_info.latest_block_height, catching_up: .sync_info.catching_up}'
```

Read the voting-power tally for v11.

```bash
/root/go/bin/celestia-appd query signal tally 11 --node "$CONSENSUS_RPC"
```

Read the scheduled block height.

```bash
/root/go/bin/celestia-appd query signal upgrade --node "$CONSENSUS_RPC"
```

Activation follows a successful `try-upgrade` after at least **5/6 of voting power** signals. The chain schedules the switch **232,616 blocks** after that transaction, about **7.6 days** at the block time used in the release notes. Read the scheduled height from `query signal upgrade`. [Mainnet release notes](https://github.com/celestiaorg/celestia-app/releases/tag/v11.0.0)

Check the active chain version separately from the binary version. The multiplexer runs app v10 until activation and app v11 after the first v11 block is committed.

```bash
curl -fsS "$CONSENSUS_RPC/abci_info" | jq -r '.result.response.app_version'
```

## Signal for app v11

Active Mainnet validators should signal after confirming the new consensus binary and node health. Use the RPC URL from [Check tally and activation](#check-tally-and-activation) in the same shell. Submit a signal while app v10 is active and activation is still unscheduled.

Use the existing operator wallet and keyring configuration on the signing host.

```bash
/root/go/bin/celestia-appd keys list --home /root/.celestia-app
```

Enter the wallet name shown in the list. If you select a keyring backend explicitly, use that same backend for listing keys and signaling.

```bash
read -r -p "Mainnet validator wallet name: " VALIDATOR_WALLET
```

Review and confirm the signal. The announced fee is `210000utia`.

```bash
/root/go/bin/celestia-appd tx signal signal 11 --from "$VALIDATOR_WALLET" --home /root/.celestia-app --chain-id celestia --node "$CONSENSUS_RPC" --fees 210000utia
```

Check the transaction hash after inclusion. A successful on-chain result has block height greater than zero and execution code `0`.

```bash
/root/go/bin/celestia-appd query tx YOUR_SIGNAL_TX_HASH --node "$CONSENSUS_RPC" --output json
```

Refresh [the tally and the pending upgrade](#check-tally-and-activation) after your signal commits.

<details>

<summary>Schedule activation if the threshold is met</summary>

Once the tally meets the threshold, a funded account can submit `try-upgrade` while app v10 is active and activation remains unscheduled. Enter an accepted gas price in `utia` for your node. The release recommends a gas limit of `1000000`.

```bash
read -r -p "Gas price including utia: " GAS_PRICE_UTIA
```

Use the RPC URL and funded wallet selected above. Review the transaction before confirming.

```bash
/root/go/bin/celestia-appd tx signal try-upgrade --from "$VALIDATOR_WALLET" --home /root/.celestia-app --chain-id celestia --node "$CONSENSUS_RPC" --gas 1000000 --gas-prices "$GAS_PRICE_UTIA"
```

After inclusion, query the scheduled height again.

```bash
/root/go/bin/celestia-appd query signal upgrade --node "$CONSENSUS_RPC"
```

</details>

## Optional download cleanup

After the services recover on each host, remove that host's release staging directory. The executable paths for the active services are listed above.

```bash
cd "$HOME" &&
rm -r -- "$HOME/celestia-v11.0.0"
```

[Versions](https://service.block-pro.net/mainnet/celestia/versions.md) · [Network upgrades](https://docs.celestia.org/operate/maintenance/network-upgrades/)
