Skip to content

Commit 1d8a899

Browse files
authored
Merge pull request #1226 from Concordium/Protocol-8-changes
Added information about suspending a validator
2 parents fb3863d + bb24f2b commit 1d8a899

File tree

2 files changed

+37
-0
lines changed

2 files changed

+37
-0
lines changed

source/mainnet/docs/protocol/concepts-baker.rst

+33
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ A validator needs to :term:`stake<staked amount>` a part of its CCD balance on t
2020

2121
All validators automatically take part in a *lottery* every round to decide who will produce the next block, see :term:`leader election<leader election>`. The greater the validator's stake, the greater the validator's chance of :term:`winning the lottery<lottery power>` and being selected to produce a block.
2222

23+
2324
Overview of the validation process
2425
==================================
2526

@@ -104,3 +105,35 @@ A block is final when it cannot be rolled back any more, i.e., part of the autho
104105

105106
A block is final at a minimum of two seconds after its creation. A new block has to be created descended from that block for the new block to be final.
106107

108+
Validator Suspension
109+
====================
110+
111+
A validator may be suspended if it remains inactive and fails to produce blocks when selected as a round leader. This mechanism, introduced in Protocol 8, helps maintain the blockchain's performance and reliability by excluding inactive validators.
112+
113+
A validator faces :term:`suspension` if it reaches a threshold of missed rounds. The size of a validator's stake affects how long the validator's node has to be inactive before reaching the threshold:
114+
115+
* High-stake validators may reach the suspension threshold within hours due to their frequent selection as round leaders.
116+
* Low-stake validators may take several days to reach the threshold due to fewer opportunities to produce blocks.
117+
118+
When a validator misses multiple blocks in succession and reaches the inactivity threshold by a payday, it becomes *primed for suspension*. The validator then has until the next snapshot epoch to demonstrate activity by either:
119+
120+
* Producing a block
121+
* Having their signature included in a quorum certificate
122+
123+
If the validator remains inactive through the snapshot epoch, the suspension takes effect at the following payday epoch.
124+
125+
.. note::
126+
127+
A high-stake validator could face suspension after approximately 23 hours of inactivity, while low-stake validators typically require a longer period of inactivity before reaching the threshold.
128+
129+
130+
A suspended validator:
131+
132+
* Can resume validation through a manual transaction
133+
* Incurs no specific penalties beyond the suspension period
134+
* Maintains its delegators unless the delegators choose to update their delegation
135+
136+
.. note::
137+
138+
The protocol includes safeguards to prevent more than one-third of the total stake from being suspended simultaneously as this would halt the blockchain. This suspension mechanism protects against accidental or careless inactivity but does not protect against malicious behavior.
139+

source/mainnet/docs/resources/glossary.rst

+4
Original file line numberDiff line numberDiff line change
@@ -413,6 +413,10 @@ Also see the Concordium `Whitepaper <https://developer.concordium.software/gover
413413

414414
A list presented to a wallet by a dApp or service whose items are either attributes to reveal, or properties of attributes to prove.
415415

416+
Suspension
417+
418+
A state where a validator is temporarily excluded from block production due to prolonged inactivity. The suspension threshold varies based on the validator's stake size and remains in effect for at least one epoch until manually resumed.
419+
416420
Tally
417421

418422
Tally (noun) is the number of votes obtained by every candidate computed by summing all weighted votes for every candidate. Also, tally (verb) is the process of calculating the number of votes.

0 commit comments

Comments
 (0)