Expand description

High level wrappers for making transactions with minimal user input. These wrappers handle encoding, setting energy costs when those are fixed for transaction. See also the send module above which combines construction with signing.

Structs§

  • A transaction that is prepared to be signed. The serde instance serializes the structured payload and skips serializing the encoded one.

Enums§

  • An upper bound on the amount of energy to spend on a transaction. Transaction costs have two components, one is based on the size of the transaction and the number of signatures, and then there is a transaction specific one. This construction helps handle the fixed costs and allows the user to focus only on the transaction specific ones. The most important case for this are smart contract initialisations and updates.

Constants§

  • Size of a transaction header. This is currently always 60 bytes. Future chain updates might revise this, but this is a big change so this is expected to change seldomly.

Functions§

  • Configure the account as a baker. Only valid for protocol version 4 and up.
  • Configure the account as a delegator. Only valid for protocol version 4 and up.
  • Deploy the given Wasm module. The module is given as a binary source, and no processing is done to the module.
  • Make an encrypted transfer. The payload can be constructed using make_transfer_data.
  • Make an encrypted transfer with a memo. The payload can be constructed using make_transfer_data.
  • Initialize a smart contract, giving it the given amount of energy for execution. The unique parameters are
  • A convenience wrapper around sign_transaction that construct the transaction and signs it. Compared to transaction-type-specific wrappers above this allows selecting the amount of energy
  • Construct a transction to register the given piece of data.
  • Construct a transfer transaction.
  • Transfer the given amount from public to encrypted balance of the given account.
  • Transfer the given amount from encrypted to public balance of the given account. The payload may be constructed using make_sec_to_pub_transfer_data
  • Construct a transfer transaction with a memo.
  • Construct a transfer with schedule transaction, sending to the given account.
  • Construct a transfer with schedule and memo transaction, sending to the given account.
  • Update a smart contract intance, giving it the given amount of energy for execution. The unique parameters are
  • Construct a transaction to update keys of a single credential on an account. The transaction specific arguments are
  • Construct a transaction to update credentials on an account. The transaction specific arguments are