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?

Are there any restrictions on external API calls within VIDAs?

There are no restrictions on external API calls. However, if an API returns data that can change over time or introduce non-determinism, it should be handled by Conduit Nodes instead of being directly queried by the VIDA. The Conduit Nodes will fetch the data, reach consensus through a voting process, and publish the agreed-upon result on PWR Chain with a timestamp. This ensures that future VIDA Execution Instances can reference the same verified data at a specific point in time, preventing state inconsistencies and maintaining execution integrity.

PreviousInconsistent VIDA Results from Non-Deterministic Execution?NextHow are VIDA Upgrades Managed without Breaking Replayability?

Last updated 1 month ago

Was this helpful?