Decrease the amount of reserved KSM when register thread id with code/genesis. Warning to all KSM holders and devs!

Do you see any stats? 

https://kusama.subscan.io/event?page=1&time_dimension=date&module=registrar

51 days ago deregister chain event.

Last registration event  71 days 22 hrs ago.

Parity, fellowship for whom you are building the network? 

For yourself and yours system chains? or for people.

You changed the params to not let abuse via runtime upgrade with a largest wasm size. But in that particular set up kusama and polkadot was 3 years and nothing critical happend.

Parity, are you intentionally is trying to kill kusama? 
Market cap of polkadot to kusama is in ratio 20 : 1. the same treasury dollar cost allocation 

BUT:

Prices to register a new thread to start new project:

Polkadot 3300 DOT -> 14390$

Kusama 1110 KSM  -> 21645$ WHAT? 21k$+? ARE you KIDDING?

this numbers above is a price to just a register a wasm code with genesis. so how many developers would be attracted to start their idea on kusama and try something?

Parity, Fellowship! Please!

Please! this wish for change created to reduce the price for bytes for wasm file to be compatible with polkadot price.

Acroding to ration of market cap it should be 14390 / 20 = 720$ therefore around 40KSM. Ok you can multiply by the ration of num of nodes 297 vs 1000. so it is 3
So I believe 120 KSM to register wasm file with a max len size should be configured for Kusama runtime.

 

Summoning all KSM holders to take a careful look what parity is doing to force everyone leave kusama and go to polkadot.

UPD:

https://www.youtube.com/shorts/CaBtljsfPMk
Look the second part of this short.

so next in line to develop feature as off-chain runtime upgrade in next year!
It means that price for registration chain will be the same as now -> be 30k$ for the next year and kusama will still continue to lose devs and projects...