https://betaardordocs.jelurida.com/index.php?action=history&feed=atom&title=Translations%3ALightweight_Contracts%2F241%2FenTranslations:Lightweight Contracts/241/en - Revision history2026-05-14T18:22:07ZRevision history for this page on the wikiMediaWiki 1.39.10https://betaardordocs.jelurida.com/index.php?title=Translations:Lightweight_Contracts/241/en&diff=12609&oldid=prevFuzzyBot: Importing a new version from external source2020-08-11T00:38:24Z<p>Importing a new version from external source</p>
<p><b>New page</b></p><div>However, there are few steps contract developers need to take to increase the reliability of Oracle contracts, as a developer, you should consider that contracts should be designed to be idempotent (i.e. can run multiple times on the same data and produce the same result). For example, a contract can run once when a trigger transaction is received, then again if the node switches to a better fork and the trigger transaction is included in a different fork, and again in case the contract runner is re-downloading the blockchain. Ideally, in all these cases the contract should reproduce the exact same output transactions. The blockchain itself protects against including duplicate transactions in the blockchain.</div>FuzzyBot