An optional attachment
The fee expressed in Planck
Using this field allows to make a transaction dependent on other transactions.
The senders private key, i.e. the crypto.Keys.signPrivateKey If the private key is not given, then the transaction method will return the unsigned byte string. The transaction won't be processed until the unsigned bytes are being signed and broadcasted using TransactionApi.signAndBroadcastTransaction
The senders public key, i.e. the crypto.Keys.publicKey
Setting this option to true, skips the additional security check, i.e. the verification of the
unsigned transaction bytes, which detects tampered node responses. By default, the option is false.
Usually, you won't use this option, but can be useful when a method cannot be verified,
because the verification is not implemented yet.
The argument object for ContractApi.publishContract
The amount in planck needed to execute the contract
The compiled program in hex form (recommend to use [BlockTalk](https://github.com/burst-apps-team/blocktalk smart contracts compiler)
Optional deadline in minutes, default is 1440
The description of your contract (max. 1000 chars)
The name for the contract
is optional here, as it may be calculated dynamically for contracts. For automatic calculation pass an empty string
is optional here, the initial data for the contract (must be according to your data stack in your contract and in BE hex code)
is optional here, the number of pages to store contracts data. If not given, it's set to 1 or calculated from the eventually passed initial
data. You can roughly say that if each data page holds 32 variables, i.e. the number of data pages is (variableCount/32) + 1Consider publishing by reference also, which is way cheaper: ContractApi.publishContractByReference