candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

staking_admin

Hey everyone,

I would like to propose this new referendum today as an amendment and follow-up on the previous [referendum #308](https://kusama.subsquare.io/referenda/308).
As stated before in referendum #308, the intention of the referendum is the promotion of 6 collators to invulnerables, these being:

- TurboFlakes
- LuckyFriday
- ParaNodes
- Polkadotters
- Stake.Plus
- IcebergNodes

The referendum was successfully executed on [block #20691161](https://kusama.subscan.io/block/20691161?tab=event&event=20691161-2), but unfortunately, not all colators were promoted as intended.

After recapping my steps when creating the previous referendum, I realized that I must have made a mistake when manually creating the preimage. The issue on the [original call](https://kusama.subscan.io/referenda_v2/308) falls on two of the six collators being duplicated and two others missing.

After discussing the issue with my peers, I would like to present this referenda to the community today. It intends to fix the previous issue and promote LuckyFriday and ParaNodes to invulnerables on Asset-Hub Kusama as per the intention of the previous referendum.

Once again, apologies to LuckyFriday and ParaNodes for wrongly being missed on the previous call.

And thank you all for your time and vote,
Paulo


- Paulo is proposing a new referendum to fix a mistake made in a previous referendum (#308).
- The previous referendum aimed to promote 6 collators to invulnerables on Asset-Hub Kusama.
- However, not all collators were promoted as intended due to a mistake in manually creating the preimage.
- Paulo wants to fix the issue by promoting LuckyFriday and ParaNodes to invulnerables through this new referendum.
- Paulo apologizes to LuckyFriday and ParaNodes for the mistake and thanks everyone for their time and vote.

Executed

[Fix 308] Expand invulnerables set on Asset-Hub Kusama

Hey everyone,

I’m proposing this referendum today, it aims to fix the only XCM instruction that failed to execute from the successful outcome of [referendum 224](https://kusama.subsquare.io/referenda/224). 

**Brief Summary**
The previous referenda 224 was all about decentralizing the collator set on both system chains  – Bridge-hub Kusama and Asset-hub Kusama with a call tabled with five XCM instructions. From these five instructions, four were successfully executed and only the call related to the expansion of the invulnerables set on Asset-Hub Kusama failed to execute. The reason for the failed instruction was due to the fact of missing onchain session keys from one of the collators by the time the referenda moved into the execution phase.

At the time, knowing that the runtime v1000000 would bring new extrinsics to better handle such cases and also facilitate add/remove invulnerables, was than discussed by all parties involved that would make sense to wait until the current runtime was active on chain to propose a new referenda that would fix the previous XCM instruction, and such referenda could also be used as an opportunity to try out the new extrinsic – collatorSelection.addInvulnerable. 

As a result I’m proposing this referendum asking the community to vote on it.

**What to expect from this referendum**
With the successful outcome we could expect the following:

- 6 new invulnerables, changing the total number from 2 to 8 (Note: the following list of collators were the ones already previously selected on referenda 224)
TurboFlakes: `H1tAQMm3eizGcmpAhL9aA9gR844kZpQfkU7pkmMiLx9jSzE`
LuckyFriday: `HPUEzi4v3YJmhBfSbcGEFFiNKPAGVnGkfDiUzBNTR7j1CxT`
ParaNodes: `J11Rp4mjz3vRb2DL51HqRGRjhuEQRyXgtuFskebXb8zMZ9s`
Polkadotters: `EPGHRDFaBbQz4uF8DgnuScxYp4rvvtpL5MTed7VvGprNQmm`
Stake.Plus: `E5G5qLNBF7nwhemokqNrNwUCQ7oHrLsBVjSc7XhTdRq8672`
IcebergNodes: `Eicei1RVHvqHBPJAY2fZpLy2KtCMjY7Kwjo3svjmGLH7FmT`

- 3 out of the 9 active permissionless collators will automatically switch to invulnerables with the remaining 6 keeping their active slot.

Thanks for your vote and time
paulo // apps.turboflakes.io


- A proposal is being made to fix a failed instruction from a previous referendum.
- The failed instruction was related to expanding the invulnerables set on Asset-Hub Kusama.
- The reason for the failed instruction was due to missing onchain session keys from one of the collators.
- The proposal asks the community to vote on adding 6 new invulnerables, changing the total number from 2 to 8.
- 3 out of the 9 active permissionless collators will automatically switch to invulnerables with the remaining 6 keeping their active slot.

[Fix 224] Expand invulnerables set on Asset-Hub Kusama

[Referendum 214](https://kusama.polkassembly.io/referenda/214) with call info that will work.

[Fix 214] Further decentralize collator set on Kusama system chains

This proposal aims to decentralize the following system chains – Kusama Asset Hub (former Statemine) and Kusama Bridge Hub. This change was collectively discussed and agreed by many of the ecosystem collators and it is consistent with [Framework for Collators on System Parachains](https://docs.google.com/document/d/1H2T1Nx90HkSAYF_CaOPLG-o3LS7h_QAa2WLDdcSJMs0/edit#) that was written as a collective effort.

The proposed change will do the following

- leave 2 Parity invulnerable collators on each chain
- make 8 community collators on Asset Hub invulnerable
- create an additional 6 permissionless slots on Asset Hub
- do the same for the BridgeHub

These new 6 permissionless slots will be opened to any new collator by placing a bond of 50 KSM once this referendum is enacted. 

- This proposal is about changing two systems called Kusama Asset Hub and Kusama Bridge Hub.
- Many people who work together on these systems agreed to the change.
- The change will leave some important people in charge, but also make room for more people to join.
- There will be 6 new spots for people to join one of the systems.
- To join, people will need to pay 50 KSM.

Further decentralize collator set on Kusama system chains

On [2022-12-12](https://kusama.subsquare.io/referenda/referendum/16) this [referendum proposal](https://kusama.polkassembly.io/referenda/16) was executed to, among other things, lower the `min_untrusted_score` to deal with a [mass slashing incident](https://forum.polkadot.network/t/kusama-era-4543-slashing/1410) in Kusama.

This proposal aims at updating the current `min_unstrusted_score` in Kusama back to sensible values. The new minimum untrusted score was calculated by averaging the last 30 election scores and halving them (starting from election at block [#17416892](https://kusama.subscan.io/block/17416892)).

When enacted, this proposal will change the current untrusted minimum score in Kusama from

```
{
  minimalStake: '1,722,238,583,242,009',
  sumStake: '2,171,296,385,410,646,127',
  sumStakeSquared: '62,184,223,048,402,160,114,561,549,513,680,866'
}
```

to
```
{
  minimalStake: '2,957,640,724,907,066',
  sumStake: '3,471,819,933,857,856,584',
  sumStakeSquared: '78,133,097,080,615,021,100,202,963,085,417,458'
}
```

--- 

## Why is this change important?

The [`MinimumUntrustedScore`](https://github.com/paritytech/substrate/blob/master/frame/election-provider-multi-phase/src/lib.rs#L1326) configuration defines the minimum election score that will be accepted by the elections pallet from off-chain staking miners. Increasing the minimum untrusted score ensures that weak election solutions will not be accepted. The proposed election score is more sensible and secure given the current state of the network. 


- On December 12, 2022, a proposal was executed in Kusama to lower the `min_untrusted_score` due to a mass slashing incident.
- The proposal aims to update the current `min_untrusted_score` in Kusama to sensible values.
- The new minimum untrusted score was calculated by averaging the last 30 election scores and halving them.
- When enacted, this proposal will change the current untrusted minimum score in Kusama.
- Increasing the minimum untrusted score ensures that weak election solutions will not be accepted, making the network more secure.

Update elections' minimum untrusted score


**Short description:** This proposal seeks to adjust validator minimum commission rate from 3% to 10%

**Project Category / Type:** Infrastructure

**Discussion date:** 23.11.2022.  [https://kusama.polkassembly.io/post/1993](https://kusama.polkassembly.io/post/1993)

**Onchain publish date:** 26.01.2023.

**Governance referenda origin call:** staking_admin

**Context**

This proposal seeks to adjust the validator minimum commission rate and keeps all other staking configurations unchanged. In the current market (last several months) validator income from the minimum commission can cover less than 50% of the server rent costs. In order to maintain a sustainable environment and prevent the network degradation I am passing this proposal to onchain voting.

**Problem**

There were several topics regarding to the validator infrastructure expenses and operational costs that can be found here:

[https://kusama.polkassembly.io/post/1980](https://kusama.polkassembly.io/post/1980)

[https://kusama.polkassembly.io/post/1306](https://kusama.polkassembly.io/post/1306)

A fully active validator operating at 3% commission can stand to earn:

(800/1000)* 4 * 30 * 0.03 = 2.88 KSM/month. 
With KSM priced at 34$ this equates to ~97.92 USD/month. 


**Proposal**

The proposed increase of minimum commission to 10% is trying to create a better and more sustainable network environment. With the numbers given above it is clear this is a small step towards this goal. Beside the commission, we would need KSM price to double and reach 50$ in order to earn ~480 USD/month which is still within the boundaries of operational costs.

With this proposal we are not influencing KSM inflation rate. We are asking the nominators to steer 1.36% of their staking APY towards the network, current returns are 18.88% and we anticipate it to be 17.52% all other factors being equal. We need to have a strong, reliable, secure and redundant blockchain network in order to process and secure multi million $ assets on it.


**Objectives**

Validator earnings and effects on staking rewards

A fully active validator operating at 3% commission can stand to earn 
(800/1000)* 4 * 30 * 0.03 = 2.88 KSM/month. : 

- with KSM priced at 25$ this equates to ~ 72.00 USD/month.

- with KSM priced at 34$ this equates to ~ 97.92 USD/month.

- with KSM priced at 50$ this equates to ~ 144.00 USD/month.

A fully active validator operating at 10% commission can stand to earn 
(800/1000)* 4 * 30 * 0.1 = 9.60 KSM/ month.

- with KSM priced at 25$ this equates to ~ 240.00 USD/month.

- with KSM priced at 34$ this equates to ~ 326.40 USD/month.

- with KSM priced at 50$ this equates to ~ 480.00 USD/month.


**Known constraints**

A significant change of KSM price can have a positive or a negative impact to the changes proposed. This proposal is not trying to set permanent staking parameters i.e.  In a scenario where KSM hits $100 anyone can start a new proposal to decrease the commission rate.



**[Full Proposal](https://docs.google.com/document/d/1sHrRM7wPv390GfhdPJeUKtfKD81X5ME5OIGrlDXqOXI/edit?usp=sharing)**

- This proposal suggests changing the minimum commission rate for validators from 3% to 10%.
- This change is being proposed because the current commission rate is not enough to cover the costs of running a validator node.
- The proposal suggests that increasing the commission rate will create a more sustainable network environment.
- The proposal does not affect the inflation rate of KSM.
- The proposal suggests that a strong and secure network is needed to process and secure multi-million dollar assets.

[10] Origin: StakingAdmin