> For the complete documentation index, see [llms.txt](https://docs.seda.xyz/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seda.xyz/home/archvie/seda-litepaper/sedas-key-features/forkless-upgrades.md).

# Forkless Upgrades

In many current decentralized systems, system upgrades are challenging and require active participation from all involved parties. SEDA allows for coordinated, forkless consensus upgrades to keep the network updated. Upgrades are proposed and decided upon by the community of SEDA token holders, and are coordinated via a governance upgrade vote.

SEDA achieves this is by having its nodes composed of modular building blocks. In our implementation, most of the SEDA node logic runs on WASM binaries, which are fetched from a source pointed to by the SEDA Governance Module. Nodes watch the SEDA Governance Module for any changes to the binary so that it can upgrade it “in-flight.” This mechanism allows SEDA Token holders to have true verifiable control over the future of the SEDA Network

\ <br>


---

# 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.seda.xyz/home/archvie/seda-litepaper/sedas-key-features/forkless-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.