Transaction Construction
This page will discuss the transaction format in Acala and how to create, sign, and broadcast transactions.
This page will discuss the transaction format in Polkadot and how to create, sign, and broadcast transactions. Like the other pages in this guide, this page demonstrates some of the available tools. Always refer to each tool's documentation when integrating.
Transaction Format
Polkadot has some basic transaction information that is common to all transactions.
Address: The SS58-encoded address of the sending account.
Block Hash: The hash of the checkpoint block.
Block Number: The number of the checkpoint block.
Genesis Hash: The genesis hash of the chain.
Metadata: The SCALE-encoded metadata for the runtime when submitted.
Nonce: The nonce for this transaction.*
Spec Version: The current spec version for the runtime.
Transaction Version: The current version for transaction format.
Tip: Optional, the tip to increase transaction priority.
Era Period: Optional, the number of blocks after the checkpoint for which a transaction is valid. If zero, the transaction is immortal.
*The nonce queried from the System module does not account for pending transactions. You must track and increment the nonce manually if you want to submit multiple valid transactions at the same time.
Each transaction will have its own (or no) parameters to add. For example, the transferKeepAlive
function from the Balances pallet will take:
dest
: Destination address#[compact] value
: Number of tokens (compact encoding)
Once you have all the necessary information, you will need to:
Construct an unsigned transaction.
Create a signing payload.
Sign the payload.
Serialize the signed payload into a transaction.
Submit the serialized transaction.
Parity provides the following tools to help perform these steps.
Acala JS
[TODO]
Tx Wrapper
If you do not want to use the CLI for signing operations, Parity provides an SDK called TxWrapper to generate and sign transactions offline. See the examples for a guide.
Import a private key
Derive an address from a public key
Construct a transaction offline
Construct a signing payload
Serialize a signed transaction
Decode payload types
You may want to decode payloads to verify their contents prior to submission.
Check a transaction's hash
Submitting a Signed Payload
There are several ways to submit a signed payload:
Signer CLI (
yarn run:signer submit --tx <signed-transaction> --ws <endpoint>
)RPC with
author_submitExtrinsic
orauthor_submitAndWatchExtrinsic
, the latter of which will subscribe you to events to be notified as a transaction gets validated and included in the chain.
Notes
Some addresses to use in the examples. See Subkey documentation.
Last updated