Translations: Lightweight Contracts/242/en: Difference between revisions
From ArdorDocs
(Importing a new version from external source) |
(No difference)
|
Latest revision as of 00:38, 11 August 2020
However, when relying on external data there is no way to guarantee that transaction data won't change between invocations. Therefore developers of Oracle contracts should always look for duplicate transactions generated by the contract based on the same trigger transaction but with different data (if the data is the same, duplicate transactions will be discarded by the blockchain itself).