Dear community, 
I was proposing this referendum to scheduleLeaveCandidates&nbsp;on behalf of stake.fish for their 4 Moonriver collator nodes.
stake.fish decided to end Moonriver collation and shut down their infrastructure on 29th of September 2023. It was a rather ungrateful shutdown without declaring a leave-intention on chain.&nbsp; The process to shutdown a collator would usually be four steps:
<ol>
<li>set a timeline and publicly communicate the scheduled exit with the delegators&nbsp;</li>
<li>trigger parachainStaking.scheduleLeaveCandidates&nbsp;</li>
<li>trigger parachainStaking.executeLeaveCandidates after a waiting period</li>
<li>shut down the infrastructure / nodes</li>
</ol>
In this case we stepped straight to 4) and even after direct pings to please exit gracefully the nodes are still in the active set. For the Moonriver network this means decreased performance and longer block times and for their delegators it means missing out on rewards.
In <a href="https://forum.moonbeam.network/t/resolving-moonriver-collator-set-problems/1348" target="_blank" rel="noopener">this Forum post</a> we discussed the general problems with not having offline-chilling or slashing in the parachainStaking pallet and came to a very good long-term solution. We'd still prefer to proactively act on this matter and normalize Moonriver's performance as soon as possible.
Best regards, Sik 🚀

Dear community,  
  

I was proposing this referendum to _scheduleLeaveCandidates_ on behalf of stake.fish for their 4 Moonriver collator nodes.

stake.fish decided to end Moonriver collation and shut down their infrastructure on 29th of September 2023.  
It was a rather ungrateful shutdown without declaring a leave-intention on chain.   
  
The process to shutdown a collator would usually be four steps:

1.  set a timeline and publicly communicate the scheduled exit with the delegators 
2.  trigger _parachainStaking.scheduleLeaveCandidates_ 
3.  trigger _parachainStaking.executeLeaveCandidates_ after a waiting period
4.  shut down the infrastructure / nodes

In this case we stepped straight to 4) and even after direct pings to please exit gracefully the nodes are still in the active set.  
For the Moonriver network this means decreased performance and longer block times and for their delegators it means missing out on rewards.

In [this Forum post](https://forum.moonbeam.network/t/resolving-moonriver-collator-set-problems/1348) we discussed the general problems with not having offline-chilling or slashing in the parachainStaking pallet and came to a very good long-term solution. We'd still prefer to proactively act on this matter and normalize Moonriver's performance as soon as possible.

Best regards,  
Sik 🚀

Send a batch of dispatch calls and atomically execute them.
The whole transaction will rollback and fail if any of the calls failed.

May be called from any origin except `None`.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then the calls are dispatched without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

## Complexity
- O(C) where C is the number of calls to be batched.

- Problem Statement: The stake.fish abruptly ended Moonriver collation and shut down their infrastructure without declaring a leave-intention on chain, causing decreased performance and longer block times for the Moonriver network and loss of rewards for their delegators.
- Significance: The abrupt shutdown without following the proper four-step process disrupts the network's performance and affects the rewards of the delegators.
- Proposed Solution: The post suggests triggering 'parachainStaking.scheduleLeaveCandidates' and 'parachainStaking.executeLeaveCandidates' after a waiting period to normalize Moonriver's performance.
- Expected Outcomes: The proposed solution aims to restore the network's performance and ensure that the delegators do not miss out on rewards.

#37 Initiate removal of the offline stakefish nodes