Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Burns an asset from an account. Caller must be the asset owner Attempting to burn ROOT token will throw an error
Namespace
Type
Creates a new asset with unique ID according to the network asset id scheme.
Namespace
Type
Mints an asset to an account if the caller is the asset owner Attempting to mint ROOT token will throw an error
Namespace
Type
Sudo call to set the asset deposit for creating assets Note, this does not change the deposit when calling create within the assets pallet However that call is filtered
Namespace
Type
Transfers either ROOT or an asset
Namespace
Type
The minimum deposit for creating an asset
Namespace
Type
The holdings of a specific account for a specific asset.
Namespace
Type
The total units issued in the system.
Namespace
Type
The asset deposit was set
Namespace
Type
New asset has been created
Namespace
Type
Assets were deposited into this account by the system e.g. refunding gas
Namespace
Type
Assets were withdrawn from this account by the system e.g. paying tx fees
Namespace
Type
Some assets have been placed on hold by a pallet
Namespace
Type
Some held assets have been released by a pallet
Namespace
Type
Some held assets were spend by a pallet
Namespace
Type
Multi-part transfer of assets from who
Namespace
Type
Hold balance is less then the required amount
Namespace
Failed to create a new asset
Namespace
Decimals cannot be higher than 18
Namespace
Maximum holds placed on this asset/account pair
Namespace
The account to alter does not exist
Namespace
No more Ids are available, they've been exhausted
Namespace
The signer does not have permission to perform this action
Namespace
Operation would overflow
Namespace
The maximum * of holds per asset & account
Namespace
Type
The native token asset Id (managed by pallet-balances)
Namespace
Type
This pallet's Id, used for deriving a sovereign account ID
Namespace
Type
Provide a set of uncles.
Namespace
Type
Author of current block.
Namespace
Type
Whether uncles were already set in this block.
Namespace
Type
Uncles
Namespace
Type
undefined## Errors
The uncle is genesis.
Namespace
The uncle parent not in the chain.
Namespace
The uncle isn't recent enough to be included.
Namespace
The uncle is too high in chain.
Namespace
Too many uncles.
Namespace
The uncle is already included.
Namespace
Uncles already set in the block.
Namespace
The number of blocks back we should accept uncles. This means that we will deal with uncle-parents that are UncleGenerations + 1
before now
.
Namespace
Type
Plan an epoch config change. The epoch config change is recorded and will be enacted on the next call to enact_epoch_change
. The config will be activated one epoch after. Multiple calls to this method will replace any existing planned config change that had not been enacted yet.
Namespace
Type
Report authority equivocation/misbehavior. This method will verify the equivocation proof and validate the given key ownership proof against the extracted offender. If both are valid, the offence will be reported.
Namespace
Type
Report authority equivocation/misbehavior. This method will verify the equivocation proof and validate the given key ownership proof against the extracted offender. If both are valid, the offence will be reported. This extrinsic must be called unsigned and it is expected that only block authors will call it (validated in ValidateUnsigned
), as such if the block author is defined it will be defined as the equivocation reporter.
Namespace
Type
Current epoch authorities.
Namespace
Type
This field should always be populated during block processing unless secondary plain slots are enabled (which don't contain a VRF output).
It is set in on_finalize
, before it will contain the value from the last block.
Namespace
Type
Current slot number.
Namespace
Type
The configuration for the current epoch. Should never be None
as it is initialized in genesis.
Namespace
Type
Current epoch index.
Namespace
Type
The block numbers when the last and current epoch have started, respectively N-1
and N
. NOTE: We track this is in order to annotate the block number when a given pool of entropy was fixed (i.e. it was known to chain observers). Since epochs are defined in slots, which may be skipped, the block numbers may not line up with the slot numbers.
Namespace
Type
The slot at which the first epoch actually started. This is 0 until the first block of the chain.
Namespace
Type
Temporary value (cleared at block finalization) which is Some
if per-block initialization has already been called for current block.
Namespace
Type
How late the current block is compared to its parent.
This entry is populated as part of block execution and is cleaned up on block finalization. Querying this storage entry outside of block execution context should always yield zero.
Namespace
Type
Next epoch authorities.
Namespace
Type
The configuration for the next epoch, None
if the config will not change (you can fallback to EpochConfig
instead in that case).
Namespace
Type
Next epoch randomness.
Namespace
Type
Pending epoch configuration change that will be applied when the next epoch is enacted.
Namespace
Type
The epoch randomness for the current epoch.
Security
This MUST NOT be used for gambling, as it can be influenced by a malicious validator in the short term. It MAY be used in many cryptographic protocols, however, so long as one remembers that this (like everything else on-chain) it is public. For example, it can be used where a number is needed that cannot have been chosen by an adversary, for purposes such as public-coin zero-knowledge proofs.
Namespace
Type
Randomness under construction.
We make a trade-off between storage accesses and list length. We store the under-construction randomness in segments of up to UNDER_CONSTRUCTION_SEGMENT_LENGTH
.
Once a segment reaches this length, we begin the next one. We reset all segments and return to 0
at the beginning of every epoch.
Namespace
Type
TWOX-NOTE: SegmentIndex
is an increasing integer, so this is okay.
Namespace
Type
undefined## Errors
A given equivocation report is valid but already previously reported.
Namespace
Submitted configuration is invalid.
Namespace
An equivocation proof provided as part of an equivocation report is invalid.
Namespace
A key ownership proof provided as part of an equivocation report is invalid.
Namespace
The amount of time, in slots, that each epoch should last. NOTE: Currently it is not possible to change the epoch duration after the chain has started. Attempting to do so will brick block production.
Namespace
Type
The expected average block time at which BABE should be creating blocks. Since BABE is probabilistic it is not trivial to figure out what the expected average block time should be based on the slot duration and the security parameter c
(where 1 - c
represents the probability of a slot being empty).
Namespace
Type
Max number of authorities allowed
Namespace
Type
epochAuthorship
Returns data about which slots (primary or secondary) can be claimed in the current epoch with the keys in the keystore.
Info: This method is only active with appropriate flags.
Interface
JSON
Approve an amount of asset for transfer by a delegated third-party account.
Origin must be Signed.
Ensures that ApprovalDeposit
worth of Currency
is reserved from signing account for the purpose of holding the approval. If some non-zero amount of assets is already approved from signing account to delegate
, then it is topped up or unreserved to meet the right value.
NOTE: The signing account does not need to own amount
of assets at the point of making this call.
id
: The identifier of the asset.
delegate
: The account to delegate permission to transfer asset.
amount
: The amount of asset that may be transferred by delegate
. If there is already an approval in place, then this acts additively.
Emits ApprovedTransfer
on success.
Weight: O(1)
Namespace
Type
Reduce the balance of who
by as much as possible up to amount
assets of id
.
Origin must be Signed and the sender should be the Manager of the asset id
.
Bails with NoAccount
if the who
is already dead.
id
: The identifier of the asset to have some amount burned.
who
: The account to be debited from.
amount
: The maximum amount by which who
's balance should be reduced.
Emits Burned
with the actual amount burned. If this takes the balance to below the minimum for the asset, then the amount burned is increased to take it to zero.
Weight: O(1)
Modes: Post-existence of who
; Pre & post Zombie-status of who
.
Namespace
Type
Cancel all of some asset approved for delegated transfer by a third-party account.
Origin must be Signed and there must be an approval in place between signer and delegate
.
Unreserves any deposit previously reserved by approve_transfer
for the approval.
id
: The identifier of the asset.
delegate
: The account delegated permission to transfer asset.
Emits ApprovalCancelled
on success.
Weight: O(1)
Namespace
Type
Clear the metadata for an asset.
Origin must be Signed and the sender should be the Owner of the asset id
.
Any deposit is freed for the asset owner.
id
: The identifier of the asset to clear.
Emits MetadataCleared
.
Weight: O(1)
Namespace
Type
Issue a new class of fungible assets from a public origin.
This new asset class has no assets initially and its owner is the origin.
The origin must be Signed and the sender must have sufficient funds free.
Funds of sender are reserved by AssetDeposit
.
Parameters:
id
: The identifier of the new asset. This must not be currently in use to identify an existing asset.
admin
: The admin of this class of assets. The admin is the initial address of each member of the asset class's admin team.
min_balance
: The minimum balance of this new asset that any single account must have. If an account's balance is reduced below this, then it collapses to zero.
Emits Created
event when successful.
Weight: O(1)
Namespace
Type
Destroy a class of fungible assets.
The origin must conform to ForceOrigin
or must be Signed and the sender must be the owner of the asset id
.
id
: The identifier of the asset to be destroyed. This must identify an existing asset.
Emits Destroyed
event when successful.
NOTE: It can be helpful to first freeze an asset before destroying it so that you can provide accurate witness information and prevent users from manipulating state in a way that can make it harder to destroy.
Weight: O(c + p + a)
where:
c = (witness.accounts - witness.sufficients)
s = witness.sufficients
a = witness.approvals
Namespace
Type
Alter the attributes of a given asset.
Origin must be ForceOrigin
.
id
: The identifier of the asset.
owner
: The new Owner of this asset.
issuer
: The new Issuer of this asset.
admin
: The new Admin of this asset.
freezer
: The new Freezer of this asset.
min_balance
: The minimum balance of this new asset that any single account must have. If an account's balance is reduced below this, then it collapses to zero.
is_sufficient
: Whether a non-zero balance of this asset is deposit of sufficient value to account for the state bloat associated with its balance storage. If set to true
, then non-zero balances may be stored without a consumer
reference (and thus an ED in the Balances pallet or whatever else is used to control user-account state growth).
is_frozen
: Whether this asset class is frozen except for permissioned/admin instructions.
Emits AssetStatusChanged
with the identity of the asset.
Weight: O(1)
Namespace
Type
Cancel all of some asset approved for delegated transfer by a third-party account.
Origin must be either ForceOrigin or Signed origin with the signer being the Admin account of the asset id
.
Unreserves any deposit previously reserved by approve_transfer
for the approval.
id
: The identifier of the asset.
delegate
: The account delegated permission to transfer asset.
Emits ApprovalCancelled
on success.
Weight: O(1)
Namespace
Type
Clear the metadata for an asset.
Origin must be ForceOrigin.
Any deposit is returned.
id
: The identifier of the asset to clear.
Emits MetadataCleared
.
Weight: O(1)
Namespace
Type
Issue a new class of fungible assets from a privileged origin.
This new asset class has no assets initially.
The origin must conform to ForceOrigin
.
Unlike create
, no funds are reserved.
id
: The identifier of the new asset. This must not be currently in use to identify an existing asset.
owner
: The owner of this class of assets. The owner has full superuser permissions over this asset, but may later change and configure the permissions using transfer_ownership
and set_team
.
min_balance
: The minimum balance of this new asset that any single account must have. If an account's balance is reduced below this, then it collapses to zero.
Emits ForceCreated
event when successful.
Weight: O(1)
Namespace
Type
Force the metadata for an asset to some value.
Origin must be ForceOrigin.
Any deposit is left alone.
id
: The identifier of the asset to update.
name
: The user friendly name of this asset. Limited in length by StringLimit
.
symbol
: The exchange symbol for this asset. Limited in length by StringLimit
.
decimals
: The number of decimals this asset uses to represent one unit.
Emits MetadataSet
.
Weight: O(N + S)
where N and S are the length of the name and symbol respectively.
Namespace
Type
Move some assets from one account to another.
Origin must be Signed and the sender should be the Admin of the asset id
.
id
: The identifier of the asset to have some amount transferred.
source
: The account to be debited.
dest
: The account to be credited.
amount
: The amount by which the source
's balance of assets should be reduced and dest
's balance increased. The amount actually transferred may be slightly greater in the case that the transfer would otherwise take the source
balance above zero but below the minimum balance. Must be greater than zero.
Emits Transferred
with the actual amount transferred. If this takes the source balance to below the minimum for the asset, then the amount transferred is increased to take it to zero.
Weight: O(1)
Modes: Pre-existence of dest
; Post-existence of source
; Account pre-existence of dest
.
Namespace
Type
Disallow further unprivileged transfers from an account.
Origin must be Signed and the sender should be the Freezer of the asset id
.
id
: The identifier of the asset to be frozen.
who
: The account to be frozen.
Emits Frozen
.
Weight: O(1)
Namespace
Type
Disallow further unprivileged transfers for the asset class.
Origin must be Signed and the sender should be the Freezer of the asset id
.
id
: The identifier of the asset to be frozen.
Emits Frozen
.
Weight: O(1)
Namespace
Type
Mint assets of a particular class.
The origin must be Signed and the sender must be the Issuer of the asset id
.
id
: The identifier of the asset to have some amount minted.
beneficiary
: The account to be credited with the minted assets.
amount
: The amount of the asset to be minted.
Emits Issued
event when successful.
Weight: O(1)
Modes: Pre-existing balance of beneficiary
; Account pre-existence of beneficiary
.
Namespace
Type
Return the deposit (if any) of an asset account.
The origin must be Signed.
id
: The identifier of the asset for the account to be created.
allow_burn
: If true
then assets may be destroyed in order to complete the refund.
Emits Refunded
event when successful.
Namespace
Type
Set the metadata for an asset.
Origin must be Signed and the sender should be the Owner of the asset id
.
Funds of sender are reserved according to the formula: MetadataDepositBase + MetadataDepositPerByte * (name.len + symbol.len)
taking into account any already reserved funds.
id
: The identifier of the asset to update.
name
: The user friendly name of this asset. Limited in length by StringLimit
.
symbol
: The exchange symbol for this asset. Limited in length by StringLimit
.
decimals
: The number of decimals this asset uses to represent one unit.
Emits MetadataSet
.
Weight: O(1)
Namespace
Type
Change the Issuer, Admin and Freezer of an asset.
Origin must be Signed and the sender should be the Owner of the asset id
.
id
: The identifier of the asset to be frozen.
issuer
: The new Issuer of this asset.
admin
: The new Admin of this asset.
freezer
: The new Freezer of this asset.
Emits TeamChanged
.
Weight: O(1)
Namespace
Type
Allow unprivileged transfers from an account again.
Origin must be Signed and the sender should be the Admin of the asset id
.
id
: The identifier of the asset to be frozen.
who
: The account to be unfrozen.
Emits Thawed
.
Weight: O(1)
Namespace
Type
Allow unprivileged transfers for the asset again.
Origin must be Signed and the sender should be the Admin of the asset id
.
id
: The identifier of the asset to be thawed.
Emits Thawed
.
Weight: O(1)
Namespace
Type
Create an asset account for non-provider assets.
A deposit will be taken from the signer account.
origin
: Must be Signed; the signer account must have sufficient funds for a deposit to be taken.
id
: The identifier of the asset for the account to be created.
Emits Touched
event when successful.
Namespace
Type
Move some assets from the sender account to another.
Origin must be Signed.
id
: The identifier of the asset to have some amount transferred.
target
: The account to be credited.
amount
: The amount by which the sender's balance of assets should be reduced and target
's balance increased. The amount actually transferred may be slightly greater in the case that the transfer would otherwise take the sender balance above zero but below the minimum balance. Must be greater than zero.
Emits Transferred
with the actual amount transferred. If this takes the source balance to below the minimum for the asset, then the amount transferred is increased to take it to zero.
Weight: O(1)
Modes: Pre-existence of target
; Post-existence of sender; Account pre-existence of target
.
Namespace
Type
Transfer some asset balance from a previously delegated account to some third-party account.
Origin must be Signed and there must be an approval in place by the owner
to the signer.
If the entire amount approved for transfer is transferred, then any deposit previously reserved by approve_transfer
is unreserved.
id
: The identifier of the asset.
owner
: The account which previously approved for a transfer of at least amount
and from which the asset balance will be withdrawn.
destination
: The account to which the asset balance of amount
will be transferred.
amount
: The amount of assets to transfer.
Emits TransferredApproved
on success.
Weight: O(1)
Namespace
Type
Move some assets from the sender account to another, keeping the sender account alive.
Origin must be Signed.
id
: The identifier of the asset to have some amount transferred.
target
: The account to be credited.
amount
: The amount by which the sender's balance of assets should be reduced and target
's balance increased. The amount actually transferred may be slightly greater in the case that the transfer would otherwise take the sender balance above zero but below the minimum balance. Must be greater than zero.
Emits Transferred
with the actual amount transferred. If this takes the source balance to below the minimum for the asset, then the amount transferred is increased to take it to zero.
Weight: O(1)
Modes: Pre-existence of target
; Post-existence of sender; Account pre-existence of target
.
Namespace
Type
Change the Owner of an asset.
Origin must be Signed and the sender should be the Owner of the asset id
.
id
: The identifier of the asset.
owner
: The new Owner of this asset.
Emits OwnerChanged
.
Weight: O(1)
Namespace
Type
The holdings of a specific account for a specific asset.
Namespace
Type
Approved balance transfers. First balance is the amount approved for transfer. Second is the amount of T::Currency
reserved for storing this. First key is the asset ID, second key is the owner and third key is the delegate.
Namespace
Type
Details of an asset.
Namespace
Type
Metadata of an asset.
Namespace
Type
An approval for account delegate
was cancelled by owner
.
Namespace
Type
(Additional) funds have been approved for transfer to a destination account.
Namespace
Type
Some asset asset_id
was frozen.
Namespace
Type
An asset has had its attributes changed by the Force
origin.
Namespace
Type
Some asset asset_id
was thawed.
Namespace
Type
Some assets were destroyed.
Namespace
Type
Some asset class was created.
Namespace
Type
An asset class was destroyed.
Namespace
Type
Some asset class was force-created.
Namespace
Type
Some account who
was frozen.
Namespace
Type
Some assets were issued.
Namespace
Type
Metadata has been cleared for an asset.
Namespace
Type
New metadata has been set for an asset.
Namespace
Type
The owner changed.
Namespace
Type
The management team changed.
Namespace
Type
Some account who
was thawed.
Namespace
Type
Some assets were transferred.
Namespace
Type
An amount
was transferred in its entirety from owner
to destination
by the approved delegate
.
Namespace
Type
The asset-account already exists.
Namespace
Invalid metadata given.
Namespace
Invalid witness data given.
Namespace
Account balance must be greater than or equal to the transfer amount.
Namespace
The origin account is frozen.
Namespace
The asset ID is already taken.
Namespace
Minimum balance should be non-zero.
Namespace
The account to alter does not exist.
Namespace
The asset-account doesn't have an associated deposit.
Namespace
The signing account has no permission to do the operation.
Namespace
Unable to increment the consumer reference counters on the account. Either no provider reference exists to allow a non-zero balance of a non-self-sufficient asset, or the maximum number of consumers has been reached.
Namespace
No approval exists that would allow the transfer.
Namespace
The given asset ID is unknown.
Namespace
The operation would result in funds being burned.
Namespace
The source account would not survive the transfer and it needs to stay alive.
Namespace
The amount of funds that must be reserved when creating a new approval.
Namespace
Type
The amount of funds that must be reserved for a non-provider asset account to be maintained.
Namespace
Type
The basic amount of funds that must be reserved for an asset.
Namespace
Type
The basic amount of funds that must be reserved when adding metadata to your asset.
Namespace
Type
The additional funds that must be reserved for the number of bytes you store in your metadata.
Namespace
Type
The maximum length of a name or symbol stored on-chain.
Namespace
Type
Exactly as transfer
, except the origin must be root and the source account may be specified.
Namespace
Type
Unreserve some balance from a user by force.
Can only be called by ROOT.
Namespace
Type
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 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
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 the transfer_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
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
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
Any liquidity locks on some account balances. NOTE: Should only be accessed when setting, changing and freeing a lock.
Namespace
Type
Named reserves on some account balances.
Namespace
Type
Storage version of the pallet.
This is set to v2.0.0 for new networks.
Namespace
Type
The total units issued in the system.
Namespace
Type
A balance was set by root.
Namespace
Type
Some amount was deposited (e.g. for transaction fees).
Namespace
Type
An account was removed whose balance was non-zero but below ExistentialDeposit, resulting in an outright loss.
Namespace
Type
An account was created with some free balance.
Namespace
Type
Some balance was reserved (moved from free to reserved).
Namespace
Type
Some balance was moved from the reserve of the first account to the second account. Final argument indicates the destination balance type.
Namespace
Type
Some amount was removed from the account (e.g. for misbehavior).
Namespace
Type
Transfer succeeded.
Namespace
Type
Some balance was unreserved (moved from reserved to free).
Namespace
Type
Some amount was withdrawn from the account (e.g. for transaction fees).
Namespace
Type
Beneficiary account must pre-exist
Namespace
Value too low to create account due to existential deposit
Namespace
A vesting schedule already exists for this account
Namespace
Balance too low to send value
Namespace
Transfer/payment would kill account
Namespace
Account liquidity restrictions prevent withdrawal
Namespace
Number of named reserves exceed MaxReserves
Namespace
Vesting balance too high to send value
Namespace
The minimum amount required to keep an account open.
Namespace
Type
The maximum number of locks that should exist on an account. Not strictly enforced, but used for weight estimation.
Namespace
Type
The maximum number of named reserves that can exist on an account.
Namespace
Type
Add liquidity to Enabled trading pair, or add provision to Provisioning trading pair.
Add liquidity success will issue shares in current price which decided by the liquidity scale. Shares are temporarily not allowed to transfer and trade, it represents the proportion of assets in liquidity pool.
Add provision success will record the provision, issue shares to caller in the initial price when trading pair convert to Enabled.
Creates and enables TradingPair LP token if it does not exist for trading pair.
Fails to add liquidity for NotEnabled
trading pair.
token_a
: Asset id A.
token_b
: Asset id B.
amount_a_desired
: amount a desired to add.
amount_b_desired
: amount b desired to add.
amount_a_min
: amount a minimum willing to add.
amount_b_min
: amount b minimum willing to add.
to
: The recipient of the LP token. The caller is the default recipient if it is set to None.
deadline
: The deadline of executing this extrinsic. The deadline won't be checked if it is set to None
Namespace
Type
Disable an Enabled
trading pair.
Requires LP token to be created and in the Enabled
status
Only root can disable trading pair
token_a
: Asset id A.
token_b
: Asset id B.
Namespace
Type
Re enable a NotEnabled
trading pair.
Requires LP token to be created and in the NotEnabled
status
Only root can enable a disabled trading pair
token_a
: Asset id A.
token_b
: Asset id B.
Namespace
Type
Remove liquidity from specific liquidity pool in the form of burning shares, and withdrawing currencies in trading pairs from liquidity pool in proportion, and withdraw liquidity incentive interest.
note: liquidity can still be withdrawn for NotEnabled
trading pairs.
token_a
: Asset id A.
token_b
: Asset id B.
liquidity
: liquidity amount to remove.
amount_a_min
: minimum amount of asset A to be withdrawn from LP token.
amount_b_min
: minimum amount of asset B to be withdrawn from LP token.
to
: The recipient of the withdrawn token assets. The caller is the default recipient if it is set to None.
deadline
: The deadline of executing this extrinsic. The deadline won't be checked if it is set to None
Namespace
Type
Set the FeeTo
account. This operation requires root access.
note: analogous to Uniswapv2 setFeeTo
fee_to
: the new account or None assigned to FeeTo.
Namespace
Type
Trading with DEX, swap with exact supply amount. Specify your input; retrieve variable output.
note: analogous to Uniswapv2 swapExactTokensForTokens
path
: trading path.
amount_in
: exact supply amount.
amount_out_min
: acceptable minimum target amount.
to
: The recipient of the swapped token asset. The caller is the default recipient if it is set to None.
deadline
: The deadline of executing this extrinsic. The deadline won't be checked if it is set to None
Namespace
Type
Trading with DEX, swap with exact target amount. Specify your output; supply variable input.
note: analogous to Uniswapv2 swapTokensForExactTokens
amount_out
: exact target amount.
amount_in_max
: acceptable maximum supply amount.
path
: trading path.
to
: The recipient of the swapped token asset. The caller is the default recipient if it is set to None.
deadline
: The deadline of executing this extrinsic. The deadline won't be checked if it is set to None
Namespace
Type
FeeTo account where network fees are deposited
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Add liquidity success. [who, asset_id_0, reserve_0_increment, asset_id_1, reserve_1_increment, share_increment, to]
Namespace
Type
Add provision success. [who, asset_id_0, contribution_0, asset_id_1, contribution_1]
Namespace
Type
Disable trading pair. [trading_pair]
Namespace
Type
Enable trading pair. [trading_pair]
Namespace
Type
Set FeeTo account success. [fee_to]
Namespace
Type
Provisioning trading pair convert to Enabled. [trading_pair, pool_0_amount, pool_1_amount, total_share_amount]
Namespace
Type
Remove liquidity from the trading pool success. [who, asset_id_0, reserve_0_decrement, asset_id_1, reserve_1_decrement, share_decrement, to]
Namespace
Type
Use supply Asset to swap target Asset. [trader, trading_path, supply_Asset_amount, target_Asset_amount, to]
Namespace
Type
Supply amount is more than max_supply_amount
Namespace
The deadline has been missed
Namespace
Namespace
Insufficent amount
Namespace
Insufficient asset_a liquidity amount
Namespace
Insufficient asset_b liquidity amount
Namespace
Insufficient input amount
Namespace
Liquidity is not enough
Namespace
Insufficient liquidity burnt
Namespace
Insufficient output amount
Namespace
Target amount is less to min_target_amount
Namespace
Insufficient withdraw amount for token A
Namespace
Insufficient withdraw amount for token B
Namespace
Invalid Asset id
Namespace
Invalid constant product K
Namespace
Must provide non-zero amount of liquidity
Namespace
The increment of liquidity is invalid
Namespace
Invalid trading path length
Namespace
The Liquidity Provider token does not exist
Namespace
Trading pair must be in Enabled status
Namespace
Trading pair must be in NotEnabled status
Namespace
The supply amount is zero
Namespace
The target amount is zero
Namespace
The default FeeTo account
Namespace
Type
The DEX's burn id, to provide for a redundant, unredeemable minter/burner address.
Namespace
Type
Trading fee rate The first item of the tuple is the numerator of the fee rate, second item is the denominator, fee_rate = numerator / denominator, use (u32, u32) over Rate
type to minimize internal division operation.
Namespace
Type
Liquidity pair default token decimals
Namespace
Type
The limit for length of trading path
Namespace
Type
getAmountsIn
Given an array of AssetIds, return amounts in for an amount out
Interface
JSON
getAmountsOut
Given an array of AssetIds, return amounts out for an amount in
Interface
JSON
getLPTokenID
Given two AssetIds, return liquidity token created for the pair
Interface
JSON
getLiquidity
Given two AssetIds, return liquidity
Interface
JSON
getTradingPairStatus
Given two AssetIds, return whether trading pair is enabled or disabled
Interface
JSON
quote
Given some amount of an asset and pair reserves, returns an equivalent amount of the other asset
Interface
JSON
Ping extrinsic sends an event to the bridge containing a message
Namespace
Type
The next available offer_id
Namespace
Type
A ping was received from Ethereum
Namespace
Type
A ping message was sent to Ethereum
Namespace
Type
A pong response was received from Ethereum
Namespace
Type
A pong message was sent to Ethereum
Namespace
Type
The abi received does not match the encoding scheme
Namespace
Invalid ping_or_pong parameter, must be 0 or 1
Namespace
There are no remaining session ids
Namespace
This pallet's Id, used for deriving a sovereign account ID
Namespace
Type
Trigger the governance fallback.
This can only be called when [Phase::Emergency
] is enabled, as an alternative to calling [Call::set_emergency_election_result
].
Namespace
Type
Set a solution in the queue, to be handed out to the client of this pallet in the next call to ElectionProvider::elect
.
This can only be set by T::ForceOrigin
, and only when the phase is Emergency
.
The solution is not checked for any feasibility and is assumed to be trustworthy, as any feasibility check itself can in principle cause the election process to fail (due to memory/weight constrains).
Namespace
Type
Set a new value for MinimumUntrustedScore
.
Dispatch origin must be aligned with T::ForceOrigin
.
This check can be turned off by setting the value to None
.
Namespace
Type
Submit a solution for the signed phase.
The dispatch origin for this call must be signed.
The solution is potentially queued, based on the claimed score and processed at the end of the signed phase.
A deposit is reserved and recorded for the solution. Based on the outcome, the solution might be rewarded, slashed, or get all or a part of the deposit back.
Namespace
Type
Submit a solution for the unsigned phase.
The dispatch origin for this call must be none.
This submission is checked on the fly. Moreover, this unsigned solution is only validated when submitted to the pool from the local node. Effectively, this means that only active validators can submit this transaction when authoring a block (similar to an inherent).
To prevent any incorrect solution (and thus wasted time/weight), this transaction will panic if the solution submitted by the validator is invalid in any way, effectively putting their authoring reward at risk.
No deposit or reward is associated with this submission.
Namespace
Type
Current phase.
Namespace
Type
Desired number of targets to elect for this round.
Only exists when [Snapshot
] is present.
Namespace
Type
The minimum score that each 'untrusted' solution must attain in order to be considered feasible.
Can be set via set_minimum_untrusted_score
.
Namespace
Type
Current best solution, signed or unsigned, queued to be returned upon elect
.
Namespace
Type
Internal counter for the number of rounds.
This is useful for de-duplication of transactions submitted to the pool, and general diagnostics of the pallet.
This is merely incremented once every time that an upstream elect
is called.
Namespace
Type
A sorted, bounded set of (score, index)
, where each index
points to a value in SignedSubmissions
.
We never need to process more than a single signed submission at a time. Signed submissions can be quite large, so we're willing to pay the cost of multiple database accesses to access them one at a time instead of reading and decoding all of them at once.
Namespace
Type
The next index is to be assigned to an incoming signed submission.
Every accepted submission is assigned a unique index; that index is bound to that particular submission for the duration of the election. On election finalization, the next index is reset to 0.
We can't just use SignedSubmissionIndices.len()
, because that's a bounded set; past its capacity, it will simply saturate. We can't just iterate over SignedSubmissionsMap
, because iteration is slow. Instead, we store the value here.
Namespace
Type
Unchecked, signed solutions.
Together with SubmissionIndices
, this stores a bounded set of SignedSubmissions
while allowing us to keep only a single one in memory at a time.
Twox note: the key of the map is an auto-incrementing index which users cannot inspect or affect; we shouldn't need a cryptographically secure hasher.
Namespace
Type
Snapshot data of the round.
This is created at the beginning of the signed phase and cleared upon calling elect
.
Namespace
Type
The metadata of the [RoundSnapshot
]
Only exists when [Snapshot
] is present.
Namespace
Type
An election failed.
Not much can be said about which computes failed in the process.
Namespace
Type
The election has been finalized, with the given computation and score.
Namespace
Type
An account has been rewarded for their signed submission being finalized.
Namespace
Type
The signed phase of the given round has started.
Namespace
Type
An account has been slashed for submitting an invalid signed submission.
Namespace
Type
A solution was stored with the given compute.
If the solution is signed, this means that it hasn't yet been processed. If the solution is unsigned, this means that it has also been processed.
The bool
is true
when a previous solution was ejected to make room for this one.
Namespace
Type
The unsigned phase of the given round has started.
Namespace
Type
The call is not allowed at this point.
Namespace
The fallback failed
Namespace
Self::insert_submission
returned an invalid index.
Namespace
Snapshot metadata should exist but didn't.
Namespace
OCW submitted solution for wrong round
Namespace
Submission was too early.
Namespace
Submission was too weak, score-wise.
Namespace
Wrong number of winners presented.
Namespace
The origin failed to pay the deposit.
Namespace
Witness data to dispatchable is invalid.
Namespace
The queue was full, and the solution was not better than any of the existing ones.
Namespace
The signed submission consumes too much weight
Namespace
The minimum amount of improvement to the solution score that defines a solution as "better" in the Signed phase.
Namespace
Type
The minimum amount of improvement to the solution score that defines a solution as "better" in the Unsigned phase.
Namespace
Type
The maximum number of electable targets to put in the snapshot.
Namespace
Type
The maximum number of electing voters to put in the snapshot. At the moment, snapshots are only over a single block, but once multi-block elections are introduced they will take place over multiple blocks.
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
The priority of the unsigned transaction submitted in the unsigned-phase
Namespace
Type
The repeat threshold of the offchain worker.
For example, if it is 5, that means that at least 5 blocks will elapse between attempts to submit the worker's solution.
Namespace
Type
Base deposit for a signed solution.
Namespace
Type
Per-byte deposit for a signed solution.
Namespace
Type
Per-weight deposit for a signed solution.
Namespace
Type
The maximum amount of unchecked solutions to refund the call fee for.
Namespace
Type
Maximum number of signed submissions that can be queued.
It is best to avoid adjusting this during an election, as it impacts downstream data structures. In particular, SignedSubmissionIndices<T>
is bounded on this value. If you update this value during an election, you must ensure that SignedSubmissionIndices.len()
is less than or equal to the new value. Otherwise, attempts to submit new solutions may cause a runtime panic.
Namespace
Type
Maximum weight of a signed solution.
If [Config::MinerConfig
] is being implemented to submit signed solutions (outside of this pallet), then [MinerConfig::solution_weight
] is used to compare against this value.
Namespace
Type
Duration of the signed phase.
Namespace
Type
Base reward for a signed solution
Namespace
Type
Duration of the unsigned phase.
Namespace
Type
Activate/deactivate deposits (root only)
Namespace
Type
Activate/deactivate withdrawals (root only)
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Map GA asset Id to ERC20 address
Namespace
Type
The peg contract address on Ethereum
Namespace
Type
Map from DelayedPaymentId to PendingPayment
Namespace
Type
Map from block number to DelayedPaymentIds scheduled for that block
Namespace
Type
Whether deposit are active
Namespace
Type
Metadata for well-known erc20 tokens (symbol, decimals)
Namespace
Type
Map ERC20 address to GA asset Id
Namespace
Type
The next available payment id for withdrawals and deposits
Namespace
Type
Map from asset_id to minimum amount and delay
Namespace
Type
The blocks with payments that are ready to be processed
Namespace
Type
The ROOT peg contract address on Ethereum
Namespace
Type
Whether withdrawals are active
Namespace
Type
A delayed erc20 deposit has failed (payment_id, beneficiary)
Namespace
Type
A delayed erc20 withdrawal has failed (asset_id, beneficiary)
Namespace
Type
A bridged erc20 deposit succeeded. (asset, amount, beneficiary)
Namespace
Type
An erc20 deposit has been delayed.(payment_id, scheduled block, amount, beneficiary)
Namespace
Type
A bridged erc20 deposit failed. (source address, abi data)
Namespace
Type
Tokens were burnt for withdrawal on Ethereum as ERC20s (asset, amount, beneficiary)
Namespace
Type
A withdrawal has been delayed.(payment_id, scheduled block, amount, beneficiary)
Namespace
Type
There are no more payment ids available, they've been exhausted
Namespace
Type
A delay was added for an asset_id (asset_id, min_balance, delay)
Namespace
Type
The peg contract address has been set
Namespace
Type
The ROOT peg contract address has been set
Namespace
Type
Could not create the bridged asset
Namespace
Deposits are inactive
Namespace
Withdrawals over the set payment delay for EVM calls are disabled
Namespace
The abi received does not match the encoding scheme
Namespace
Deposit has bad amount
Namespace
Could not convert pallet id to account
Namespace
The peg source address is incorrect for the token being bridged
Namespace
Withdrawals of this asset are not supported
Namespace
Withdrawals are inactive
Namespace
undefined
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Flag to indicate whether authorities have been changed during the current era
Namespace
Type
Whether the bridge is paused (e.g. during validator transitions or by governance)
Namespace
Type
The (optimistic) challenge period after which a submitted event is considered valid
Namespace
Type
Maps from event claim id to challenger and bond amount paid
Namespace
Type
The bridge contract address on Ethereum
Namespace
Type
The maximum number of delayed events that can be processed in on_initialize()
Namespace
Type
EthCallOracle notarizations keyed by (Id, Notary)
Namespace
Type
map from EthCallOracle notarizations to an aggregated count
Namespace
Type
EthCallOracle request info
Namespace
Type
Queue of pending EthCallOracle requests
Namespace
Type
The minimum number of block confirmations needed to notarize an Ethereum event
Namespace
Type
Notarizations for queued events Either: None = no notarization exists OR Some(yay/nay)
Namespace
Type
Map from block number to list of EventClaims that will be considered valid and should be forwarded to handlers (i.e after the optimistic challenge period has passed without issue)
Namespace
Type
The block in which we process the next authority change
Namespace
Type
Subscription Id for EthCall requests
Namespace
Type
Id of the next event proof
Namespace
Type
Scheduled notary (validator) public keys for the next session
Namespace
Type
Active notary (validator) public keys
Namespace
Type
The current validator set id
Namespace
Type
The event proof Id generated by the previous validator set to notarize the current set. Useful for syncing the latest proof to Ethereum
Namespace
Type
Active xrpl notary (validator) public keys
Namespace
Type
List of all event ids that are currently being challenged
Namespace
Type
Status of pending event claims
Namespace
Type
Queued event claims, can be challenged within challenge period
Namespace
Type
Queued event proofs to be processed once bridge has been re-enabled
Namespace
Type
Tracks processed message Ids (prevent replay)
Namespace
Type
The permissioned relayer
Namespace
Type
Maps from relayer account to their paid bond amount
Namespace
Type
Door Signers set by sudo (white list)
Namespace
Type
The event proof Id generated by the previous validator set to notarize the current set. Useful for syncing the latest proof to Xrpl
Namespace
Type
A notary (validator) set change is in motion (event_id, new_validator_set_id) A proof for the change will be generated with the given event_id
Namespace
Type
An event has been challenged (claim_id, challenger)
Namespace
Type
An event proof has been sent for signing by ethy-gadget
Namespace
Type
An event has been submitted from Ethereum (event_claim_id, event_claim, process_at)
Namespace
Type
The schedule to unpause the bridge has failed (scheduled_block)
Namespace
Type
Verifying an event failed
Namespace
Type
The event is still awaiting consensus. Process block pushed out (claim_id, process_at)
Namespace
Type
Processing an event failed
Namespace
Type
Processing an event succeeded
Namespace
Type
Generating event proof delayed as bridge is paused
Namespace
Type
An account has deposited a relayer bond
Namespace
Type
An account has withdrawn a relayer bond
Namespace
Type
A new relayer has been set
Namespace
Type
The bridge contract address has been set
Namespace
Type
Verifying an event succeeded
Namespace
Type
A notary (validator) set change for Xrpl is in motion (event_id, new_validator_set_id) A proof for the change will be generated with the given event_id
Namespace
Type
Xrpl authority set change request failed
Namespace
Type
Xrpl Door signers are set
Namespace
Type
The bridge is paused pending validator set changes (once every era / 24 hours) It will reactive after ~10 minutes
Namespace
The relayer already has a bonded amount
Namespace
The relayer is active and cant unbond the specified amount
Namespace
There is already a challenge for this claim
Namespace
Event was already submitted and is pending
Namespace
Event was already submitted and is complete
Namespace
Namespace
Some internal operation failed
Namespace
Claim was invalid e.g. not properly ABI encoded
Namespace
A notarization was invalid
Namespace
Someone tried to set a greater amount of validators than allowed
Namespace
The relayer hasn't paid the relayer bond so can't be set as the active relayer
Namespace
There is no event claim associated with the supplied claim_id
Namespace
Namespace
Caller does not have permission for that action
Namespace
offchain worker not configured properly
Namespace
Namespace
undefined
Transact an Ethereum transaction.
Namespace
Type
Namespace
Type
The current Ethereum block.
Namespace
Type
The current Ethereum receipts.
Namespace
Type
The current transaction statuses.
Namespace
Type
Current building block's transactions and receipts.
Namespace
Type
An ethereum transaction was successfully executed.
Namespace
Type
Namespace
Namespace
Namespace
Namespace
Namespace
Signature is invalid.
Namespace
Pre-log is present, therefore transact is not allowed.
Namespace
Namespace
undefined
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
The EVM base fee has been set to base_fee
Namespace
Type
The length multiplier has been set to length_multiplier
Namespace
Type
The weight multiplier has been set to weight_multiplier
Namespace
Type
undefined
Issue an EVM call operation. This is similar to a message call transaction in Ethereum.
Namespace
Type
Issue an EVM create operation. This is similar to a contract creation transaction in Ethereum.
Namespace
Type
Issue an EVM create2 operation.
Namespace
Type
Withdraw balance from EVM into currency/balances pallet.
Namespace
Type
Namespace
Type
Namespace
Type
A contract has been created at given address.
Namespace
Type
A contract was attempted to be created, but the execution failed.
Namespace
Type
A contract has been executed successfully with states applied.
Namespace
Type
A contract has been executed with errors. States are reverted with only gas fees applied.
Namespace
Type
Ethereum events from contracts.
Namespace
Type
Not enough balance to perform action
Namespace
Calculating total fee overflowed
Namespace
Gas limit is too high.
Namespace
Gas limit is too low.
Namespace
Gas price is too low.
Namespace
Nonce is invalid
Namespace
Calculating total payment overflowed
Namespace
EVM reentrancy
Namespace
Undefined error.
Namespace
Withdraw fee failed
Namespace
undefined
Call an internal call with specified gas token payment_asset: The token to be used for paying gas fees. This is exchanged in OnChargeTransaction::withdraw_fee() max_payment: The limit of how many tokens will be used to perform the exchange call: The inner call to be performed after the exchange
Namespace
Type
undefined## Events
A call was made with specified payment asset
Namespace
Type
The selected fee token is equal to the native gas token
Namespace
The inner call is a fee preference call
Namespace
The native token asset Id (managed by pallet-balances)
Namespace
Type
Note that the current authority set of the GRANDPA finality gadget has stalled.
This will trigger a forced authority set change at the beginning of the next session, to be enacted delay
blocks after that. The delay
should be high enough to safely assume that the block signalling the forced change will not be re-orged e.g. 1000 blocks. The block production rate (which may be slowed down because of finality lagging) should be taken into account when choosing the delay
. The GRANDPA voters based on the new authority will start voting on top of best_finalized_block_number
for new finalized blocks. best_finalized_block_number
should be the highest of the latest finalized block of all validators of the new authority set.
Note: Only callable by root.
Namespace
Type
Report voter equivocation/misbehavior. This method will verify the equivocation proof and validate the given key ownership proof against the extracted offender. If both are valid, the offence will be reported.
Namespace
Type
Report voter equivocation/misbehavior. This method will verify the equivocation proof and validate the given key ownership proof against the extracted offender. If both are valid, the offence will be reported.
This extrinsic must be called unsigned and it is expected that only block authors will call it (validated in ValidateUnsigned
), as such if the block author is defined it will be defined as the equivocation reporter.
Namespace
Type
The number of changes (both in terms of keys and underlying economic responsibilities) in the "set" of Grandpa validators from genesis.
Namespace
Type
next block number where we can force a change.
Namespace
Type
Pending change: (signaled at, scheduled change).
Namespace
Type
A mapping from grandpa set ID to the index of the most recent session for which its members were responsible.
TWOX-NOTE: SetId
is not under user control.
Namespace
Type
true
if we are currently stalled.
Namespace
Type
State of the current authority set.
Namespace
Type
New authority set has been applied.
Namespace
Type
Current authority set has been paused.
Namespace
Type
Current authority set has been resumed.
Namespace
Type
Attempt to signal GRANDPA change with one already pending.
Namespace
A given equivocation report is valid but already previously reported.
Namespace
An equivocation proof provided as part of an equivocation report is invalid.
Namespace
A key ownership proof provided as part of an equivocation report is invalid.
Namespace
Attempt to signal GRANDPA pause when the authority set isn't live (either paused or already pending pause).
Namespace
Attempt to signal GRANDPA resume when the authority set isn't paused (either live or already pending resume).
Namespace
Cannot signal forced change so soon after last.
Namespace
Max Authorities in use
Namespace
Type
proveFinality
Prove finality for the given block number, returning the Justification for the last block in the set.
Interface
JSON
roundState
Returns the state of the current best round state as well as the ongoing background rounds
Interface
JSON
subscribeJustifications
Subscribes to grandpa justifications
Interface
JSON
Create a FuturePass account for the delegator who is able to make calls on behalf of FuturePass.
The dispatch origin for this call must be Signed.
Parameters:
account
: The delegated account for the FuturePass.
Namespace
Type
This extrinsic migrates EVM-based FuturePass assets to the Substrate-based FuturePass (native).
Parameters:
owner
- The account ID of the owner of the EVM-based FuturePass.
evm_futurepass
- The account ID of the EVM-based FuturePass.
asset_ids
- A vector of asset IDs representing the assets to be migrated.
collection_ids
- A vector of collection IDs representing the NFTs collections to be migrated.
Namespace
Type
Dispatch the given call through FuturePass account. Transaction fees will be paid by the FuturePass. The dispatch origin for this call must be Signed
Parameters:
futurepass
: The FuturePass account through which the call is dispatched
call
: The Call that needs to be dispatched through the FuturePass account
Namespace
Type
Register a delegator to an existing FuturePass account given message parameters for a respective signature.
Note:
Only FuturePass owner account can add more delegates.
The signer is recovered from the signature given the message parameters (which are used to reconstruct the message).
You can assume the message is constructed like so:
--- solidity bytes32 message = keccak256(abi.encodePacked(futurepass, delegate, proxyType, deadline)); ethSignedMessage = keccak256(abi.encodePacked("\x19Ethereum Signed Message:\n32", message));
The dispatch origin for this call must be Signed.
Parameters:
futurepass
: FuturePass account to register the account as delegate; 20 bytes.
delegate
: The delegated account for the futurepass; 20 bytes.
proxy_type
: Delegate permission level; 1 byte.
deadline
: Deadline for the signature; 4 bytes.
signature
: Signature of the message parameters.
Namespace
Type
Update FuturePass native assets migrator admin account.
The dispatch origin for this call must be sudo/root origin.
Parameters:
migrator
: The new account that will become the FuturePass asset migrator.
Namespace
Type
Transfer ownership of a FuturePass to a new account. The new owner must not already own a FuturePass. This removes all delegates from the FuturePass. The new owner will be the only delegate; they can add more delegates.
The dispatch origin for this call must be Signed and must be the current owner of the FuturePass.
Parameters:
current_owner
: The current owner of the FuturePass.
new_owner
: The new account that will become the owner of the FuturePass.
Namespace
Type
Unregister a delegate from a FuturePass account.
The dispatch origin for this call must be Signed.
Parameters:
futurepass
: FuturePass account to unregister the delegate from.
delegate
: The delegated account for the FuturePass.
Note: If the caller is FuturePass holder owner, they can remove any delegate (including themselves); otherwise the caller must be the delegate (can only remove themself).
Namespace
Type
Accounts which have set FuturePass as default proxied on-chain account (delegate -> FuturePass)
Namespace
Type
FuturePass holders (account -> futurepass)
Namespace
Type
Migration data for the user (root) and collections they can migrate
Namespace
Type
The next available incrementing futurepass id
Namespace
Type
FuturePass set as default proxy
Namespace
Type
Delegate registration to FuturePass account
Namespace
Type
Delegate unregistration from FuturePass account
Namespace
Type
Migration of FuturePass assets
Namespace
Type
FuturePass creation
Namespace
Type
Updating FuturePass migrator account
Namespace
Type
FuturePass transfer
Namespace
Type
A proxy call was executed with the given call
Namespace
Type
Account is already FuturePass holder
Namespace
AccountParsingFailure
Namespace
Account already exists as a delegate
Namespace
Account is not FuturePass delegate
Namespace
ExpiredDeadline
Namespace
Invalid deadline
Namespace
Invalid proxy type
Namespace
Invalid signature
Namespace
FuturePass migrator admin account is not set
Namespace
Account is not FuturePass owner
Namespace
FuturePass owner cannot remove themselves
Namespace
Account does not have permission to call this function
Namespace
RegisterDelegateSignerMismatch
Namespace
undefined
Namespace
Type
For each session index, we keep a mapping of ValidatorId<T>
to the number of blocks authored by the given authority.
Namespace
Type
The block number after which it's ok to send heartbeats in the current session.
At the beginning of each session we set this to a value that should fall roughly in the middle of the session duration. The idea is to first wait for the validators to produce a block in the current session, so that the heartbeat later on will not be necessary.
This value will only be used as a fallback if we fail to get a proper session progress estimate from NextSessionRotation
, as those estimates should be more accurate then the value we calculate for HeartbeatAfter
.
Namespace
Type
The current set of keys that may issue a heartbeat.
Namespace
Type
For each session index, we keep a mapping of SessionIndex
and AuthIndex
to WrapperOpaque<BoundedOpaqueNetworkState>
.
Namespace
Type
At the end of the session, no offence was committed.
Namespace
Type
A new heartbeat was received from AuthorityId
.
Namespace
Type
At the end of the session, at least one validator was found to be offline.
Namespace
Type
Duplicated heartbeat.
Namespace
Non existent public key.
Namespace
A configuration for base priority of unsigned transactions.
This is exposed so that it can be tuned for particular runtime, when multiple pallets send unsigned transactions.
Namespace
Type
Blocks an account from transacting on the network
Namespace
Type
Blocks a call from being executed pallet_name: The name of the pallet as per the runtime file. i.e. FeeProxy call_name: The snake_case name for the call. i.e. set_fee Both pallet and call names are not case sensitive
Namespace
Type
Blocks an account from transacting on the network Can be used to block individual precompile addresses or contracts
Namespace
Type
Blocks an entire pallets calls from being executed pallet_name: The name of the pallet as per the runtime file. i.e. FeeProxy Pallet names are not case sensitive
Namespace
Type
Enable maintenance mode which prevents all non sudo calls
Namespace
Type
Map from account to blocked status
Namespace
Type
Map from call to blocked status map (PalletNameBytes, FunctionNameBytes) => bool
Namespace
Type
Map from EVM target address to blocked status
Namespace
Type
Map from pallet to blocked status map PalletNameBytes => bool
Namespace
Type
Determines whether maintenance mode is currently active
Namespace
Type
An account was blocked
Namespace
Type
An account was blocked
Namespace
Type
An account was blocked
Namespace
Type
Maintenance mode was activated
Namespace
Type
An account was blocked
Namespace
Type
This account is not authorized to execute this transaction
Namespace
This pallet or call cannot be blocked
Namespace
The call name is not valid utf-8 characters
Namespace
The pallet name is not valid utf-8 characters
Namespace
This call is disabled as the chain is in maintenance mode
Namespace
The maximum length of a pallet or call name, stored on-chain
Namespace
Type
Register approval for a dispatch to be made from a deterministic composite account if approved by a total of threshold - 1
of other_signatories
.
Payment: DepositBase
will be reserved if this is the first approval, plus threshold
times DepositFactor
. It is returned once this dispatch happens or is cancelled.
The dispatch origin for this call must be Signed.
threshold
: The total number of approvals for this dispatch before it is executed.
other_signatories
: The accounts (other than the sender) who can approve this dispatch. May not be empty.
maybe_timepoint
: If this is the first approval, then this must be None
. If it is not the first approval, then it must be Some
, with the timepoint (block number and transaction index) of the first approval transaction.
call_hash
: The hash of the call to be executed.
NOTE: If this is the final approval, you will want to use as_multi
instead.
Namespace
Type
Register approval for a dispatch to be made from a deterministic composite account if approved by a total of threshold - 1
of other_signatories
.
If there are enough, then dispatch the call.
Payment: DepositBase
will be reserved if this is the first approval, plus threshold
times DepositFactor
. It is returned once this dispatch happens or is cancelled.
The dispatch origin for this call must be Signed.
threshold
: The total number of approvals for this dispatch before it is executed.
other_signatories
: The accounts (other than the sender) who can approve this dispatch. May not be empty.
maybe_timepoint
: If this is the first approval, then this must be None
. If it is not the first approval, then it must be Some
, with the timepoint (block number and transaction index) of the first approval transaction.
call
: The call to be executed.
NOTE: Unless this is the final approval, you will generally want to use approve_as_multi
instead, since it only requires a hash of the call.
Result is equivalent to the dispatched result if threshold
is exactly 1
. Otherwise on success, result is Ok
and the result from the interior call, if it was executed, may be found in the deposited MultisigExecuted
event.
Namespace
Type
Immediately dispatch a multi-signature call using a single approval from the caller.
The dispatch origin for this call must be Signed.
other_signatories
: The accounts (other than the sender) who are part of the multi-signature, but do not participate in the approval process.
call
: The call to be executed.
Result is equivalent to the dispatched result.
Namespace
Type
Cancel a pre-existing, on-going multisig transaction. Any deposit reserved previously for this operation will be unreserved on success.
The dispatch origin for this call must be Signed.
threshold
: The total number of approvals for this dispatch before it is executed.
other_signatories
: The accounts (other than the sender) who can approve this dispatch. May not be empty.
timepoint
: The timepoint (block number and transaction index) of the first approval transaction for this dispatch.
call_hash
: The hash of the call to be executed.
Namespace
Type
Namespace
Type
The set of open multisig operations.
Namespace
Type
A multisig operation has been approved by someone.
Namespace
Type
A multisig operation has been cancelled.
Namespace
Type
A multisig operation has been executed.
Namespace
Type
A new multisig operation has begun.
Namespace
Type
Call is already approved by this signatory.
Namespace
The data to be stored is already stored.
Namespace
The maximum weight information provided was too low.
Namespace
Threshold must be 2 or greater.
Namespace
Call doesn't need any (more) approvals.
Namespace
Multisig operation not found when attempting to cancel.
Namespace
No timepoint was given, yet the multisig operation is already underway.
Namespace
Only the account that originally created the multisig is able to cancel it.
Namespace
The sender was contained in the other signatories; it shouldn't be.
Namespace
The signatories were provided out of order; they should be ordered.
Namespace
There are too few signatories in the list.
Namespace
There are too many signatories in the list.
Namespace
A timepoint was given, yet no multisig operation is underway.
Namespace
A different timepoint was given to the multisig operation that is underway.
Namespace
The base amount of currency needed to reserve for creating a multisig execution or to store a dispatch call for later.
This is held for an additional storage item whose value size is 4 + sizeof((BlockNumber, Balance, AccountId))
bytes and whose key size is 32 + sizeof(AccountId)
bytes.
Namespace
Type
The amount of currency needed per unit threshold when creating a multisig execution.
This is held for adding 32 bytes more into a pre-existing storage value.
Namespace
Type
The maximum amount of signatories allowed in the multisig.
Namespace
Type
Accepts an offer on a token Caller must be token owner
Namespace
Type
Auction a bundle of tokens on the open market to the highest bidder
Tokens must be from the same collection
Tokens with individual royalties schedules cannot be sold in bundles
Caller must be the token owner
payment_asset
fungible asset Id to receive payment with
reserve_price
winning bid must be over this threshold
duration
length of the auction (in blocks), uses default duration if unspecified
Namespace
Type
Place a bid on an open auction
amount
to bid (in the seller's requested payment asset)
Namespace
Type
Buy a token listing for its specified price
Namespace
Type
Cancels an offer on a token Caller must be the offer buyer
Namespace
Type
Close a sale or auction returning tokens Requires no successful bids have been made for an auction. Caller must be the listed seller
Namespace
Type
Create an offer on a token Locks funds until offer is accepted, rejected or cancelled An offer can't be made on a token currently in an auction (This follows the behaviour of Opensea and forces the buyer to bid rather than create an offer)
Namespace
Type
Flag an account as a marketplace
marketplace_account
- if specified, this account will be registered entitlement
- Permill, percentage of sales to go to the marketplace If no marketplace is specified the caller will be registered
Namespace
Type
Sell a bundle of tokens at a fixed price
Tokens must be from the same collection
Tokens with individual royalties schedules cannot be sold with this method
buyer
optionally, the account to receive the NFT. If unspecified, then any account may purchase asset_id
fungible asset Id to receive as payment for the NFT fixed_price
ask price duration
listing duration time in blocks from now Caller must be the token owner
Namespace
Type
Set the FeeTo
account This operation requires root access
Namespace
Type
Update fixed price for a single token sale
listing_id
id of the fixed price listing new_price
new fixed price Caller must be the token owner
Namespace
Type
The pallet id for the tx fee pot
Namespace
Type
Block numbers where listings will close. Value is true
if at block number listing_id
is scheduled to close.
Namespace
Type
NFT sale/auction listings keyed by listing id
Namespace
Type
Winning bids on open listings.
Namespace
Type
The next available listing Id
Namespace
Type
The next available marketplace id
Namespace
Type
The next available offer_id
Namespace
Type
Map from offer_id to the information related to the offer
Namespace
Type
Map from collection to any open listings
Namespace
Type
Map from marketplace account_id to royalties schedule
Namespace
Type
Maps from token_id to a vector of offer_ids on that token
Namespace
Type
An auction has closed without selling
Namespace
Type
An auction has opened
Namespace
Type
An auction has sold
Namespace
Type
A new highest bid was placed
Namespace
Type
The network fee receiver address has been updated
Namespace
Type
A fixed price sale has closed without selling
Namespace
Type
A fixed price sale has completed
Namespace
Type
A fixed price sale has been listed
Namespace
Type
A fixed price sale has had its price updated
Namespace
Type
An account has been registered as a marketplace
Namespace
Type
An offer has been made on an NFT
Namespace
Type
An offer has been accepted
Namespace
Type
An offer has been cancelled
Namespace
Type
Auction bid was lower than reserve or current highest bid
Namespace
The metadata path is invalid (non-utf8 or empty)
Namespace
No offer exists for the given OfferId
Namespace
The caller owns the token and can't make an offer
Namespace
The account_id hasn't been registered as a marketplace
Namespace
The maximum number of offers on this token has been reached
Namespace
Selling tokens from different collection is not allowed
Namespace
No more Ids are available, they've been exhausted
Namespace
The collection does not exist
Namespace
The caller is not the specified buyer
Namespace
Origin is not the collection owner and is not permitted to perform the operation
Namespace
The token is not listed for auction sale
Namespace
The token is not listed for fixed price sale
Namespace
The token does not exist
Namespace
The caller is not the seller of the NFT
Namespace
Origin does not own the NFT
Namespace
Total royalties would exceed 100% of sale or an empty vec is supplied
Namespace
Cannot operate on a listed NFT
Namespace
The token is not listed for sale
Namespace
Cannot make an offer on a token up for auction
Namespace
Offer amount needs to be greater than 0
Namespace
The default account which collects network fees from marketplace sales
Namespace
Type
Default auction / sale length in blocks
Namespace
Type
This pallet's Id, used for deriving a sovereign account ID
Namespace
Type
The NFI (Non-Fungible Intelligence) pallet allows for enabling NFI compatibility on new or existing collections. Once enabled, when an NFI-compatible NFT/SFT is minted, our trusted relayer will automatically generate the NFI data, storing the resulting NFIData on-chain.
Currently disabled on TRN mainnet.
Enables NFI compatibility on a collection. Caller must be the collection owner
Namespace
Type
Users can manually request NFI data if it does not already exist on a token. This can be used to manually request data for pre-existing tokens in a collection that has had nfi enabled Caller must be either the token owner or the collection owner Note. the mint fee will need to be paid for any manual request
Namespace:
Type:
Submit NFI data to the chain. Caller must be the registered relayer. NFI must be enabled for the collection
Namespace:
Type:
Set the NFI mint fee which is paid per token by the minter. Setting fee_details to None removes the mint fee
Namespace:
Type:
Set the relayer address. This address is able to submit the NFI data back to the chain. Caller must be sudo
Namespace:
Type:
Set the 'FeeTo' account. Caller must be sudo
Namespace:
Type:
Stores the permission enabled relayer account
Namespace:
Type:
Stores the extra mint fee that is charged for NFI enabled tokens
Namespace:
Type:
Stores the NFI Data linked to a token
Namespace:
Type:
Whether or not NFI is enabled for a collection
Namespace:
Type:
The Fee To address that collects network fees
Namespace:
Type:
Request for new NFI data creation
Namespace:
Type:
A new NFI storage item has been set
Namespace:
Type:
NFI storage has been removed for a token
Namespace:
Type:
New fee details have been set
Namespace:
Type:
The network fee receiver address has been updated
Namespace:
Type:
Additional mint fee has been paid to the receiver address
Namespace:
Type:
NFI compatibility enabled for a collection
Namespace:
Type:
A new relayer has been set
Namespace:
Type:
The mint fee must be a valid integer above 0
Namespace:
NFI storage is not enabled for this collection
Namespace:
The caller is not the relayer and does not have permission to perform this action
Namespace:
The caller is not the collection owner and does not have permission to perform this action
Namespace:
The caller is not the token owner and does not have permission to perform this action
Namespace:
The token does not exist
Namespace:
Percentage of sale price to charge for network fees
Namespace:
Type:
Maximum length of data stored per token
Namespace:
Type:
Burn a token 🔥
Caller must be the token owner
Namespace
Type
Bridged collections from Ethereum will initially lack an owner. These collections will be assigned to the pallet. This allows for claiming those collections assuming they were assigned to the pallet
Namespace
Type
Create a new collection Additional tokens can be minted via mint_additional
name
- the name of the collection initial_issuance
- number of tokens to mint now max_issuance
- maximum number of tokens allowed in collection token_owner
- the token owner, defaults to the caller metadata_scheme
- The off-chain metadata referencing scheme for tokens in this royalties_schedule
- defacto royalties plan for secondary sales, this will apply to all tokens in the collection by default.
Namespace
Type
Mint tokens for an existing collection
collection_id
- the collection to mint tokens in quantity
- how many tokens to mint token_owner
- the token owner, defaults to the caller if unspecified Caller must be the collection owner
----------- Weight is O(N) where N is quantity
Namespace
Type
Set the base URI of a collection Caller must be the current collection owner
Namespace
Type
Set the max issuance of a collection Caller must be the current collection owner
Namespace
Type
Namespace
Type
Set the name of a collection Caller must be the current collection owner
Namespace
Type
Set the owner of a collection Caller must be the current collection owner
Namespace
Type
Set the royalties schedule of a collection Caller must be the current collection owner
Namespace
Type
Namespace
Type
Transfer ownership of an NFT Caller must be the token owner
Namespace
Type
Map from collection to its information
Namespace
Type
The next available incrementing collection id
Namespace
Type
Map from collection to its public minting information
Namespace
Type
Map from a token to lock status if any
Namespace
Type
Base URI was set
Namespace
Type
Token(s) were bridged
Namespace
Type
A token was burned
Namespace
Type
Collection has been claimed
Namespace
Type
A new collection of tokens was created
Namespace
Type
Max issuance was set
Namespace
Type
Token(s) were minted
Namespace
Type
Payment was made to cover a public mint
Namespace
Type
A mint price was set for a collection
Namespace
Type
Name was set
Namespace
Type
A new owner was set
Namespace
Type
Public minting was enabled/disabled for a collection
Namespace
Type
Royalties schedule was set
Namespace
Type
A token was transferred
Namespace
Type
Attemped to mint a token that was bridged from a different chain
Namespace
Token(s) blocked from minting during the bridging process
Namespace
Cannot claim already claimed collections
Namespace
Total issuance of collection must be zero to add xls20 compatibility
Namespace
Given collection name is invalid (invalid utf-8, too long, empty)
Namespace
Initial issuance on XLS-20 compatible collections must be zero
Namespace
Max issuance needs to be greater than 0 and initial_issuance Cannot exceed MaxTokensPerCollection
Namespace
The metadata path is invalid (non-utf8 or empty)
Namespace
The caller can not be the new owner
Namespace
The max issuance has already been set and can't be changed
Namespace
The collection max issuance has been reached and no more tokens can be minted
Namespace
The quantity exceeds the max tokens per mint limit
Namespace
No more Ids are available, they've been exhausted
Namespace
The collection does not exist
Namespace
Origin is not the collection owner and is not permitted to perform the operation
Namespace
The token does not exist
Namespace
Origin does not own the NFT
Namespace
This collection has not allowed public minting
Namespace
Total royalties would exceed 100% of sale or an empty vec is supplied
Namespace
The number of tokens have exceeded the max tokens allowed
Namespace
Cannot operate on a listed NFT
Namespace
This pallet's Id, used for deriving a sovereign account ID
Namespace
Type
The maximum length of a collection name, stored on-chain
Namespace
Type
ownedTokens
Get all NFTs owned by an account
Interface
JSON
tokenUri
Get the URI of a token
Interface
JSON
Withdraw blocked tokens, must be called by the destination defined in BlockedTokens
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
The next available BlockedMintId
Namespace
Type
Namespace
Type
The NFT-peg contract address was set
Namespace
Type
Bridged ERC721 tokens were unable to be minted due to collection limit being reached
Namespace
Type
An ERC721 deposit was made
Namespace
Type
Bridged ERC721 tokens were minted
Namespace
Type
An ERC721 withdraw was made
Namespace
Type
Send more addresses than are allowed
Namespace
Sent more tokens than are allowed
Namespace
The length of the given vec exceeds the maximal allowed length limit
Namespace
The abi data passed in could not be decoded
Namespace
The prefix uint in the abi encoded data was invalid
Namespace
No blocked tokens for the given id
Namespace
No collection info exists
Namespace
No mapped token was stored for bridging the token back to the bridged chain
Namespace
Tried to bridge a token that originates from Root, which is not yet supported
Namespace
Blocked tokens can only be reclaimed by the destination address
Namespace
The state sync decoding feature is not implemented
Namespace
Multiple tokens were passed from contract, but amounts were unqeual per each array
Namespace
Namespace
Type
Note: There may be an additional charge for NFTs minted with NFI enabled. See the section below. 0.5% of the mint fee is sent to the Vortex for redistribution to network participants.
A vector of reports of the same kind that happened at the same time slot.
Namespace
Type
The primary structure that holds all offence records keyed by report identifiers.
Namespace
Type
Enumerates all reports of a kind along with the time they happened.
All reports are sorted by the time of offence.
Note that the actual type of this mapping is Vec<u8>
, this is because values of different types are not supported at the moment so we are doing the manual serialization.
Namespace
Type
There is an offence reported of the given kind
happened at the session_index
and (kind-specific) time slot. This event is not deposited for duplicate slashes. [kind, timeslot].
Namespace
Type
Send a call through a recovered account.
The dispatch origin for this call must be Signed and registered to be able to make calls on behalf of the recovered account.
Parameters:
account
: The recovered account you want to make a call on-behalf-of.
call
: The call you want to make with the recovered account.
Namespace
Type
Cancel the ability to use as_recovered
for account
.
The dispatch origin for this call must be Signed and registered to be able to make calls on behalf of the recovered account.
Parameters:
account
: The recovered account you are able to call on-behalf-of.
Namespace
Type
Allow a successful rescuer to claim their recovered account.
The dispatch origin for this call must be Signed and must be a "rescuer" who has successfully completed the account recovery process: collected threshold
or more vouches, waited delay_period
blocks since initiation.
Parameters:
account
: The lost account that you want to claim has been successfully recovered by you.
Namespace
Type
As the controller of a recoverable account, close an active recovery process for your account.
Payment: By calling this function, the recoverable account will receive the recovery deposit RecoveryDeposit
placed by the rescuer.
The dispatch origin for this call must be Signed and must be a recoverable account with an active recovery process for it.
Parameters:
rescuer
: The account trying to rescue this recoverable account.
Namespace
Type
Create a recovery configuration for your account. This makes your account recoverable.
Payment: ConfigDepositBase
+ FriendDepositFactor
* #_of_friends balance will be reserved for storing the recovery configuration. This deposit is returned in full when the user calls remove_recovery
.
The dispatch origin for this call must be Signed.
Parameters:
friends
: A list of friends you trust to vouch for recovery attempts. Should be ordered and contain no duplicate values.
threshold
: The number of friends that must vouch for a recovery attempt before the account can be recovered. Should be less than or equal to the length of the list of friends.
delay_period
: The number of blocks after a recovery attempt is initialized that needs to pass before the account can be recovered.
Namespace
Type
Initiate the process for recovering a recoverable account.
Payment: RecoveryDeposit
balance will be reserved for initiating the recovery process. This deposit will always be repatriated to the account trying to be recovered. See close_recovery
.
The dispatch origin for this call must be Signed.
Parameters:
account
: The lost account that you want to recover. This account needs to be recoverable (i.e. have a recovery configuration).
Namespace
Type
Remove the recovery process for your account. Recovered accounts are still accessible.
Note: The user must make sure to call close_recovery
on all active recovery attempts before calling this function else it will fail.
Payment: By calling this function the recoverable account will unreserve their recovery configuration deposit. (ConfigDepositBase
+ FriendDepositFactor
* #_of_friends)
The dispatch origin for this call must be Signed and must be a recoverable account (i.e. has a recovery configuration).
Namespace
Type
Allow ROOT to bypass the recovery process and set an a rescuer account for a lost account directly.
The dispatch origin for this call must be ROOT.
Parameters:
lost
: The "lost account" to be recovered.
rescuer
: The "rescuer account" which can call as the lost account.
Namespace
Type
Allow a "friend" of a recoverable account to vouch for an active recovery process for that account.
The dispatch origin for this call must be Signed and must be a "friend" for the recoverable account.
Parameters:
lost
: The lost account that you want to recover.
rescuer
: The account trying to rescue the lost account that you want to vouch for.
The combination of these two parameters must point to an active recovery process.
Namespace
Type
Active recovery attempts.
First account is the account to be recovered, and the second account is the user trying to recover the account.
Namespace
Type
The list of allowed proxy accounts.
Map from the user who can access it to the recovered account.
Namespace
Type
The set of recoverable accounts and their recovery configuration.
Namespace
Type
Lost account has been successfully recovered by the rescuer account.
Namespace
Type
A recovery process for lost account by rescuer account has been closed.
Namespace
Type
A recovery process has been set up for an account.
Namespace
Type
A recovery process has been initiated for lost account by rescuer account.
Namespace
Type
A recovery process has been removed for an account.
Namespace
Type
A recovery process for a lost account by rescuer account has been vouched for by the sender.
Namespace
Type
This account is already set up for recovery
Namespace
This account is already set up for recovery
Namespace
A recovery process has already started for this account
Namespace
This user has already vouched for this recovery
Namespace
Some internal state is broken.
Namespace
The friend must wait until the delay period to vouch for this recovery
Namespace
Friends list must be less than max friends
Namespace
User is not allowed to make a call on behalf of this account
Namespace
Friends list must be greater than zero and threshold
Namespace
This account is not a friend who can vouch
Namespace
This account is not set up for recovery
Namespace
Friends list must be sorted and free of duplicates
Namespace
A recovery process has not started for this rescuer
Namespace
There are still active recovery attempts that need to be closed
Namespace
The threshold for recovering this account has not been met
Namespace
Threshold must be greater than zero
Namespace
The base amount of currency needed to reserve for creating a recovery configuration.
This is held for an additional storage item whose value size is 2 + sizeof(BlockNumber, Balance)
bytes.
Namespace
Type
The amount of currency needed per additional user when creating a recovery configuration.
This is held for adding sizeof(AccountId)
bytes more into a pre-existing storage value.
Namespace
Type
The maximum amount of friends allowed in a recovery configuration.
NOTE: The threshold programmed in this Pallet uses u16, so it does not make sense to have a limit here greater than u16::MAX. But also, that is a lot more than you should probably set this value to anyway.
Namespace
Type
The base amount of currency needed to reserve for starting a recovery.
This is primarily held for deterring malicious recovery attempts, and should have a value large enough that a bad actor would choose not to place this deposit. It also acts to fund additional storage item whose value size is sizeof(BlockNumber, Balance + T * AccountId)
bytes. Where T is a configurable threshold.
Namespace
Type
Register a proxy account for the sender that is able to make calls on its behalf.
The dispatch origin for this call must be Signed.
Parameters:
proxy
: The account that the caller
would like to make a proxy.
proxy_type
: The permissions allowed for this proxy account.
delay
: The announcement period required of the initial proxy. Will generally be zero.
Namespace
Type
Publish the hash of a proxy-call that will be made in the future.
This must be called some number of blocks before the corresponding proxy
is attempted if the delay associated with the proxy relationship is greater than zero.
No more than MaxPending
announcements may be made at any one time.
This will take a deposit of AnnouncementDepositFactor
as well as AnnouncementDepositBase
if there are no other pending announcements.
The dispatch origin for this call must be Signed and a proxy of real
.
Parameters:
real
: The account that the proxy will make a call on behalf of.
call_hash
: The hash of the call to be made by the real
account.
Namespace
Type
Spawn a fresh new account that is guaranteed to be otherwise inaccessible, and initialize it with a proxy of proxy_type
for origin
sender.
Requires a Signed
origin.
proxy_type
: The type of the proxy that the sender will be registered as over the new account. This will almost always be the most permissive ProxyType
possible to allow for maximum flexibility.
index
: A disambiguation index, in case this is called multiple times in the same transaction (e.g. with utility::batch
). Unless you're using batch
you probably just want to use 0
.
delay
: The announcement period required of the initial proxy. Will generally be zero.
Fails with Duplicate
if this has already been called in this transaction, from the same sender, with the same parameters.
Fails if there are insufficient funds to pay for deposit.
Namespace
Type
Removes a previously spawned pure proxy.
WARNING: All access to this account will be lost. Any funds held in it will be inaccessible.
Requires a Signed
origin and the sender account must have been created by a call to pure
with corresponding parameters.
spawner
: The account that was originally called pure
to create this account.
index
: The disambiguation index originally passed to pure
. Probably 0
.
proxy_type
: The proxy type originally passed to pure
.
height
: The height of the chain when the call to pure
was processed.
ext_index
: The extrinsic index in which the call to pure
was processed.
Fails with NoPermission
in case the caller is not a previously created pure account whose pure
call has corresponding parameters.
Namespace
Type
Dispatch the given call
from an account that the sender is authorised for through add_proxy
.
Removes any corresponding announcement(s).
The dispatch origin for this call must be Signed.
Parameters:
real
: The account that the proxy will make a call on behalf of.
force_proxy_type
: Specify the exact proxy type to be used and checked for this call.
call
: The call to be made by the real
account.
Namespace
Type
Dispatch the given call
from an account that the sender is authorized for through add_proxy
.
Removes any corresponding announcement(s).
The dispatch origin for this call must be Signed.
Parameters:
real
: The account that the proxy will make a call on behalf of.
force_proxy_type
: Specify the exact proxy type to be used and checked for this call.
call
: The call to be made by the real
account.
Namespace
Type
Remove the given announcement of a delegate.
May be called by a target (proxied) account to remove a call that one of their delegates (delegate
) has announced they want to execute. The deposit is returned.
The dispatch origin for this call must be Signed.
Parameters:
delegate
: The account that previously announced the call.
call_hash
: The hash of the call to be made.
Namespace
Type
Remove a given announcement.
May be called by a proxy account to remove a call they previously announced and return the deposit.
The dispatch origin for this call must be Signed.
Parameters:
real
: The account that the proxy will make a call on behalf of.
call_hash
: The hash of the call to be made by the real
account.
Namespace
Type
Unregister all proxy accounts for the sender.
The dispatch origin for this call must be Signed.
WARNING: This may be called on accounts created by pure
, however, if done, then the unreserved fees will be inaccessible. All access to this account will be lost.
Namespace
Type
Unregister a proxy account for the sender.
The dispatch origin for this call must be Signed.
Parameters:
proxy
: The account that the caller
would like to remove as a proxy.
proxy_type
: The permissions currently enabled for the removed proxy account.
Namespace
Type
The announcements made by the proxy (key).
Namespace
Type
The set of account proxies. Maps the account which has delegated to the accounts which are being delegated to, together with the amount held on deposit.
Namespace
Type
An announcement was placed to make a call in the future.
Namespace
Type
A proxy was added.
Namespace
Type
A proxy was executed correctly, with the given.
Namespace
Type
A proxy was removed.
Namespace
Type
A pure account has been created by new proxy with given disambiguation index and proxy type.
Namespace
Type
Account is already a proxy.
Namespace
Call may not be made by proxy because it may escalate its privileges.
Namespace
Cannot add self as proxy.
Namespace
Proxy registration not found.
Namespace
Sender is not a proxy of the account to be proxied.
Namespace
There are too many proxies registered or too many announcements pending.
Namespace
Announcement, if made at all, was made too recently.
Namespace
A call which is incompatible with the proxy type's filter was attempted.
Namespace
The base amount of currency needed to reserve for creating an announcement.
This is held when a new storage item holding a Balance
is created (typically 16 bytes).
Namespace
Type
The amount of currency needed per announcement made.
This is held for adding an AccountId
, Hash
and BlockNumber
(typically 68 bytes) into a pre-existing storage value.
Namespace
Type
The maximum amount of time-delayed announcements that are allowed to be pending.
Namespace
Type
The maximum amount of proxies allowed for a single account.
Namespace
Type
The base amount of currency needed to reserve for creating a proxy.
This is held for an additional storage item whose value size is sizeof(Balance)
bytes and whose key size is sizeof(AccountId)
bytes.
Namespace
Type
The amount of currency needed per proxy added.
This is held for adding 32 bytes plus an instance of ProxyType
more into a pre-existing storage value. Thus, when configuring ProxyDepositFactor
one should take into account 32 + proxy_type.encode().len()
bytes of data.
Namespace
Type
Register a preimage on-chain.
If the preimage was previously requested, no fees or deposits are taken for providing the preimage. Otherwise, a deposit is taken proportional to the size of the preimage.
Namespace
Type
Request a preimage be uploaded to the chain without paying any fees or deposits.
If the preimage requests has already been provided on-chain, we unreserve any deposit a user may have paid, and take the control of the preimage out of their hands.
Namespace
Type
Clear an unrequested preimage from the runtime storage.
Namespace
Type
Clear a previously made request for a preimage.
IMPORTANT: This must not be called onhash
more times thanrequest_preimage
.
Namespace
Type
The preimages stored by this pallet.
Namespace
Type
The request status of a given hash.
Namespace
Type
A preimage has ben cleared.
Namespace
Type
A preimage has been noted.
Namespace
Type
A preimage has been requested.
Namespace
Type
Preimage has already been noted on-chain.
Namespace
The user is not authorized to perform this action.
Namespace
The preimage cannot be removed since it has not yet been noted.
Namespace
The preimage request cannot be removed since no outstanding requests exist.
Namespace
A preimage may not be removed when there are outstanding requests.
Namespace
Preimage is too large to store on-chain.
Namespace
undefined
Cancel an anonymously scheduled task.
Namespace
Type
Cancel a named scheduled task.
Namespace
Type
Anonymously schedule a task.
Namespace
Type
Anonymously schedule a task after a delay.
Namespace
Type
Schedule a named task.
Namespace
Type
Schedule a named task after a delay.
Namespace
Type
Items to be executed, indexed by the block number that they should be executed on.
Namespace
Type
Lookup from identity to the block number and index of the task.
Namespace
Type
The call for the provided hash was not found so the task has been aborted.
Namespace
Type
Canceled some task.
Namespace
Type
Dispatched some task.
Namespace
Type
Scheduled some task.
Namespace
Type
Failed to schedule a call
Namespace
Cannot find the scheduled call.
Namespace
Reschedule failed because it does not change scheduled time.
Namespace
Given target block number is in the past.
Namespace
The maximum weight that may be scheduled per block for any dispatchables of less priority than schedule::HARD_DEADLINE
.
Namespace
Type
The maximum number of scheduled calls in the queue for a single block. Not strictly enforced, but used for weight estimation.
Namespace
Type
Removes any session key(s) of the function caller.
This doesn't take effect until the next session.
The dispatch origin of this function must be Signed and the account must be either be convertible to a validator ID using the chain's typical addressing system (this usually means being a controller account) or directly convertible into a validator ID (which usually means being a stash account).
Namespace
Type
Sets the session key(s) of the function caller to keys
. Allows an account to set its session key prior to becoming a validator. This doesn't take effect until the next session.
The dispatch origin of this function must be signed.
Namespace
Type
Current index of the session.
Namespace
Type
Indices of disabled validators.
The vec is always kept sorted so that we can find whether a given validator is disabled using binary search. It gets cleared when on_session_ending
returns a new set of identities.
Namespace
Type
The owner of a key. The key is the KeyTypeId
+ the encoded key.
Namespace
Type
The next session keys for a validator.
Namespace
Type
True if the underlying economic identities or weighting behind the validators has changed in the queued validator set.
Namespace
Type
The queued keys for the next session. When the next session begins, these keys will be used to determine the validator's session keys.
Namespace
Type
The current set of validators.
Namespace
Type
New session has happened. Note that the argument is the session index, not the block number as the type might suggest.
Namespace
Type
Registered duplicate key.
Namespace
Invalid ownership proof.
Namespace
Key setting account is not live, so it's impossible to associate keys.
Namespace
No associated validator ID for account.
Namespace
No keys are associated with this account.
Namespace
undefined
Authenticates the current sudo key and sets the given AccountId (new
) as the new sudo key.
The dispatch origin for this call must be Signed.
Namespace
Type
Authenticates the sudo key and dispatches a function call with Root
origin.
The dispatch origin for this call must be Signed.
Namespace
Type
Authenticates the sudo key and dispatches a function call with Signed
origin from a given account.
The dispatch origin for this call must be Signed.
Namespace
Type
Authenticates the sudo key and dispatches a function call with Root
origin. This function does not check the weight of the call, and instead allows the Sudo user to specify the weight of the call.
The dispatch origin for this call must be Signed.
Namespace
Type
The AccountId
of the sudo key.
Namespace
Type
The [sudoer] just switched identity; the old key is supplied if one existed.
Namespace
Type
A sudo just took place. [result]
Namespace
Type
A sudo just took place. [result]
Namespace
Type
Sender must be the Sudo account
Namespace
undefined
Burn a token 🔥
Caller must be the token owner
Namespace
Type
Create a new collection to group multiple semi-fungible tokens Tokens can be created within the collection by calling create_token
collection_name
- the name of the collection collection_owner
- the collection owner, defaults to the caller metadata_scheme
- The off-chain metadata referencing scheme for tokens in this royalties_schedule
- defacto royalties plan for secondary sales, this will apply to all tokens in the collection by default.
The collectionUuid used to store the SFT CollectionInfo is retrieved from the NFT pallet. This is so that CollectionUuids are unique across all collections, regardless of if they are SFT or NFT collections.
Namespace
Type
Create additional tokens for an existing collection These tokens act similar to tokens within an ERC1155 contract Each token has individual issuance, max_issuance,
Namespace
Type
Mints some balances into some serial numbers for an account This acts as a batch mint function and allows for multiple serial numbers and quantities to be passed in simultaneously. Must be called by the collection owner
collection_id
- the SFT collection to mint into serial_numbers
- A list of serial numbers to mint into quantities
- A list of quantities to mint into each serial number token_owner
- The owner of the tokens, defaults to the caller
Namespace
Type
Set the base URI of a collection (MetadataScheme) Caller must be the current collection owner
Namespace
Type
Set the max issuance of a collection Caller must be the current collection owner
Namespace
Type
Namespace
Type
Set the name of a collection Caller must be the current collection owner
Namespace
Type
Set the owner of a collection Caller must be the current collection owner
Namespace
Type
Set the royalties schedule of a collection Caller must be the current collection owner
Namespace
Type
Namespace
Type
Transfer ownership of an SFT Caller must be the token owner
Namespace
Type
Map from collection to its public minting information
Namespace
Type
Map from collection to its information
Namespace
Type
Map from token to its token information, including ownership information
Namespace
Type
Base URI was set
Namespace
Type
A token was burned
Namespace
Type
A new collection of tokens was created
Namespace
Type
Max issuance was set
Namespace
Type
Token(s) were minted
Namespace
Type
Payment was made to cover a public mint
Namespace
Type
A mint price was set for a collection
Namespace
Type
Name was set
Namespace
Type
A new owner was set
Namespace
Type
Public minting was enabled/disabled for a collection
Namespace
Type
Royalties schedule was set
Namespace
Type
A new token was created within a collection
Namespace
Type
A token was transferred
Namespace
Type
The user does not own enough of this token to perform the operation
Namespace
Max issuance needs to be greater than 0 and initial_issuance Cannot exceed MaxTokensPerCollection
Namespace
Caller can not be the new owner
Namespace
The specified quantity must be greater than 0
Namespace
The max issuance has already been set and can't be changed
Namespace
The collection max issuance has been reached and no more tokens can be minted
Namespace
The max amount of owners per token has been reached
Namespace
Given collection or token name is invalid (invalid utf-8, empty)
Namespace
The collection does not exist
Namespace
Origin is not the collection owner and is not permitted to perform the operation
Namespace
The token does not exist
Namespace
The operation would cause a numeric overflow
Namespace
This collection has not allowed public minting
Namespace
Total royalties would exceed 100% of sale or an empty vec is supplied
Namespace
Max unique owners that can own an SFT token
Namespace
Type
Max tokens that can be minted in one transaction
Namespace
Type
Max tokens that a collection can contain
Namespace
Type
This pallet's Id, used for deriving a sovereign account ID
Namespace
Type
The maximum length of a collection or token name, stored on-chain
Namespace
Type
A dispatch that will fill the block weight up to the given ratio.
Namespace
Type
Kill all storage items with a key that starts with the given prefix.
NOTE: We rely on the Root origin to provide us the number of subkeys under the prefix we are removing to accurately calculate the weight of this function.
Namespace
Type
Kill some items from storage.
Namespace
Type
Make some on-chain remark.
Namespace
Type
Make some on-chain remark and emit event.
Namespace
Type
Set the new runtime code.
Namespace
Type
Set the new runtime code without doing any checks of the given code
.
Namespace
Type
Set the number of pages in the WebAssembly environment's heap.
Namespace
Type
Set some items of storage.
Namespace
Type
The full account information for a particular account ID.
Namespace
Type
Total length (in bytes) for all extrinsics put together, for the current block.
Namespace
Type
Map of block numbers to block hashes.
Namespace
Type
The current weight for the block.
Namespace
Type
Digest of the current block, also part of the block header.
Namespace
Type
The number of events in the Events<T>
list.
Namespace
Type
Events deposited for the current block.
NOTE: The item is unbound and should therefore never be read on chain. It could otherwise inflate the PoV size of a block.
Events have a large in-memory size. Box the events to not go out-of-memory just in case someone still reads them from within the runtime.
Namespace
Type
Mapping between a topic (represented by T::Hash) and a vector of indexes of events in the <Events<T>>
list.
All topic vectors have deterministic storage locations depending on the topic. This allows light-clients to leverage the changes trie storage tracking mechanism and in case of changes fetch the list of events of interest.
The value has the type (T::BlockNumber, EventIndex)
because if we used only just the EventIndex
then in case if the topic has the same contents on the next block no notification will be triggered thus the event might be lost.
Namespace
Type
The execution phase of the block.
Namespace
Type
Total extrinsics count for the current block.
Namespace
Type
Extrinsics data for the current block (maps an extrinsic's index to its data).
Namespace
Type
Stores the spec_version
and spec_name
of when the last runtime upgrade happened.
Namespace
Type
The current block number being processed. Set by execute_block
.
Namespace
Type
Hash of the previous block.
Namespace
Type
True if we have upgraded so that AccountInfo contains three types of RefCount
. False (default) if not.
Namespace
Type
True if we have upgraded so that type RefCount
is u32
. False (default) if not.
Namespace
Type
:code
was updated.
Namespace
Type
An extrinsic failed.
Namespace
Type
An extrinsic completed successfully.
Namespace
Type
An account was reaped.
Namespace
Type
A new account was created.
Namespace
Type
On on-chain remark happened.
Namespace
Type
The origin filter prevent the call to be dispatched.
Namespace
Failed to extract the runtime version from the new runtime.
Either calling Core_version
or decoding RuntimeVersion
failed.
Namespace
The name of specification does not match between the current runtime and the new runtime.
Namespace
Suicide called when the account has non-default composite data.
Namespace
There is a non-zero reference count preventing the account from being purged.
Namespace
The specification version is not allowed to decrease between the current runtime and the new runtime.
Namespace
Maximum number of block number to block hash mappings to keep (oldest pruned first).
Namespace
Type
The maximum length of a block (in bytes).
Namespace
Type
Block & extrinsics weights: base values and limits.
Namespace
Type
The weight of runtime database operations the runtime can invoke.
Namespace
Type
The designated SS58 prefix of this chain.
This replaces the "ss58Format" property declared in the chain spec. Reason is that the runtime should know about the prefix in order to make use of it as an identifier of the chain.
Namespace
Type
Get the chain's current version.
Namespace
Type
accountNextIndex
Retrieves the next accountIndex as available on the node
Interface
JSON
addLogFilter
Adds the supplied directives to the current log filter
:::info This method is only active with appropriate flags :::
Interface
JSON
addReservedPeer
Adds a reserved peer
:::info This method is only active with appropriate flags :::
Interface
JSON
chain
Retrieves the chain
Interface
JSON
chainType
Retrieves the chain type
Interface
JSON
dryRun
Dry run an extrinsic at a given block
:::info This method is only active with appropriate flags :::
Interface
JSON
health
Return health status of the node
Interface
JSON
localListenAddresses
The addresses include a trailing /p2p/ with the local PeerId, and are thus suitable to be passed to addReservedPeer or as a bootnode address for example
Interface
JSON
localPeerId
Returns the base58-encoded PeerId of the node
Interface
JSON
name
Retrieves the node name
Interface
JSON
nodeRoles
Returns the roles the node is running as
Interface
JSON
peers
Returns the currently connected peers
:::info This method is only active with appropriate flags :::
Interface
JSON
properties
Get a custom set of properties as a JSON object, defined in the chain spec
Interface
JSON
removeReservedPeer
Remove a reserved peer
:::info This method is only active with appropriate flags :::
Interface
JSON
reservedPeers
Returns the list of reserved peers
Interface
JSON
resetLogFilter
Resets the log filter to Substrate defaults
:::info This method is only active with appropriate flags :::
Interface
JSON
syncState
Returns the state of the syncing of the node
Interface
JSON
version
Retrieves the version of the node
Interface
JSON
Take the origin account as a stash and lock up value
of its balance. controller
will be the account that controls it.
value
must be more than the minimum_balance
specified by T::Currency
.
The dispatch origin for this call must be Signed by the stash account.
Emits Bonded
.
Namespace
Type
Add some extra amount that have appeared in the stash free_balance
into the balance up for staking.
The dispatch origin for this call must be Signed by the stash, not the controller.
Use this if there are additional funds in your stash account that you wish to bond. Unlike bond
or unbond
this function does not impose any limitation on the amount that can be added.
Emits Bonded
.
Namespace
Type
Cancel enactment of a deferred slash.
Can be called by the T::SlashCancelOrigin
.
Parameters: era and indices of the slashes for that era to kill.
Namespace
Type
Declare no desire to either validate or nominate.
Effects will be felt at the beginning of the next era.
The dispatch origin for this call must be Signed by the controller, not the stash.
Namespace
Type
Declare a controller
to stop participating as either a validator or nominator.
Effects will be felt at the beginning of the next era.
The dispatch origin for this call must be Signed, but can be called by anyone.
If the caller is the same as the controller being targeted, then no further checks are enforced, and this function behaves just like chill
.
If the caller is different than the controller being targeted, the following conditions must be met:
controller
must belong to a nominator who has become non-decodable,
Or:
A ChillThreshold
must be set and checked which defines how close to the max nominators or validators we must reach before users can start chilling one-another.
A MaxNominatorCount
and MaxValidatorCount
must be set which is used to determine how close we are to the threshold.
A MinNominatorBond
and MinValidatorBond
must be set and checked, which determines if this is a person that should be chilled because they have not met the threshold bond required.
This can be helpful if bond requirements are updated, and we need to remove old users who do not satisfy these requirements.
Namespace
Type
Force a validator to have at least the minimum commission. This will not affect a validator who already has a commission greater than or equal to the minimum. Any account can call this.
Namespace
Type
Force there to be a new era at the end of the next session. After this, it will be reset to normal (non-forced) behaviour.
The dispatch origin must be Root.
Warning: The election process starts multiple blocks before the end of the era. If this is called just before a new era is triggered, the election process may not have enough blocks to get a result.
Namespace
Type
Force there to be a new era at the end of sessions indefinitely.
The dispatch origin must be Root.
Warning: The election process starts multiple blocks before the end of the era. If this is called just before a new era is triggered, the election process may not have enough blocks to get a result.
Namespace
Type
Force there to be no new eras indefinitely.
The dispatch origin must be Root.
Warning: The election process starts multiple blocks before the end of the era. Thus the election process may be ongoing when this is called. In this case, the election will continue until the next era is triggered.
Namespace
Type
Force a current staker to become completely unstaked, immediately.
The dispatch origin must be Root.
Namespace
Type
Increments the ideal number of validators.
The dispatch origin must be Root.
Namespace
Type
Remove the given nominations from the calling validator.
Effects will be felt at the beginning of the next era.
The dispatch origin for this call must be Signed by the controller, not the stash.
who
: A list of nominator stash accounts who are nominating this validator which should no longer be nominating this validator.
Note: Making this call only makes sense if you first set the validator preferences to block any further nominations.
Namespace
Type
Declare the desire to nominate targets
for the origin controller.
Effects will be felt at the beginning of the next era.
The dispatch origin for this call must be Signed by the controller, not the stash.
Namespace
Type
Pay out all the stakers behind a single validator for a single era.
validator_stash
is the stash account of the validator. Their nominators, up to T::MaxNominatorRewardedPerValidator
, will also receive their rewards.
era
may be any era between [current_era - history_depth; current_era]
.
The origin of this call must be Signed. Any account can call this function, even if it is not one of the stakers.
Namespace
Type
Remove all data structures concerning a staker/stash once it is at a state where it can be considered dust
in the staking system. The requirements are:
the total_balance
of the stash is below existential deposit. 2. or, the ledger.total
of the stash is below existential deposit.
The former can happen in cases like a slash; the latter when a fully unbonded account is still receiving staking rewards in RewardDestination::Staked
.
It can be called by anyone, as long as stash
meets the above requirements.
Refunds the transaction fees upon successful execution.
Namespace
Type
Rebond a portion of the stash scheduled to be unlocked.
The dispatch origin must be signed by the controller.
Namespace
Type
Scale up the ideal number of validators by a factor.
The dispatch origin must be Root.
Namespace
Type
(Re-)set the controller of a stash.
Effects will be felt instantly (as soon as this function is completed successfully).
The dispatch origin for this call must be Signed by the stash, not the controller.
Namespace
Type
Set the validators who cannot be slashed (if any).
The dispatch origin must be Root.
Namespace
Type
(Re-)set the payment target for a controller.
Effects will be felt instantly (as soon as this function is completed successfully).
The dispatch origin for this call must be Signed by the controller, not the stash.
Namespace
Type
Update the various staking configurations .
min_nominator_bond
: The minimum active bond needed to be a nominator.
min_validator_bond
: The minimum active bond needed to be a validator.
max_nominator_count
: The max number of users who can be a nominator at once. When set to None
, no limit is enforced.
max_validator_count
: The max number of users who can be a validator at once. When set to None
, no limit is enforced.
chill_threshold
: The ratio of max_nominator_count
or max_validator_count
which should be filled in order for the chill_other
transaction to work.
min_commission
: The minimum amount of commission that each validators must maintain. This is checked only upon calling validate
. Existing validators are not affected.
RuntimeOrigin must be Root to call this function.
NOTE: Existing nominators and validators will not be affected by this update. to kick people under the new limits, chill_other
should be called.
Namespace
Type
Sets the ideal number of validators.
The dispatch origin must be Root.
Namespace
Type
Schedule a portion of the stash to be unlocked ready for transfer out after the bond period ends. If this leaves an amount actively bonded less than T::Currency::minimum_balance(), then it is increased to the full amount.
The dispatch origin for this call must be Signed by the controller, not the stash.
Once the unlock period is done, you can call withdraw_unbonded
to actually move the funds out of management ready for transfer.
No more than a limited number of unlocking chunks (see MaxUnlockingChunks
) can co-exists at the same time. In that case, [Call::withdraw_unbonded
] need to be called first to remove some of the chunks (if possible).
If a user encounters the InsufficientBond
error when calling this extrinsic, they should call chill
first in order to free up their bonded funds.
Emits Unbonded
.
See also [Call::withdraw_unbonded
].
Namespace
Type
Declare the desire to validate for the origin controller.
Effects will be felt at the beginning of the next era.
The dispatch origin for this call must be Signed by the controller, not the stash.
Namespace
Type
Remove any unlocked chunks from the unlocking
queue from our management.
This essentially frees up that balance to be used by the stash account to do whatever it wants.
The dispatch origin for this call must be Signed by the controller.
Emits Withdrawn
.
See also [Call::unbond
].
Namespace
Type
The active era information, it holds index and start.
The active era is the era being currently rewarded. Validator set of this era must be equal to [SessionInterface::validators
].
Namespace
Type
Map from all locked "stash" accounts to the controller account.
Namespace
Type
A mapping from still-bonded eras to the first session index of that era.
Must contains information for eras for the range: [active_era - bounding_duration; active_era]
Namespace
Type
The amount of currency given to reporters of a slash event which was canceled by extraordinary circumstances (e.g. governance).
Namespace
Type
The threshold for when users can start calling chill_other
for other validators / nominators. The threshold is compared to the actual number of validators / nominators (CountFor*
) in the system compared to the configured max (Max*Count
).
Namespace
Type
Counter for the related counted storage map
Namespace
Type
Counter for the related counted storage map
Namespace
Type
The current era index.
This is the latest planned era, depending on how the Session pallet queues the validator set, it might be active or not.
Namespace
Type
The last planned session scheduled by the session pallet.
This is basically in sync with the call to [pallet_session::SessionManager::new_session
].
Namespace
Type
Rewards for the last HISTORY_DEPTH
eras. If reward hasn't been set or has been removed then 0 reward is returned.
Namespace
Type
Exposure of validator at era.
This is keyed first by the era index to allow bulk deletion and then the stash account.
Is it removed after HISTORY_DEPTH
eras. If stakers hasn't been set or has been removed then empty exposure is returned.
Namespace
Type
Clipped Exposure of validator at era.
This is similar to [ErasStakers
] but number of nominators exposed is reduced to the T::MaxNominatorRewardedPerValidator
biggest stakers. Note: The field total
and own
of the exposure remains unchanged. This is used to limit the i/o cost for the nominator payout.
This is keyed fist by the era index to allow bulk deletion and then the stash account.
Is it removed after HISTORY_DEPTH
eras. If stakers hasn't been set or has been removed then empty exposure is returned.
Namespace
Type
The session index at which the era start for the last HISTORY_DEPTH
eras.
Note: This tracks the starting session (i.e. session index when era start being active) for the eras in [CurrentEra - HISTORY_DEPTH, CurrentEra]
.
Namespace
Type
The total amount staked for the last HISTORY_DEPTH
eras. If total hasn't been set or has been removed then 0 stake is returned.
Namespace
Type
Similar to ErasStakers
, this holds the preferences of validators.
This is keyed first by the era index to allow bulk deletion and then the stash account.
Is it removed after HISTORY_DEPTH
eras.
Namespace
Type
The total validator era payout for the last HISTORY_DEPTH
eras.
Eras that haven't finished yet or has been removed doesn't have reward.
Namespace
Type
Mode of era forcing.
Namespace
Type
Any validators that may never be slashed or forcibly kicked. It's a Vec since they're easy to initialize and the performance hit is minimal (we expect no more than four invulnerables) and restricted to testnets.
Namespace
Type
Map from all (unlocked) "controller" accounts to the info regarding the staking.
Namespace
Type
The maximum nominator count before we stop allowing new validators to join.
When this value is not set, no limits are enforced.
Namespace
Type
The maximum validator count before we stop allowing new validators to join.
When this value is not set, no limits are enforced.
Namespace
Type
The minimum amount of commission that validators can set.
If set to 0
, no limit exists.
Namespace
Type
Minimum number of staking participants before emergency conditions are imposed.
Namespace
Type
The minimum active bond to become and maintain the role of a nominator.
Namespace
Type
The minimum active bond to become and maintain the role of a validator.
Namespace
Type
The map from nominator stash key to their nomination preferences, namely the validators that they wish to support.
Note that the keys of this storage map might become non-decodable in case the [Config::MaxNominations
] configuration is decreased. In this rare case, these nominators are still existent in storage, their key is correct and retrievable (i.e. contains_key
indicates that they exist), but their value cannot be decoded. Therefore, the non-decodable nominators will effectively not-exist, until they re-submit their preferences such that it is within the bounds of the newly set Config::MaxNominations
.
This implies that ::iter_keys().count()
and ::iter().count()
might return different values for this map. Moreover, the main ::count()
is aligned with the former, namely the number of keys that exist.
Lastly, if any of the nominators become non-decodable, they can be chilled immediately via [Call::chill_other
] dispatchable by anyone.
Namespace
Type
All slashing events on nominators, mapped by era to the highest slash value of the era.
Namespace
Type
Indices of validators that have offended in the active era and whether they are currently disabled.
This value should be a superset of disabled validators since not all offences lead to the validator being disabled (if there was no slash). This is needed to track the percentage of validators that have offended in the current era, ensuring a new era is forced if OffendingValidatorsThreshold
is reached. The vec is always kept sorted so that we can find whether a given validator has previously offended using binary search. It gets cleared when the era ends.
Namespace
Type
Where the reward payment should be made. Keyed by stash.
Namespace
Type
Slashing spans for stash accounts.
Namespace
Type
The percentage of the slash that is distributed to reporters.
The rest of the slashed value is handled by the Slash
.
Namespace
Type
Records information about the maximum slash of a stash within a slashing span, as well as how much reward has been paid out.
Namespace
Type
True if network has been upgraded to this version. Storage version of the pallet.
This is set to v7.0.0 for new networks.
Namespace
Type
All unapplied slashes that are queued for later.
Namespace
Type
The ideal number of staking participants.
Namespace
Type
The map from (wannabe) validator stash key to the preferences of that validator.
Namespace
Type
All slashing events on validators, mapped by era to the highest slash proportion and slash value of the era.
Namespace
Type
An account has bonded this amount. [stash, amount]
NOTE: This event is only emitted when funds are bonded via a dispatchable. Notably, it will not be emitted for staking rewards when they are added to stake.
Namespace
Type
An account has stopped participating as either a validator or nominator.
Namespace
Type
The era payout has been set; the first balance is the validator-payout; the second is the remainder from the maximum amount of reward.
Namespace
Type
A nominator has been kicked from a validator.
Namespace
Type
An old slashing report from a prior era was discarded because it could not be processed.
Namespace
Type
The stakers' rewards are getting paid.
Namespace
Type
The nominator has been rewarded by this amount.
Namespace
Type
One staker (and potentially its nominators) has been slashed by the given amount.
Namespace
Type
A new set of stakers was elected.
Namespace
Type
The election failed. No new era is planned.
Namespace
Type
An account has unbonded this amount.
Namespace
Type
A validator has set their preferences.
Namespace
Type
An account has called withdraw_unbonded
and removed unbonding chunks worth Balance
from the unlocking queue.
Namespace
Type
Stash is already bonded.
Namespace
Rewards for this era have already been claimed for this validator.
Namespace
Controller is already paired.
Namespace
Internal state has become somehow corrupted and the operation cannot continue.
Namespace
A nomination target was supplied that was blocked or otherwise not a validator.
Namespace
Some bound is not met.
Namespace
The user has enough bond and thus cannot be chilled forcefully by an external person.
Namespace
Commission is too low. Must be at least MinCommission
.
Namespace
Duplicate index.
Namespace
Targets cannot be empty.
Namespace
Attempting to target a stash that still has funds.
Namespace
Incorrect previous history depth input provided.
Namespace
Incorrect number of slashing spans provided.
Namespace
Cannot have a validator or nominator role, with value less than the minimum defined by governance (see MinValidatorBond
and MinNominatorBond
). If unbonding is the intention, chill
first to remove one's role as validator/nominator.
Namespace
Invalid era to reward.
Namespace
Invalid number of nominations.
Namespace
Slash record index out of bounds.
Namespace
Can not schedule more unlock chunks.
Namespace
Not a controller account.
Namespace
Items are not sorted and unique.
Namespace
Not a stash account.
Namespace
Can not rebond without unlocking chunks.
Namespace
There are too many nominators in the system. Governance needs to adjust the staking settings to keep things safe for the runtime.
Namespace
Too many nomination targets supplied.
Namespace
There are too many validators in the system. Governance needs to adjust the staking settings to keep things safe for the runtime.
Namespace
Number of eras that staked funds must remain bonded for.
Namespace
Type
Number of eras to keep in history.
Following information is kept for eras in [current_era - HistoryDepth, current_era]
: ErasStakers
, ErasStakersClipped
, ErasValidatorPrefs
, ErasValidatorReward
, ErasRewardPoints
, ErasTotalStake
, ErasStartSessionIndex
, StakingLedger.claimed_rewards
.
Must be more than the number of eras delayed by session. I.e. active era must always be in history. I.e. active_era > current_era - history_depth
must be guaranteed.
If migrating an existing pallet from storage value to config value, this should be set to same value or greater as in storage.
Note: HistoryDepth
is used as the upper bound for the BoundedVec
item StakingLedger.claimed_rewards
. Setting this value lower than the existing value can lead to inconsistencies in the StakingLedger
and will need to be handled properly in a migration. The test reducing_history_depth_abrupt
shows this effect.
Namespace
Type
Maximum number of nominations per nominator.
Namespace
Type
The maximum number of nominators rewarded for each validator.
For each validator only the $MaxNominatorRewardedPerValidator
biggest stakers can claim their reward. This used to limit the i/o cost for the nominator payout.
Namespace
Type
The maximum number of unlocking
chunks a [StakingLedger
] can have. Effectively determines how many unique eras a staker may be unbonding in.
Note: MaxUnlockingChunks
is used as the upper bound for the BoundedVec
item StakingLedger.unlocking
. Setting this value lower than the existing value can lead to inconsistencies in the StakingLedger
and will need to be handled properly in a runtime migration. The test reducing_max_unlocking_chunks_abrupt
shows this effect.
Namespace
Type
Number of sessions per era.
Namespace
Type
Number of eras that slashes are deferred by, after computation.
This should be less than the bonding duration. Set to 0 if slashes should be applied immediately, without opportunity for intervention.
Namespace
Type
Set the current time.
This call should be invoked exactly once per block. It will panic at the finalization phase, if this call hasn't been invoked by that time.
The timestamp should be greater than the previous one by the amount specified by MinimumPeriod
.
The dispatch origin for this call must be Inherent
.
Namespace
Type
Did the timestamp get updated in this block?
Namespace
Type
Current time for the current block.
Namespace
Type
undefinedundefined## Constants
The minimum period between blocks. Beware that this is different to the expected period that the block production apparatus provides. Your chosen consensus system will generally work with this to determine a sensible block time. e.g. For Aura, it will be double this period on default settings.
Namespace
Type
Set approval for an account (or contract) to transfer any tokens from an SFT collection mapping(address => mapping(address => bool)) private _operatorApprovals;
Namespace
Type
Set approval for an account to transfer an amount of tokens on behalf of the caller Mapping from caller to spender and amount mapping(address => mapping(address => uint256)) private _allowances;
Namespace
Type
Removes an approval over an account and asset_id mapping(address => mapping(address => uint256)) private _allowances;
Namespace
Type
Set approval for a single NFT Mapping from token_id to operator clears approval on transfer mapping(uint256 => address) private _tokenApprovals;
Namespace
Type
Set approval for an account (or contract) to transfer any tokens from a collection mapping(address => mapping(address => bool)) private _operatorApprovals;
Namespace
Type
Public method which allows users to remove approvals on a token they own
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
undefined## Errors
Address is already approved
Namespace
There is no approval set for this token
Namespace
The caller is not approved for the requested amount
Namespace
The caller isn't approved for any amount
Namespace
The caller account can't be the same as the operator account
Namespace
The token doesn't exist
Namespace
The account is not the owner of the token
Namespace
The account is not the owner of the token or an approved account
Namespace
undefined
Namespace
Type
Namespace
Type
A transaction fee actual_fee
, of which tip
was added to the minimum inclusion fee, has been paid by who
.
Namespace
Type
undefined## Constants
A fee multiplier for Operational
extrinsics to compute "virtual tip" to boost their priority
This value is multiplied by the final_fee
to obtain a "virtual tip" that is later added to a tip component in regular priority
calculations. It means that a Normal
transaction can front-run a similarly sized Operational
extrinsic (with no tip), by including a tip value greater than the virtual tip.
```rust,ignore // For Normal
let priority = priority_calc(tip);
// For Operational
let virtual_tip = (inclusion_fee + tip) * OperationalFeeMultiplier; let priority = priority_calc(tip + virtual_tip); ```
Note: Since we use final_fee
the multiplier applies also to the regular tip
sent with the transaction. So, not only does the transaction get a priority bump based on the inclusion_fee
, but we also amplify the impact of tips applied to Operational
transactions.
Namespace
Type
Send a call through an indexed pseudonym of the sender.
Filter from origin are passed along. The call will be dispatched with an origin which use the same filter as the origin of this call.
NOTE:
If you need to ensure that any account-based filtering is not honored (i.e. because you expect proxy
to have been used prior in the call stack and you do not want the call restrictions to apply to any sub-accounts), then use as_multi_threshold_1
in the Multisig pallet instead.
Prior to version *12, this was called as_limited_sub
.
The dispatch origin for this call must be Signed.
Namespace
Type
Send a batch of dispatch calls.
May be called from any origin.
calls
: The calls to be dispatched from the same origin. The number of call must not exceed the constant: batched_calls_limit
(available in constant metadata).
If origin is root then call are dispatch without checking origin filter. (This includes bypassing frame_system::Config::BaseCallFilter
).
This will return Ok
in all circumstances. To determine the success of the batch, an event is deposited. If a call failed and the batch was interrupted, then the BatchInterrupted
event is deposited, along with the number of successful calls made and the error of the failed call. If all were successful, then the BatchCompleted
event is deposited.
Namespace
Type
Send a batch of dispatch calls and atomically execute them. The whole transaction will rollback and fail if any of the calls failed.
May be called from any origin.
calls
: The calls to be dispatched from the same origin. The number of call must not exceed the constant: batched_calls_limit
(available in constant metadata).
If origin is root then call are dispatch without checking origin filter. (This includes bypassing frame_system::Config::BaseCallFilter
).
Namespace
Type
Dispatches a function call with a provided origin.
The dispatch origin for this call must be Root.
Namespace
Type
Send a batch of dispatch calls. Unlike batch
, it allows errors and won't interrupt.
May be called from any origin.
calls
: The calls to be dispatched from the same origin. The number of call must not exceed the constant: batched_calls_limit
(available in constant metadata).
If origin is root then call are dispatch without checking origin filter. (This includes bypassing frame_system::Config::BaseCallFilter
).
Namespace
Type
undefined## Events
Batch of dispatches completed fully with no error.
Namespace
Type
Batch of dispatches completed but has errors.
Namespace
Type
Batch of dispatches did not complete fully. Index of first failing dispatch given, as well as the error.
Namespace
Type
A call was dispatched.
Namespace
Type
A single item within a Batch of dispatches has completed with no error.
Namespace
Type
A single item within a Batch of dispatches has been completed with error.
Namespace
Type
Too many calls batched.
Namespace
The limit on the number of batched calls.
Namespace
Type
List a vortex distribution
Namespace
Type
Disable a distribution
id
- The distribution id
Namespace
Type
Unsigned distribution of vortex, called by offchain worker
id
- The distribution id current_block
- Current block number
Namespace
Type
Redeem tokens from vault
id
- The distribution id vortex_token_amount
- Amount of vortex to redeem
Namespace
Type
Register distribution rewards
id
- The distribution id rewards
- Rewards list
Namespace
Type
Namespace
Type
Set asset prices
asset_prices
- List of asset prices id
- The distribution id
Namespace
Type
Set distribution eras
id
- The distribution id start_era
- Start era end_era
- End era
Namespace
Type
Start distributing vortex
id
- The distribution id
Namespace
Type
Trigger distribution
id
- The distribution id
Namespace
Type
Namespace
Type
Stores asset prices for each vortex distribution
Namespace
Type
Stores next unsigned tx block number
Namespace
Type
Namespace
Type
Stores stake and roles reward points for each vortex distribution
Namespace
Type
Stores total vortex amount for each distribution
Namespace
Type
Stores start and end eras of each vortex distribution
Namespace
Type
Stores order books for each vortex distribution
Namespace
Type
Stores payout pivot block for each vortex distribution
Namespace
Type
Stores status of each vortex distribution
Namespace
Type
Admin Account changed
Namespace
Type
Rewards registered
Namespace
Type
Set asset prices
Namespace
Type
Set distribution eras
Namespace
Type
Trigger distribution calculation
Namespace
Type
Distribution created
Namespace
Type
Distribution disabled
Namespace
Type
Distribution done
Namespace
Type
Distribution paid out
Namespace
Type
Distribution started
Namespace
Type
Assets should not include vortex asset
Namespace
Vortex distribution is not ready to be redeemed
Namespace
Vortex distribution is not ready to be triggered
Namespace
Invalid amount
Namespace
Invalid end block
Namespace
Not a validator
Namespace
Vortex distribution not triggered
Namespace
No Vtx asset minted
Namespace
Pivot string too long
Namespace
Require to be previous admin
Namespace
Vortex period not set
Namespace
Vortex distribution already enabled
Namespace
Vortex distribution disabled
Namespace
ID already in use
Namespace
No available Dist id
Namespace
History depth
Namespace
Type
The native token asset Id (managed by pallet-balances)
Namespace
Type
Payout batch size
Namespace
Type
Vortex root pot id
Namespace
Type
Vortex fee pot id
Namespace
Type
Unsigned transaction interval
Namespace
Type
Vortex token asset Id
Namespace
Type
Vortex distribution pot id
Namespace
Type
Move the caller's Id directly in front of lighter
.
The dispatch origin for this call must be Signed and can only be called by the Id of the account going in front of lighter
.
Only works if
both nodes are within the same bag,
and origin
has a greater Score
than lighter
.
Namespace
Type
Declare that some dislocated
account has, through rewards or penalties, sufficiently changed its score that it should properly fall into a different bag than its current one.
Anyone can call this function about any potentially dislocated account.
Will always update the stored score of dislocated
to the correct score, based on ScoreProvider
.
If dislocated
does not exists, it returns an error.
Namespace
Type
Counter for the related counted storage map
Namespace
Type
A bag stored in storage.
Stores a Bag
struct, which stores head and tail pointers to itself.
Namespace
Type
A single node, within some bag.
Nodes store links forward and back within their respective bags.
Namespace
Type
Moved an account from one bag to another.
Namespace
Type
Updated the score of some account to the given amount.
Namespace
Type
A error in the list interface implementation.
Namespace
The list of thresholds separating the various bags.
Ids are separated into unsorted bags according to their score. This specifies the thresholds separating the bags. An id's bag is the largest bag for which the id's score is less than or equal to its upper threshold.
When ids are iterated, higher bags are iterated completely before lower bags. This means that iteration is semi-sorted: ids of higher score tend to come before ids of lower score, but peer ids within a particular bag are sorted in insertion order.
Expressing the constant
This constant must be sorted in strictly increasing order. Duplicate items are not permitted.
There is an implied upper limit of Score::MAX
; that value does not need to be specified within the bag. For any two threshold lists, if one ends with Score::MAX
, the other one does not, and they are otherwise equal, the two lists will behave identically.
Calculation
It is recommended to generate the set of thresholds in a geometric series, such that there exists some constant ratio such that threshold[k + 1] == (threshold[k] * constant_ratio).max(threshold[k] + 1)
for all k
.
The helpers in the /utils/frame/generate-bags
module can simplify this calculation.
Examples
If BagThresholds::get().is_empty()
, then all ids are put into the same bag, and iteration is strictly in insertion order.
If BagThresholds::get().len() == 64
, and the thresholds are determined according to the procedure given above, then the constant ratio is equal to 2.
If BagThresholds::get().len() == 200
, and the thresholds are determined according to the procedure given above, then the constant ratio is approximately equal to 1.248.
If the threshold list begins [1, 2, 3, ...]
, then an id with score 0 or 1 will fall into bag 0, an id with score 2 will fall into bag 1, etc.
Migration
In the event that this list ever changes, a copy of the old bags list must be retained. With that List::migrate
can be called, which will perform the appropriate migration.
Namespace
Type
Enables XLS-20 compatibility on a collection
Collection must not have any tokens minted
Caller must be collection owner
Namespace
Type
Submit XLS-20 token ids to The Root Network Only callable by the trusted relayer account Can apply multiple mappings from the same collection in one transaction
Namespace
Type
Namespace
Type
Set the relayer address
Namespace
Type
Set the xls20 mint fee which is paid per token by the collection owner This covers the additional costs incurred by the relayer for the following:
Minting the token on XRPL
Calling fulfill_xls20_mint on The Root Network
Namespace
Type
The permissioned relayer
Namespace
Type
The extra cost of minting an XLS-20 compatible NFT
Namespace
Type
Maps from TRN native token_id to XLS-20 TokenId
Namespace
Type
A new relayer has been set
Namespace
Type
A collection has had XLS-20 compatibility enabled
Namespace
Type
A new XLS20 mapping has been set
Namespace
Type
Additional mint fee for XLS-20 mint has been paid to relayer
Namespace
Type
A new Xls20 Mint Fee has been set
Namespace
Type
Request sent to XLS20 Relayer
Namespace
Type
There is already a Root native -> XLS-20 mapping for this token
Namespace
No the owner of the collection
Namespace
The NFT does not exist
Namespace
The caller is not the relayer and does not have permission to perform this action
Namespace
The collection is not compatible with XLS-20
Namespace
The supplied fee for minting XLS-20 tokens is too low
Namespace
undefined
add a relayer
Namespace
Type
Namespace
Type
remove a relayer
Namespace
Type
Namespace
Type
Set XRPL door address managed by this pallet
Namespace
Type
Set the door tx fee amount
Namespace
Type
Sets the payment delay payment_delay is a tuple of payment_threshold and delay in blocks
Namespace
Type
Set the door account current ticket sequence params for current allocation - force set
Namespace
Type
Set the door account ticket sequence params for the next allocation
Namespace
Type
Set the xrp source tag
Namespace
Type
Submit xrp transaction challenge
Namespace
Type
Submit xrp transaction
Namespace
Type
Withdraw xrp transaction
Namespace
Type
Withdraw xrp transaction
Namespace
Type
Challenge received for a transaction mapped by hash, will be cleared when validator validates
Namespace
Type
Map from DelayedPaymentId to (sender, WithdrawTx)
Namespace
Type
Map from block number to DelayedPatmentIds scheduled for that block
Namespace
Type
The door address on XRPL
Namespace
Type
The current ticket sequence of the XRPL door account
Namespace
Type
The Ticket sequence params of the XRPL door account for the current allocation
Namespace
Type
The Ticket sequence params of the XRPL door account for the next allocation
Namespace
Type
The flat fee for XRPL door txs
Namespace
Type
Highest pruned XRPL ledger index
Namespace
Type
Highest settled XRPL ledger index
Namespace
Type
The next available delayedPaymentId
Namespace
Type
The highest block number that has had all delayed payments processed
Namespace
Type
Payment delay for any withdraw over the specified Balance threshold
Namespace
Type
Temporary storage to set the transactions ready to be processed at specified block number
Namespace
Type
Stores submitted transactions from XRPL waiting to be processed Transactions will be cleared according to the submission window after processing
Namespace
Type
List of all XRP transaction relayers
Namespace
Type
Settled xrp transactions stored against XRPL ledger index
Namespace
Type
Source tag to be used to indicate the transaction is happening from futureverse
Namespace
Type
XRPL transactions submission window width in ledger indexes
Namespace
Type
Keeps track whether the TicketSequenceThresholdReached event is emitted
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Transaction not supported
Namespace
Type
The payment delay was removed
Namespace
Type
The payment delay was set
Namespace
Type
Processing an event failed
Namespace
Type
Processing an event succeeded
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
Namespace
Type
A withdrawal was delayed as it was above the min_payment threshold
Namespace
Type
Request to withdraw some XRP amount to XRPL
Namespace
Type
Cannot process more transactions at that block
Namespace
This ledger index is within the submission window and can't be pruned
Namespace
The scheduled block cannot hold any more delayed payments
Namespace
The door address has not been configured
Namespace
highest_pruned_ledger_index must be less than highest_settled_ledger_index - submission_window_width
Namespace
The signers are not known by ethy
Namespace
The NextTicketSequenceParams is invalid
Namespace
The NextTicketSequenceParams has not been set
Namespace
The paymentIds have been exhausted
Namespace
Namespace
There is no settledXRPTransactionDetails for this ledger index
Namespace
Transaction submitted is outside the submission window
Namespace
Namespace
The TicketSequenceParams is invalid
Namespace
XRPL does not allow more than 8 signers for door address
Namespace
Too Many transactions per ledger
Namespace
Submitted a duplicate transaction hash
Namespace
Withdraw amount must be non-zero and < = u64
Namespace
Challenge Period to wait for a challenge before processing the transaction
Namespace
Type
Upper limit to the number of blocks we can check per block for delayed payments
Namespace
Type
Maximum number of delayed transactions that can be processed in a single block
Namespace
Type
Maximum number of transactions that can be pruned in on_idle
Namespace
Type
XRP Asset Id set at runtime
Namespace
Type