# How are VIDA Upgrades Managed without Breaking Replayability? A structured approach to upgrades involves assigning a version identifier to the VIDA. If the VIDA is centralized, then the development team can announce upgrade schedules, version numbers, and application hashes. If it's decentralized, Conduit Nodes can vote on upgrade schedules, version numbers, and application hashes. Once an upgrade is approved, both Conduit Nodes and VIDA Execution Instances must update their software accordingly. If a node fails to update before the new version becomes active at a specified block or timestamp, it will be unable to continue operating and will effectively freeze. --- # Agent Instructions: 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: ``` GET https://whitepaperv2.pwrlabs.io/how-are-vida-upgrades-managed-without-breaking-replayability.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.