@Earl_Vadim:
I do not know what you're doing.
-> Make your own batch with the start command and move it into the autostart. I did it that way and it works.
If he is a scammer, he certainly does not make it so easy
@pr0ximus
I am not a specialist, but my theory is:
Your miner has to register at the pool. This happens via a static TCP sequence you can see via Wireshark.
This includes the WalletID and the method "eth_submitLogin".
Starts Claymore DevFee, he signs off. Starts the sequence again but with another WalletID (Claymores - WalletID) and the miner runs for Claymore.
In this sequence, NoDevFee intervenes intercepts the packets and changes the WalletID to yours.
I think stealing shares is just possible at this time. When NoDevFee inserts its own WalletID he gets the DevFee.
So without new login on the pool he can not steal any shares.
Anyone can check with Wireshark where the DevFee goes.
But we will see more in a few hours