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?

  1. FAQ

How does PWR Chain Resolve Inconsistent VIDA Execution Results?

Anyone on PWR Chain can run a VIDA to independently verify its results (if the VIDA is public). However, inconsistent results may arise if VIDA instances are running different versions, encountering non-deterministic behavior, or facing unexpected issues.

VIDAs are responsible for implementing their own execution verification mechanisms. This can be achieved through cross-instance state verification or validation by Conduit Nodes, which confirm the results and publish their state root hash on the PWR Chain.

Best Practices to Prevent Inconsistencies:

  • VIDAs must adhere to deterministic execution rules (e.g., avoiding floating-point operations or local system time).

  • External data sources (e.g., APIs) must be validated and timestamped by Conduit Nodes before being used in VIDA logic.

PreviousBuilding a Stateful VIDANextInconsistent VIDA Results from Non-Deterministic Execution?

Last updated 2 months ago

Was this helpful?