Over the past weeks we've seen a lot of volatility in the Moonriver collator set with multiple big entities leaving the field. And it's not always been smoothly executed. 
We have seen multiple nodes from one operator being just abandonned and still included in the active set while being offline for over a month which is unacceptable for the chain performance.

For that reason our [latest and greatest Runtime upgrade](https://forum.moonbeam.network/t/runtime-rt2600-schedule/1372/5?u=dev0_sik) included a new feature that was also mentioned in a [forum discussion](https://forum.moonbeam.network/t/resolving-moonriver-collator-set-problems/1348/2?u=dev0_sik) about the problems described above.

This referendum seekds to enable the markingOffline feature so afterwards everybody from the community will be able to execute an parachainStaking.notifyInactiveCollator extrinsic which temporarily removes the flagged offline collator from the set, after some automated tests to ensure it's not a false-positive.

In case of open questions feel free to comment below or approach me in any way. 

Cheers, 
Sik

Problem Statement:
- The Moonriver collator set has experienced volatility and issues with nodes being abandoned and still included in the active set, leading to poor chain performance.

Significance:
- The problem of offline collators in the Moonriver collator set is unacceptable and affects the performance of the chain.

Proposed Solution:
- Enable the markingOffline feature and allow the community to execute an extrinsic to temporarily remove flagged offline collators from the set after automated tests.

Expected Outcomes:
- Improved performance and stability of the Moonriver collator set by removing offline collators.

#44 Enable the new feature to flag collators offline when not producing blocks