Translations: Lightweight Contracts/106/en: Difference between revisions

Latest revision as of 00:38, 11 August 2020

Message definition (Lightweight Contracts)

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.
Internally the createTransaction method implements local signing, fee calculation, and other complex processing that you as contract developer don't have to deal with.

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 context.createTransaction() method to submit the transaction to the blockchain. Internally the createTransaction method implements local signing, fee calculation, and other complex processing that you as contract developer don't have to deal with.