# System Chains: The Same Bad Actors Again

**URL:** <https://forum.polkadot.network/t/system-chains-the-same-bad-actors-again/18667>\
**Category:** Governance\
**Created:** [September 15, 2026, 8:34pm UTC](https://forum.polkadot.network/t/system-chains-the-same-bad-actors-again/18667 "2026-09-15T20:34:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Megadot](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/megadot/32/10593_2.png) [@Megadot](https://forum.polkadot.network/u/Megadot)\
**Post date:** [September 15, 2026, 8:34pm UTC](https://forum.polkadot.network/t/system-chains-the-same-bad-actors-again/18667/1 "2026-09-15T20:34:39Z")

</div>

Eight days ago, I raised [concerns in the System Chains Bounty top-up discussion](https://polkadot.subsquare.io/referenda/1943) about validators with a documented history of questionable practices who continue to occupy privileged positions in the ecosystem, apparently with the support of W3F.

- Mile​🌍 - [commision flipping](https://forum.polkadot.network/t/validators-running-multiple-identities-and-flipping-commissions-in-same-day/16569/10)and [running other identity](https://forum.polkadot.network/t/validators-running-multiple-identities-and-flipping-commissions-in-same-day/16569/52)
- 🐟YellowFin Tuna​🐟 - [commision flipping](https://forum.polkadot.network/t/validators-running-multiple-identities-and-flipping-commissions-in-same-day/16569/10) and [running other identity](https://forum.polkadot.network/t/validators-running-multiple-identities-and-flipping-commissions-in-same-day/16569/42)
- Coinstudio - [commision flipping](https://forum.polkadot.network/t/validators-running-multiple-identities-and-flipping-commissions-in-same-day/16569/10)
- 🕴TUXEDO​🕴 - c[ommision flipping](https://forum.polkadot.network/t/validators-running-multiple-identities-and-flipping-commissions-in-same-day/16569/10)
- Openbitlab - [running other identity](https://forum.polkadot.network/t/validators-running-multiple-identities-and-flipping-commissions-in-same-day/16569/50)
- BESTVALIDATOR | ZURICH - [running mutiple identities](https://forum.polkadot.network/t/validators-running-multiple-identities-and-flipping-commissions-in-same-day/16569/51)

Eight days later, **the curators have not even acknowledged these concerns**. This silence says a lot about the level of transparency and accountability being applied to issues raised by the community.

What is particularly difficult to understand is how operators who have repeatedly abused the community’s trust can continue to be granted privileged positions in the **System Chains** , which are among the most critical pieces of infrastructure in the Polkadot ecosystem.

And now, with multiple referenda on [Polkadot](https://polkadot.subsquare.io/referenda) and [Kusama](https://kusama.subsquare.io/referenda) proposing changes to the invulnerable collators of AssetHub, Coretime and other System Chains, **some of the same actors appear once again in the proposed allocations**.

For example, the [proposed People Polkadot setup](https://polkadot.subsquare.io/referenda/1948) is just one example of what is happening across the System Chains, with the same pattern appearing in AssetHub, Coretime and the other System Chains as well.

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/9/922f804ce51ffcfdba980dd0fa78abe36f2f72c9.png)

This should not be treated as business as usual. Operators who have abused the community’s trust should not be rewarded with privileged System Chain positions. **They should be removed from these roles, and the community should immediately reconsider and withdraw nominations supporting them.**

The community deserves transparency about the selection criteria, an explanation of how previous concerns have been evaluated, and accountability from those responsible for these decisions.

**It is now up to the community to scrutinise these referenda carefully, and to see where W3F stands when accountability actually matters.**

---

<div class="post-metadata">

**Author:** ![ultracoconut](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/ultracoconut/32/5932_2.png) [@ultracoconut](https://forum.polkadot.network/u/ultracoconut)\
**Post date:** [September 17, 2026, 9:48am UTC](https://forum.polkadot.network/t/system-chains-the-same-bad-actors-again/18667/2 "2026-09-17T09:48:29Z")

</div>

I have a solution for that:

> [@Proposal: Unified Collator Pool for System Chains (64 Slots)](https://forum.polkadot.network/t/proposal-unified-collator-pool-for-system-chains-64-slots/18453):
>
> Short Description I propose unifying the collator infrastructure of Polkadot’s System Chains — Polkadot Hub, Bridge Hub, People, Collectives, etc. — into a single shared pool of 64 active operators. Instead of maintaining separate collator sets for each System Chain, all operators would be capable of supporting the entire System Chain ecosystem. The protocol could then dynamically assign block production responsibilities across the pool. The goal is to reduce infrastructure fragmentation, impr…