> For the complete documentation index, see [llms.txt](https://bitnet-whitepaper.gitbook.io/developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bitnet-whitepaper.gitbook.io/developer-docs/upgrades-overview/hard-fork-upgrades.md).

# Hard Fork Upgrades

### Coordinating Hard Fork Upgrades on BitNet

While traditional governance proposals allow BitNet to schedule upgrades in a decentralized way, they require a full voting period. For **critical updates**, such as emergency patches or security fixes, BitNet supports **Hard Fork Upgrades** to ensure faster execution.

***

#### What is a Hard Fork Upgrade?

A **Hard Fork** in BitNet allows validators to pre-agree on a future upgrade height without waiting for a governance vote. It is triggered by a specially crafted patch release that automatically initiates the upgrade logic when the blockchain reaches a defined block height.

***

#### Step-by-Step Hard Fork Process

1. **Patch Creation**\
   A private branch is used to fix the vulnerability or apply breaking changes.\
   Example: A patch release like `v8.0.1` includes upgrade logic targeting `v9.0.0`.
2. **Patch Deployment**\
   Validators install the patch release (`v8.0.1`), which contains the hard-coded fork logic set for a specific block height.
3. **Validator Coordination**\
   At least **two-thirds (2/3)** of the validator voting power must upgrade before the fork height to avoid network halts.
4. **Release Distribution**\
   The full major release (`v9.0.0`) is made publicly available **at least one hour** before the scheduled fork to allow:
   * Binary creation (\~30 minutes)
   * Validator testing and Cosmovisor updates

***

#### Why Hard Forks Matter

* **Fast Response**: Ideal for critical security fixes
* **No Governance Delay**: Bypasses full voting periods
* **Automated Execution**: Logic executes at `BeginBlock` of upgrade height
* **Validator Participation Required**: If <2/3 voting power upgrades, the fork will fail


---

# 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://bitnet-whitepaper.gitbook.io/developer-docs/upgrades-overview/hard-fork-upgrades.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.