dude, the evidence as said is that the sum of "accepted" blocks of the two DevFee workers reported in miner status page, was in some case nearly half of my main worker URL! Some other miners reported "just" 20-25% of DevFee blocks...

Also the TX/RX packets counter related to destination IPs of my legit and dev workers (all targeting SlushPool) shown in MikroTik router, was matching the same percentage shown in miner stat page.

Then, the active workers graph on SlushPool dashboard shown a zig-zag shape that means my legit worker went down for prolonged periods before resume...

I also did a test to "tarpit" forward traffic to Dev workers destination addresses (with /ip/filter rules) just to delay traffic reducing efficiency (and thus priority) without killing the sockets, and it partially worked! I mean the number of "accepted" blocks has reduced drastically, but after some minutes the two DevFee workers turn to "death" and the miner automatically reboots in an endless loop..

I'm sorry I didn't take screenshots to prove what I'm reporting, but I've run the test for the whole last night and today my priority was to resume ASAP the Braiins OS firmare! You may easily replicate this condition by yourself, but I suggest to run at least 3-4 miners at once for a couple of hours.

Here the screenshot of last night SlushPool dash showing workers drops: https://ibb.co/MfFm4Q6

I want to heavily complain with Awe Miner support as they are legitimating a scam tool spoiling their trust and reputation!

This firmware itself is not so bad (nothing revolutionary ever seen so far though), but in my opinion AM should distribute an "hack-free" verified version to their licensed users...