Dear Moonbeam Community,

first I want to give you quick info about what this proposal would do:  
It would trigger a `parachainStaking.goOffline()` Extrinsic in the name of the "Moonbean" Collator (0xbD8027E8463843911Ed5503f339C992E728BD471).
  
  
**What does this do?**   
It temporarily removes the mentioned Collator from the active set. 
He could always return by manually triggering a `parachainStaking.goOnline()` and would not loose his nominations.
  
**Why do I want to do this?**  
This Collator hasn't produced a single block in the last 7 days. 
The Moonbeam Network is slowed down when a Collator is included in the active set that doesn't produce blocks. 
Also, their delegators do not gain any rewards.
  
  
**Background information on why this node is not producing blocks:**  
Back in July, the [release notes of node version v0.25.0](https://github.com/PureStake/moonbeam/releases/tag/v0.25.0) had ⚠️ important notes about ⚠️ breaking changes and instructed all the Collators to generate new keys to obtain a `rand`-key for the VRF (Verifiable Random Function).
It was also oftentimes discussed in the Collator channel of the official Moonbeam Discord that this step is mandatory.
  
With the [latest runtime upgrade to version 1802](https://moonbeam.polkassembly.network/referendum/62) Collators without a `rand`-key were no longer able to propose blocks to the Moonbeam chain.
A total of 5 Collators have been affected of which most acted quickly to get back operating. 
You can identify these Collators by the "missed blocks"-indicator (⚠️) on the [StakeGLMR Website](https://stakeglmr.com/).
  
As soon as we realized the problem we stated what needs to be done in the Collator channel and also tagged & DM'ed these operators.
The individual targeted by this proposal is anonymous and placed no contact information to get in touch.   
This incident clearly shows that he neither participates in the Collator discussions nor has any kind of monitoring or alerting in place (which is absolutely mandatory for a node operator).
  
  
Best regards,  
Sik | crifferent.de



Dispatches a function call with a provided origin.

The dispatch origin for this call must be _Root_.

# <weight>
- O(1).
- Limited storage reads.
- One DB write (event).
- Weight of derivative `call` execution + T::WeightInfo::dispatch_as().
# </weight>

- The proposal is to temporarily remove a Collator from the active set.
- The Collator hasn't produced any blocks in the last 7 days.
- This slows down the Moonbeam Network and the Collator's delegators don't get rewards.
- The Collator didn't generate new keys as instructed, so they can't propose blocks anymore.
- The Collator doesn't participate in discussions or have monitoring in place.

#66 Chill "Moonbean"-Collator After 1 Week Of Unresponsiveness

No Active Proposals