LogoLogo
  • Abstract
  • Architecture
  • VIDA
  • VIDA Security & Trustlessness
  • EVMs on PWR Chain
  • Conduits
  • Consensus
  • Scalability
  • Security
  • Transaction Fee Model
  • PWR Coin Utility
  • Costs, Inflation & Deflation
  • HOW TO
    • How To Build a VIDA
      • Basics of Blockchain Development
      • Stateless vs. Stateful VIDAs
      • Building a Stateless VIDA
      • Building a Stateful VIDA
  • FAQ
    • How does PWR Chain Resolve Inconsistent VIDA Execution Results?
  • Inconsistent VIDA Results from Non-Deterministic Execution?
  • Are there any restrictions on external API calls within VIDAs?
  • How are VIDA Upgrades Managed without Breaking Replayability?
  • If an VIDA’s Logic Changes, how does PWR Chain Ensure Past Transactions Remain Verifiable?
  • Others
    • Glossary
Powered by GitBook
On this page

Was this helpful?

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.

PreviousAre there any restrictions on external API calls within VIDAs?NextIf an VIDA’s Logic Changes, how does PWR Chain Ensure Past Transactions Remain Verifiable?

Last updated 2 months ago

Was this helpful?