Polkassembly Logo

Create Pencil IconCreate
OpenGov
View All Wish For Change

[WFC] No Fellowship Removal Without Kusama Vote

inWish For Change
8 days ago
Deciding

Wish

Any change that removes, merges, or otherwise eliminates the Kusama Technical Fellowship as an independent on-chain collective shall require a dedicated Wish For Change referendum on Kusama, approved by Kusama token holders, before implementation.

This applies to all mechanisms — including but not limited to runtime upgrades, Fellowship whitelisted calls, or governance migration — that would result in Kusama no longer having its own Technical Fellowship distinct from the Polkadot Technical Fellowship.

Context

Issue #484 proposes retiring the Kusama Technical Fellowship in favor of the Polkadot Technical Fellowship operating via bridge. PR #1100, merged March 12 2026, is the first implementation step — making Kusama system chains recognize the Polkadot Fellowship's authority alongside Kusama's own. This follows WFC 573, which committed Kusama to an independent JAM upgrade path.

The community whose governance structure would change should decide whether that change happens.

What this WFC does NOT do

  • It does not oppose fellowship consolidation on its merits
  • It does not seek to reverse PR #1100 (both fellowships currently coexist)
  • It does not require a separate Kusama Fellowship to be independently funded
  • It does not claim fellowship removal is irreversible — Kusama OpenGov retains full sovereignty regardless

It establishes one requirement: no removal without a Kusama vote.

Comments (2)

7 days ago

it is important to state that the presumption from the Polkadot Fellowship is that the Kusama Fellowship will be removed per #1100 without any KSM derived governance mandate:

Once the fellowship tooling is also upgraded and we see we can easily and reliably use the Polkadot Technical Fellowship on Kusama, we will follow-up with another change to completely remove the deprecated Kusama Technical Fellowship.

Also ahead of the Kusama JAM implementation was mandated via WFC #573 there was also the approval of WFC #498:

A New Kusama Vision - 10 Million DOT from W3F & Transition Away From Being A Canary Network...
...Recognise that Kusama is no longer merely a canary network and instead should be treated as an experiment-centric peer network of Polkadot.

We are approaching the pivotal moment - absolute clarity on claims of independence, sovereignity and opengov derived legitimacy - and indeed of the platform risk faced by those continuing to build infrastructure on Kusama.

7 days ago

Who's the proposer ?
Seems not to be verified

6 days ago

Hi there anon @EhmW...1L7K

This person is claiming authorship: https://forum.polkadot.network/t/clarifying-kusamas-governance-direction-independence-or-integration/16858/11

And you are right, it would be good that the proposer register a on-chain id for this referenda..

Cheers...

PleaseLogin to comment

Voting Period

Decision Period

22 / 28 days

Confirmation Period

0 / 1 days

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

Polkassembly · Archived 2026 · polkassembly.io

Terms and ConditionsTerms of Website
Privacy Policy