Summary On 2025-11-25 15:54 UTC during a spammening session, kusama test parachains were used to spam with transactions and finality started lagging until the failsafe kicked in. [Finality lag] Why did the finality started lagging ? As more load was added on the spammening test parachains nodes s…

[image] alexggh: @validators please make sure you respect the hardware specifications. One would think this ought to be optional and not have to be said in any case, and that those who can’t keep up would be chilled and/or slashed in the case they can’t do what they’ve committed to doing befo…

[image] somedude: ould think this ought to be optional and not have to be said in any case, and that those who can’t keep up would be chilled and/or slashed in the case they can’t do what they’ve committed to doing before getting elected. Yes, that would be the desirable state, this RFC Corre…

[2025-11-25] Kusama parachains spammening aftermath

Tech Talk

alexggh December 11, 2024, 9:01am 3

Yes, that would be the desirable state, this RFC Correct validator rewards by burdges · Pull Request #119 · polkadot-fellows/RFCs · GitHub is aimed to surface the validators that don’t keep up with their assigned work and punish them in rewards.

Topic		Replies	Views
[2025-05-09] Kusama dispute storm postmortem Tech Talk postmortem	3	585	May 18, 2025
Finality stall on Kusama (15.02.2024) - post mortem Tech Talk postmortem , kusama	8	615	February 22, 2024
Update: Parachain validator set size increase on Kusama Governance validators , kusama	4	673	July 9, 2024
Stalled parachains on Kusama - post mortem Tech Talk postmortem , kusama	5	1058	September 27, 2023
[2024-09-17] Polkadot finality lag/slow parachain production immediately after runtime upgrade - post mortem Tech Talk postmortem	0	610	September 18, 2024

[2025-11-25] Kusama parachains spammening aftermath

Related topics