Something went wrong on our end
Select Git revision
exceptions.rst
runtime-calls.md 39.30 KiB
Runtime calls
Calls are categorized according to the dispatch origin they require:
- User calls: the dispatch origin for this kind of call must be signed by the transactor. This is the only call category that can be submitted with an extrinsic.
- Root calls: This kind of call requires a special origin that can only be invoked through on-chain governance mechanisms.
- Inherent calls: This kind of call is invoked by the author of the block itself (usually automatically by the node).
- Disabled calls: These calls can not be called directly, they are reserved for internal use by other runtime calls.
We only document user calls below.
There are 65 user calls from 17 pallets.
Account - 1
unlink_identity - 0
unlink_identity()
Taking 0.0106 % of a block.
Unlink the identity associated with the account.
Balances - 6
transfer_allow_death - 0
transfer_allow_death(dest, value)
Taking 0.0186 % of a block.
dest: AccountIdLookupOf<T>
value: T::Balance
Transfer some liquid free balance to another account.
transfer_allow_death
will set the FreeBalance
of the sender and receiver.
If the sender's account is below the existential deposit as a result
of the transfer, the account will be reaped.
The dispatch origin for this call must be Signed
by the transactor.
transfer_keep_alive - 3
transfer_keep_alive(dest, value)
Taking 0.0119 % of a block.
dest: AccountIdLookupOf<T>
value: T::Balance
Same as the transfer_allow_death
call, but with a check that the transfer will not
kill the origin account.
99% of the time you want transfer_allow_death
instead.