This referendum calls MultiBlockElectionSigned.set_invulnerables on Polkadot Asset Hub to restore the Parity staking miner as an invulnerable signed submitter (16ciP5rjt4Yqivi1SWCGh7XsA8BDguV4tnTuyr937u2NME6h)

Background

When staking moved to Asset Hub, this account was set as the only invulnerable signed submitter of the multi-block election. An invulnerable submitter pays a fixed deposit (10 DOT) instead of the queue-dependent one.

The account lost this status by accident/bug: a rejected solution used to remove its submitter from the invulnerables automatically. Since polkadot-sdk#10454, which is included from polkadot-stable2509-4 onwards, only governance can remove an invulnerable. The list has been empty since then.

What this referendum does

• Sets the invulnerables list to the single account above. The list is empty today, so no other account is affected.
• Changes no other parameter, and adds no code or runtime upgrade.

Call

• Call data: 0x580404f86a0e73c498fa0c135fae2e66da58346e777a6687cc7f7d234b0cb09c021232
• Call hash: 0xc9dbdc01bc26c8a249022d3c20f36ad34af14f6375358087970c8162c691c560

Notes

• A community miner (14x3h6Vfr1fcW1wcf53K3LiTkMHQUcWQzWLRYAB7AnAehhFN) has won every election for several weeks, see the recent reward events. The Parity miner runs only as a safety net that submits only if no better solution is available. The extra safety net is represented by the on-chain unsigned solution in case no miner is running.
• Being invulnerable is part of that safety net. Once invulnerable, the Parity miner always pays a fixed 10 DOT deposit, however many submissions are in the queue. It doesn't make the Parity miner more likely to win. The best valid solution still wins.
• If the community miner(s) stop running and the Parity miner starts winning, I would be in favor of sending its rewards to the DAP buffer at regular intervals via bot or similar.