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

From ArdorDocs
Jump to: navigation, search
(Importing a new version from external source)
 
(No difference)

Latest revision as of 00:38, 11 August 2020

Message definition (Lightweight Contracts)
To trigger the execution of a deployed contract, any account can submit a transaction with a special message attachment. The message should be prunable (leave "Message is Never Deleted" unchecked in the wallet) and should be formatted as Json, can be either encrypted or plain text, should identify the contract to execute and optionally provide contract specific invocation parameters.

To trigger the execution of a deployed contract, any account can submit a transaction with a special message attachment. The message should be prunable (leave "Message is Never Deleted" unchecked in the wallet) and should be formatted as Json, can be either encrypted or plain text, should identify the contract to execute and optionally provide contract specific invocation parameters.