https://betaardordocs.jelurida.com/index.php?action=history&feed=atom&title=Translations%3ALightweight_Contracts%2F106%2FenTranslations:Lightweight Contracts/106/en - Revision history2026-05-14T18:23:07ZRevision history for this page on the wikiMediaWiki 1.39.10https://betaardordocs.jelurida.com/index.php?title=Translations:Lightweight_Contracts/106/en&diff=12583&oldid=prevFuzzyBot: Importing a new version from external source2020-08-11T00:38:22Z<p>Importing a new version from external source</p>
<p><b>New page</b></p><div>In most cases, contracts should not save any internal state between contract invocations. To make changes to the blockchain state, contracts should submit transactions. To submit a transaction, invoke the API caller for the specific transaction type, then use the <code>context.createTransaction()</code> method to submit the transaction to the blockchain.<br />
Internally the createTransaction method implements local signing, fee calculation, and other complex processing that you as contract developer don't have to deal with.</div>FuzzyBot