Inconsistent VIDA Results from Non-Deterministic Execution?
Non-deterministic execution is not allowed in a VIDA, randomness and other Non-deterministic practices make it impossible to create a consistent execution result across different VIDA Execution Instances.
If a VIDA wants to use randomness, it should derive randomness from on-chain data (e.g., block hashes or timestamps) to ensure reproducibility. Example:
Or it should Use external randomness providers (e.g., Chainlink VRF) only if their outputs are recorded on PWR Chain first1.
Time-based logic can still be implemented because PWR Chain timestamps all transactions and that can be used to create time-based logic.
PreviousHow does PWR Chain Resolve Inconsistent VIDA Execution Results?NextAre there any restrictions on external API calls within VIDAs?
Last updated
Was this helpful?