candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

staking_admin

- A proposal to cancel a "deferred" slash for era 7126 is being submitted.
- The slash was due to a bug, and similar issues in the past were canceled.
- The problem occurred because a node issued an unnecessary "pre-vote" after downtime.
- This led to an equivocation, which is a slashable offense.
- The issue was reported immediately, but delays caused the slash to be reported later.
- The operator has already compensated the affected parties.
- The community is asked to support canceling the slash due to the bug.

Executed

Dear community,
I'm submitting this proposal to cancel a "deferred" slash for era 7126 which would be applied in era 7154.&nbsp; The issue resulting in the slash was deemed to be<a href="https://github.com/paritytech/polkadot-sdk/issues/5778"> bug related</a> and the technical details are still being investigated.&nbsp; Historically, deferred slashes due to bugs were cancelled.
The issue, in my simple interpretation is as follows:
<ul>
<li>There was downtime due to hardware issues</li>
<li>Before the downtime one of my nodes was due to issue a "pre-vote"</li>
<li>When the node was online again, time passed and the prevote was no longer necessary.</li>
<li>The node may have used the local (not sync'd) finalized block as reference and proceeded to issue the pre-vote</li>
<li>Because the pre-vote already issued it resulted in an equivocation which is a slashable offence</li>
<li>Ideally, the node should have determined that time passed and the pre-vote wasn't necessary anymore</li>
</ul>
Given the circumstances and if my interpretation is correct this can happen to any operator who may restart their nodes with a pre-vote "in queue" given a delay in finalized blocks.
The issue was reported immediately but because of the bug, the "slash" was reported some 24 later. Time was also lost while trying to get a technical verdict on whether this was a bug or operator related. Given these delays, it is unlikely to receive a cancellation of the deferral on time. I would however engage the community for a deferral in solidarity.
I have already <a href="https://kusama.subscan.io/extrinsic/0x1721218fbc11aef01268df4b8cdae452a90287f4e0f300eeee8a0e9a9fffa1c4">compensated</a> the slashed parties (rounding up) and I am working on another payout for those affected by any offline time.
Kind Regards, Will | Paradox

WHO: Will | Paradox
WHAT: Submitting a proposal to cancel a "deferred" slash for era 7126 which would be applied in era 7154 due to a bug-related issue resulting in downtime.
PRICE/TIMEFRAME/RESOURCES: Not specified. Will has compensated the slashed parties and is working on another payout for those affected by any offline time.

Cancel Deferred Slash 7126 - Due to application bug

TimedOut

This was submitted with the era the slash took place.&nbsp; However, upon advice and further investigations this should be submitted with the era the slash is due to be enacted. Please vote nay and review the next referenda.

Cancel Deferred Slash - Era 7126 - Vote Nay

Please vote NAY

Rejected

[Invalid: Vote Nay] Staking Controller Account Deprecation

### Referendum Summary

- **Purpose**: To promote 6 collators to invulnerables on Asset-Hub Kusama.
- **Previous Referendum**: Referendum #308 intended to promote TurboFlakes, LuckyFriday, ParaNodes, Polkadotters, Stake.Plus, and IcebergNodes.
- **Execution**: Successfully executed on block #20691161, but not all collators were promoted.
- **Issue**: Mistake in creating the preimage led to duplication of two collators and omission of two others.
- **Proposed Fix**: New referendum to correct the error and promote LuckyFriday and ParaNodes to invulnerables.
- **Apology**: Apologies to LuckyFriday and ParaNodes for the oversight in the previous referendum.
- **Community Involvement**: Request for community support and votes to correct the issue.

WHO: Paulo

WHAT: Proposing a new referendum to fix the issue of not promoting LuckyFriday and ParaNodes to invulnerables on Asset-Hub Kusama as intended in the previous referendum.

PRICE/TIMEFRAME/RESOURCES: Not specified.

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

### Referendum Proposal Summary

- **Purpose**: Fix a failed XCM instruction from Referendum 224.
- **Background**: Referendum 224 aimed to decentralize collator sets on Bridge-hub Kusama and Asset-hub Kusama.
- **Issue**: One XCM instruction failed due to missing session keys on a collator.
- **Solution**: Propose a new referendum to add new invulnerables using a new extrinsic.
- **Expected Outcome**: Add 6 new invulnerables, increasing the total from 2 to 8.
- **Collators Added**: TurboFlakes, LuckyFriday, ParaNodes, Polkadotters, Stake.Plus, IcebergNodes.
- **Impact**: 3 out of 9 active permissionless collators will become invulnerables.

WHO: Paulo, proposing a referendum to the Kusama community.
WHAT: Fixing the only XCM instruction that failed to execute from the successful outcome of referendum 224.
PRICE/TIMEFRAME/RESOURCES: Not specified.

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

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

- The proposal wants to change how some systems (Kusama Asset Hub and Kusama Bridge Hub) work.
- It was agreed by many people who help run these systems.
- The changes include:
  - Keeping 2 special collators from Parity on each chain.
  - Making 8 community collators on Asset Hub special.
  - Adding 6 new spots on Asset Hub for anyone to join.
  - Doing the same for BridgeHub.
- To join the new spots, new collators need to put down 50 KSM.

WHO: The proposal is a collective effort by ecosystem collators.

WHAT: Decentralize Kusama Asset Hub and Kusama Bridge Hub by leaving 2 Parity invulnerable collators on each chain, making 8 community collators on Asset Hub invulnerable, and creating an additional 6 permissionless slots on Asset Hub and BridgeHub.

PRICE/TIMEFRAME/RESOURCES: Any new collator can join by placing a bond of 50 KSM once the referendum is enacted. No specific timeframe or additional resources mentioned.

Further decentralize collator set on Kusama system chains

- A referendum was executed on December 12, 2022, to lower the `min_untrusted_score` in Kusama.
- This change was made to address a mass slashing incident.
- The new `min_untrusted_score` was calculated by averaging the last 30 election scores and halving them.
- The proposal updated the minimum untrusted score to more sensible and secure values.
- The change ensures that weak election solutions are not accepted by the network.
- This helps maintain the security and stability of the Kusama network.

Update elections' minimum untrusted score

- A proposal wants to change the minimum commission rate for validators from 3% to 10%.
- The goal is to help validators cover their costs and keep the network strong.
- Right now, validators earn very little money, sometimes less than $100 a month.
- If the commission rate goes up to 10%, validators could earn more money, like $240 to $480 a month.
- This change won't affect how much KSM is created (inflation rate).
- The proposal is not permanent and can be changed if KSM prices go up a lot.
- The idea is to make the network more reliable and secure for everyone.

**WHO:** The proposer

**WHAT:** Adjust validator minimum commission rate from 3% to 10%

**PRICE/TIMEFRAME/RESOURCES:** Not specified.

[10] Origin: StakingAdmin