You are responsible for your node, including ensuring uptime, correct behavior, and monitoring. If your node is not responding properly, or is displaying dishonest behavior (like running keys on 2 nodes at the same time), you will be penalized.
- Gnosis (and Ethereum) utilize a Proof-of-Stake cryptoeconomic incentive system to secure the network and disincentivize malicious behavior by nodes.
- Nodes that play an active role in validating the network are required to stake 32 mGNO (i.e. 1 GNO) per validator. They receive periodic rewards for each epoch that they stay online and performing their duties.
- However, if they engage in malicious or disruptive activity on the network, their stake gets "slashed", and they can also be permanently removed from the validator pool.
- Nodes that go offline also attract a penalty for "inactivity leaks", although these are significantly less harsh if the node is offline only for a short period of time.
- The current yield on GNO staking can be found in this Dune Dashboard.
- As of Nov 2022, GNO staking has a ~15-16% yield.
Gnosis' rewards curve was proposed in Nov 2021 in a Gnosis Forum post.
- The minimum requirement to run a validator is 32 mGNO (i.e. 1 GNO).
- The reward rate drops with more active validators
|GNO staked||% of GNO validating||reward for validators||Total GNO rewards||Overall inflation p.a.|
Gnosis follows Ethereum's Proof-of-Stake penalties.
The most common "penalty" validators encounter is if they are offline, or are late in performing their duties of attesting or proposing blocks.
- Generally speaking, the penalties for being offline (or late) are equal to the rewards that a validator would have received if they were online
- If your validator is online more than 42.5% of the time, you will be earning a positive return
- Missed, late or incorrect attestations are penalized.
- There is no penalty for missing the head vote.
- There is no penalty for failing to propose a block.
- There is no penalty for missing a sync committee (except the lost rewards).
Gnosis will move into a "inactivity leak" mode, if a large number (i.e. >1/3) of validators are offline at the same time causing the network to not finalize.
- "Offline" validators receive increasingly large penalties based on their track records
- This is designed to restore finality by reducing the stake of "offline" validators, who may get ejected from the network if their stake drops below the minimum required (i.e. 16 mGNO)
Slashing is the most serious penalty and results in losing a potentially significant amount of stake, and possible ejection of a validator from the network. This is when validators break very specific protocol rules that prevent the network from functioning effectively.
In these cases, 1/32 of a validator's staked GNO is immediately burned, and the validator enters a removal process from the chain.
- "Double signing" is the most common slashing offence, where a validator proposes and signs two different blocks at the same slot. This often happens when a validator is run in two machines at once (e.g. redundancy).
- "Double voting" by attesting to two candidates for the same block
- Attesting to a block that "surrounds" another one (i.e. changing history)
We recommend the following readings for a more in-depth understanding of validator penalties.