> For the complete documentation index, see [llms.txt](https://docs.vechain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vechain.org/developer-resources/index-with-graph-node/index-with-openzeppelin/update-subgraph.md).

# Update Subgraph

To update a subgraph without causing service interruptions, deploy it to a different namespace.

Subgraphs are identified by their IPFS CID. Re-compiling and uploading the same subgraph to IPFS will always result in the same CID.

The graph node points subgraph namespaces to the IPFS CID, allowing multiple namespaces to use the same subgraph index.

This method allows for seamless updates. Deploy new subgraphs to a staging namespace first. Once they are fully synchronized and tested, deploy them to the production namespace. This way, the production namespace will immediately point to the already synchronized subgraph.


---

# 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.vechain.org/developer-resources/index-with-graph-node/index-with-openzeppelin/update-subgraph.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.