This council motion, if voted in favour and executed, would remove Blocks United from the collator set and reduze the collator set size by 1.
On 6th of December at 01:00 UTC their collator stopped to produce blocks and was seen offline.
The incident went completely unnoticed by the operator until a community user pinged them on Discord around 35 hours later.
At the time of writing - 09th of December 22:00 UTC - the node hasn't returned to participate in consensus.
I'll attach the uptime and monitoring rules that led to this motion to remove the collator:
We have worked hard for the HydraDX community. Our collator was consistently in the top 3 best-performing, we have tutorials on our blog, like and repost everything on Twitter, have almost all of our tokens staked, and have voted 6x on every proposal from personal wallets.
We believe in HydraDX and the team. We want to be part of the future and help the protocol and platform succeed. I'm not blaming anyone other than our monitoring process. Our bad 100%. We are asking for forgiveness and the opportunity to fail forward.
We didn't have a snapshot and nobody had one to share. The data got large enough that our machine couldn't sync within the window. Lesson learned.
We ask that everyone please vote NO on this referenda #124 and allow us to keep serving HydraDX as a collator.
Edited