Staking Menu Overview
Overview of the Staking UI on azero.dev
Accessing the Staking Menu
The staking menu has the following tabs: Overview, Accounts, Payouts, Pools, Targets, Slashes, Validator stats, Performance and Suspensions. Let us now go over them one by one.
The Overview tab (testnet)
This tab gives you a high-level overview of the following aspects of the staking mechanism.
- The number of validators elected in the current era;
- Number of nominators in the current era (and in the next era);
- The total percentage of AZERO, as a fraction of all AZERO in existence;
- Current yearly inflation (this started at 10% on mainnet launch and is dropping towards 0%);
- Current session number and current era number.
Accessing this view will allow you to validate and nominate. Two important concepts are useful to understand before starting to nominate on Aleph Zero:
- Stash account: is an address that is used to keep the funds; it is used infrequently. You can think about it as your "cold wallet."
- Controller account: it does not keep funds and is frequently used. Specifically, it is used to perform actions (such as nominating a validator) on behalf of the stash but can't transfer the funds from the stash.
In the “Stashed” view, you can perform actions related to the nomination (and also validation).
The Stashed view (testnet)
In the “Pooled” view, you can perform actions related to nomination pools: see the pools you are a member of, claim rewards, etc.
The top of the Pooled view (testnet)
This tab is currently not very useful, as the Foundation runs an automated service to trigger payouts to all nominators/validators when they are available (note that this does not apply to pools, though). If you would like to see your historic payouts, we recommend using subscan—simply paste your Account in the search bar to display the details of your account, including staking rewards.
Staking Pools on mainnet
You can view the list of Nomination pools. SeeHow to Start Staking to learn more about what they are. Note that you can select "Own pools," "All pools," or "Foundation pools." The last option will display the (at the moment of writing) 10 pools operated by the Aleph Zero Foundation.
Targets tab on mainnet
This is the tab where you can conveniently analyze all available validators. The ones with a blue arrow next to them are currently part of the era committee. You can sort the list by "return," "total stake," or other parameters.
One of the defense mechanisms to guard the Aleph Zero blockchain against malevolent agents involves a slashing mechanism that penalizes users financially for disrupting the workings of the network. The tab called Slashes is a way for you to check out which users have been behaving dishonestly and, consequently, had their funds slashed. We note, though, that there is no automatic slashing currently on Aleph Zero. Also, at the moment of writing, there were no cases of malicious behavior from any of the validators, so you will most likely find this tab empty.
Validator stats on testnet
You can query a Stash Account of any validator in order to see their basic statistics. This is useful mostly to validators. But you, as a nominator, can also check if there are any recent sessions during which the validator you have in mind has underperformed. Apart from that, there are helpful diagrams that show the following:
- rewards received in a given era and the average reward till that era;
- input total stake for a given era;
- validator commission in a given era.
By default, the stored history will go back 84 eras.
Performance tab on mainnet
The performance tab allows you to track in real-time the current session and research the historical sessions to see how many blocks each particular validator created. This is of interest mostly to validators, as the numbers are not readily convertible to how much rewards the validator or their nominators will receive. If you are interested in this subject, we can refer you toElections and Rewards Math.
Suspensions on testnet
A mechanism to penalize validators for insufficient performance that is less severe than slashing is known as "suspension." A validator can be automatically suspended for underperforming a certain number of sessions in a short time window. In such a case, such a validator is ejected from the era committee and cannot join back until the suspension period is over. The above screenshot comes from the Testnet, where suspension happens quite often, as there are no financial incentives to keep the nodes in good condition. At the moment of writing, there were no suspensions on the Mainnet yet.