It has nothing to do with Consensus Rules, I think. The problem is that the devs were never able to enforce rewarding the masternodes, which is necessary and something that other masternode coins are able to do.
But I understand you don't want to spend more time on this coin without more involvement of the community .

Cheers

The POS reward is 1.20 8BIT, which is 0.32 8BIT for the stake wallet and a reward of 0.88 8BIT for the masternode. That is the reason to set up masternodes. But the stake wallets get 1.20 8BIT and don't reward the masternodes, so there is no incentive to set up a masternode. Which is a problem for a masternode coin.
The more coins you have in your wallet, the more rewards you will receive, since it depends greatly on the network weight and probably a bit of luck, but I see a lot of the same addresses getting the rewards and I'm not talking about 0.32 8BIT, but 1.20 8BIT. So they are extremely lucky or have a high network weight and they certainly cheat by not rewarding the masternodes.

I know the cheating was already a problem 4 years ago, but I don't think it was ever 39 out of 40 blocks...

What about all those people that don't pay masternodes? Or wallets like 8c3LGTpyG2JJsx52CsWmMEoGcnYQc15iuv that get extremely lucky or have an immense network weight, so they receive 4 payouts in 23 min? Or 8aKGu54w5jLjSLTmfhfLFUCWDx1ac1WGbV, 3 payouts in less than an hour? Or 8aKGu54w5jLjSLTmfhfLFUCWDx1ac1WGbV, 3 payouts in 20 min? All 1.20 coins per payout...

The problem is that there are a lot of stake wallets that don't pay rewards to the masternodes. The last 2 weeks it got worse; 80% of the time, your masternode won't get a reward.

I'm getting 9kh on my 290's: I 18, TC 24576, w 6. But I'm getting 7% rejects, have to finetune a little more.

I bought some S3's a few weeks ago from someone and I accidentally configured a static IP address on the LAN interface instead of the WAN. Since my Fing app didn't discover the new static address, I rebooted the device, but after that, I couldn't connect to the S3 anymore. The web GUI isn't available, ssh doesn't work and even a ping is not working. However, the device is hashing and I can see in Fing that it still has the same ip address that was given by my router the first time it connected.

I've tried to reset the device in every way I could find on the internet, but the device just won't reset to factory defaults. Every time I reboot, it starts hashing again and gets the same IP address. I gave my laptop that ip address and rebooted the S3, but it doesn't get another address, it just doesn't hash, until I change the settings on my laptop and reboot again.

Any help would be much appreciated.