Previously we sent simple transactions using the
api.tx endpoints, in this section we will extend that to monitor the actual transactions for inclusion and also extend the monitoring for transaction events.
To send a transaction and then waiting until it has been included in a block, we will use a subscription interface instead of just waiting for the transaction pool addition to yield the extrinsic hash. For the simplest form, we can do the following -
As per all previous subscriptions, the transaction subscription returns in
unsub() and the actual method has a subscription callback. The
result object has 2 parts,
events (to to covered in the next section) and the
status enum is in
Finalized state (checked via
isFinalized), the underlying value contains the block hash of the block where the transaction has been finalized.
Finalized will follow
InBlock, which is the block where the transaction has been included.
InBlock does not mean the block is finalized, but rather applies to the transaction state, where
Finalized means that the transaction cannot be forked off the chain.
Any transaction will emit events, as a bare minimum this will always be either a
system.ExtrinsicFailed event for the specific transaction. These provide the overall execution result for the transaction, i.e. execution has succeeded or failed.
Depending on the transaction sent, some other events may however be emitted, for instance for a
balances.transfer this could include one or more of
ReapedAccount, as defined in the substrate balances event defaults.
To display or act on these events, we can do the following -
Be aware that when a transaction status is
isFinalized, it means it is included, but it may still have failed - for instance if you try to send a larger amount that you have free, the transaction is included in a block, however from a end-user perspective the transaction failed since the transfer did not occur. In these cases a
system.ExtrinsicFailed event will be available in the events array.
The Polkadot/Substrate RPC endpoints exposes weight/payment information that takes an encoded extrinsic and calculates the on-chain weight fees for it. A wrapper for this is available on the tx itself, taking exactly the same parameters as you would pass to a normal
.signAndSend operation, specifically
.paymentInfo(sender, <any options>). To expand on our previous example -
In many cases transactions can carry quite complex information, be it for passing objects or proposing changes. In the next section we will take a dive into complex transactions, including those wrapped for sudo.