Balances
Calls
forceTransfer
Exactly as transfer
, except the origin must be root and the source account may be specified.
Namespace
Type
forceUnreserve
Unreserve some balance from a user by force.
Can only be called by ROOT.
Namespace
Type
setBalance
Set the balances of a given account.
This will alter FreeBalance
and ReservedBalance
in storage. it will also alter the total issuance of the system (TotalIssuance
) appropriately. If the new free or reserved balance is below the existential deposit, it will reset the account nonce (frame_system::AccountNonce
).
The dispatch origin for this call is root
.
Namespace
Type
transfer
Transfer some liquid-free balance to another account.
transfer
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.
Namespace
Type
transferAll
Transfer the entire transferable balance from the caller account.
NOTE: This function only attempts to transfer transferable balances. This means that any locked, reserved, or existential deposits (when keep_alive
is true
), will not be transferred by this function. To ensure that this function results in a killed account, you might need to prepare the account by removing any reference counters, storage deposits, etc.
The dispatch origin of this call must be Signed.
dest
: The recipient of the transfer.keep_alive
: A boolean to determine if thetransfer_all
operation should send all of the funds the account has, causing the sender account to be killed (false), or transfer everything except at least the existential deposit, which will guarantee to keep the sender account alive (true). #
Namespace
Type
transferKeepAlive
Same as the transfer
call, but with a check that the transfer will not kill the origin account.
99% of the time you want transfer
instead.
Namespace
Type
Storage
account
The Balances pallet example of storing the balance of an account.
Example
nocompile impl pallet_balances::Config for Runtime { type AccountStore = StorageMapShim<Self::Account<Runtime>, frame_system::Provider<Runtime>, AccountId, Self::AccountData<Balance>> }
You can also store the balance of an account in the System
pallet.
Example
nocompile impl pallet_balances::Config for Runtime { type AccountStore = System }
But this comes with tradeoffs, storing account balances in the system pallet stores frame_system
data alongside the account data contrary to storing account balances in the Balances
pallet, which uses a StorageMap
to store balances data only. NOTE: This is only used in the case that this pallet is used to store balances.
Namespace
Type
locks
Any liquidity locks on some account balances. NOTE: Should only be accessed when setting, changing and freeing a lock.
Namespace
Type
reserves
Named reserves on some account balances.
Namespace
Type
storageVersion
Storage version of the pallet.
This is set to v2.0.0 for new networks.
Namespace
Type
totalIssuance
The total units issued in the system.
Namespace
Type
Events
BalanceSet
A balance was set by root.
Namespace
Type
Deposit
Some amount was deposited (e.g. for transaction fees).
Namespace
Type
DustLost
An account was removed whose balance was non-zero but below ExistentialDeposit, resulting in an outright loss.
Namespace
Type
Endowed
An account was created with some free balance.
Namespace
Type
Reserved
Some balance was reserved (moved from free to reserved).
Namespace
Type
ReserveRepatriated
Some balance was moved from the reserve of the first account to the second account. Final argument indicates the destination balance type.
Namespace
Type
Slashed
Some amount was removed from the account (e.g. for misbehavior).
Namespace
Type
Transfer
Transfer succeeded.
Namespace
Type
Unreserved
Some balance was unreserved (moved from reserved to free).
Namespace
Type
Withdraw
Some amount was withdrawn from the account (e.g. for transaction fees).
Namespace
Type
Errors
DeadAccount
Beneficiary account must pre-exist
Namespace
ExistentialDeposit
Value too low to create account due to existential deposit
Namespace
ExistingVestingSchedule
A vesting schedule already exists for this account
Namespace
InsufficientBalance
Balance too low to send value
Namespace
KeepAlive
Transfer/payment would kill account
Namespace
LiquidityRestrictions
Account liquidity restrictions prevent withdrawal
Namespace
TooManyReserves
Number of named reserves exceed MaxReserves
Namespace
VestingBalance
Vesting balance too high to send value
Namespace
Constants
existentialDeposit
The minimum amount required to keep an account open.
Namespace
Type
maxLocks
The maximum number of locks that should exist on an account. Not strictly enforced, but used for weight estimation.
Namespace
Type
maxReserves
The maximum number of named reserves that can exist on an account.
Namespace
Type
Last updated