> For the complete documentation index, see [llms.txt](https://docs.hypersign.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hypersign.id/hypersign-identity-network/governance/proposals/blockchain-node-upgrade.md).

# Blockchain Node Upgrade

## Proposal Structure

|        Field       |                 Description                |
| :----------------: | :----------------------------------------: |
|      **name**      |             Name of the Upgrade            |
|      **title**     |            Title of the proposal           |
|   **description**  |         Description of the proposal        |
| **upgrade-height** | Height at which node upgrade should happen |
|     **deposit**    |    Deposit for the proposal (in `uhid`)    |

## Submitting Node Upgrade Proposal

* Run the following to submit a blockchain node upgrade proposal:

```
hid-noded tx gov submit-legacy-proposal software-upgrade <Proposal Name> \
--title "<Proposal Title>" \
--description "<Proposal Description>" \
--upgrade-height "<Blockchain Height at which the upgrade should occur>" \
--deposit "<Deposit for the proposal>" \
--chain-id <Chain ID> \
--from <wallet-address> \
--yes
```

## Steps for Node Upgrade

If the Software Upgrade proposal is `Passed`, then following steps are needed to be performed in order to upgrade your node.

* Download and Install the **latest** binary.
* Create the following directory structure

```
mkdir -p <hid-node Config Directory>/cosmovisor/upgrades/<Proposal Name>/bin
```

> Note: Make sure that `<Proposal Name>` matches exactly with Upgrade Proposal's name. Please note that `Proposal Name` is different from `Proposal Title`.

* Copy the latest binary to the newly created directory

```
cp <Update Binary Location> <Binary Config Directory>/cosmovisor/upgrades/<Proposal Name>/bin
```

* At the the proposed height, the upgrade would take place automatically.


---

# 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.hypersign.id/hypersign-identity-network/governance/proposals/blockchain-node-upgrade.md?ask=<question>&goal=<endgoal>
```

`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.