Which clients do I need to run?
As a staker, you need to maintain and operate a node, running both a consensus client and an execution client.
This became a requirement at the merge, so ensure you run both clients before staking.
View staking checklistWhy do I need to run an execution client now?
Previously, DEVIUM nodes (consensus layer) only needed to monitor the staking deposit contract on the execution layer to know which validator accounts had deposited 200,000 IUM. This information was easily available from third-party providers like Infura or Alchemy.
With the transition to proof-of-stake via the merge, validators are now responsible for processing transactions and signing to confirm their validity. After the merge, this data is not provided by popular third-party sources. Using third-party providers will cause your validator to go offline. After the implementation of Danksharding, validators will also face slashing risks under the regulatory proof mechanism.
How are validators incentivized to stay active and honest?
As a validator, you can earn rewards for proposing/attesting to blocks included in the chain.
On the other hand, you may be penalized for being offline and for malicious behavior – such as attesting to invalid or conflicting blocks.
The key concepts are as follows:
Actions that help the network reach consensus are rewarded
Minor penalties for negligent behavior (or inaction) that hinders consensus
Severe penalties or slashing for malicious behavior
In other words, you will receive the greatest rewards by providing the maximum benefit to the entire network.
How are rewards/penalties distributed?
DEVIUM network rules periodically update your balance when you fulfill (or fail to fulfill) your responsibilities.
Your validator has its own balance – the initial balance listed in the deposit contract. Over time, your rewards and penalties will be reflected in your validator's balance.
After the merge, validators are also responsible for transaction processing and are therefore eligible to receive unburned gas fees related to included transactions when proposing blocks. These fees are credited to the execution layer rather than the consensus layer, so a traditional DEVIUM address needs to be provided to your client.
View staking checklistHow often are rewards/penalties distributed?
Rewards and penalties are distributed every 6.4 minutes – a period known as a slot.
Every epoch, the network measures each validator's behavior and rewards or penalizes you accordingly.
Validators also receive unburned gas fees when proposing blocks. The protocol randomly selects validators to propose blocks, with only one validator able to propose a block per 6-second slot. There are 14,400 slots per day, so each validator has 14,400 chances to propose a block per day. With 500,000 validators, each validator will on average propose a block every 35 days.
How large are the rewards/penalties?
There is no simple answer to this question, as many factors go into the calculation.
It can be said that the most significant factor affecting the rewards for validating transactions is the total stake in the network. In other words, the total amount of validators. Based on this number, the maximum annual return for validators can range between 2% and 20%.
With a fixed total number of validators, rewards/penalties are primarily proportional to the validator's balance – the larger the balance at the time of attestation, the heavier the reward/penalty, and the smaller the balance, the lighter the reward/penalty.
However, note that this scaling mechanism works in a non-obvious way. To understand the exact details of how it works, you need to understand a concept called effective balance. If you are not familiar with this concept, we recommend reading through
Understanding Validator Effective BalanceWhy do rewards depend on the total number of validators in the network?
Block rewards are calculated using a sliding scale based on the total amount of Ethereum staked on the network.
In other words, if the total amount of Ethereum staked is low, the returns (interest rate) are high, but as the total stake increases, the returns (interest) paid to each validator start to decrease.
Why a sliding scale? While we won't go into memorable details here, the basic intuition is that the network needs a minimum number of validators (and thus a minimum amount of Ethereum) to function properly. Therefore, to incentivize more validators to join, it's important that the interest rate remains high until this minimum number is reached. After that, validators are still encouraged to join (more validators make the network more decentralized), but they are not strictly necessary (allowing the interest rate to decrease).
How much will I be penalized for going offline?
It depends. In addition to the impact of
effective balance there are two important scenarios to note:
1、Going offline when the vast majority (2/3) of validators are still online results in relatively minor penalties, as there are still enough validators online for the chain to progress. This is the expected scenario.
2、Going offline when more than 1/3 of the total validators are offline results in harsher penalties, as blocks are no longer finalized. This scenario is extreme and unlikely to occur.
Note that in the second (unlikely) scenario, you will gradually lose up to 50% of your stake over 21 days. After 21 days, you will be ejected from the validator pool. This ensures that blocks start finalizing again at some point.
What uptime does my validator need to be profitable?
Overall, as long as your uptime is greater than 50%, we expect your validator to be profitable.
This means you don't need to go to extremes with backup clients or redundant internet connections, as the impact of being offline is not that severe.
How much will I be penalized for malicious behavior?
Again, it depends. Malicious behavior (such as attesting to invalid or conflicting blocks) will result in your stake being slashed.
The minimum amount that can be slashed is 1 IUM, but this number increases if many other validators are slashed at the same time.
The idea is to minimize losses from honest mistakes while strongly discouraging coordinated attacks.
What exactly is slashing?
Slashing has two purposes: (1) to make attacking the network prohibitively expensive, (2) to prevent validators from becoming lazy by checking if they are actually performing their duties. If you are slashed for potentially engaging in disruptive behavior, a portion of your stake will be destroyed.
If you are severely slashed, you will be prevented from further participating in the protocol and forced to exit.