This could be just a technical problem with your miner configuration. I had similar problem yesterday (no coins stolen, I found this problem very soon, my miner was highlighted in red that it mines to the pool but there was no explanation why and it was not easy to find what is wrong).
DOGE address is configured in password field at ltc.tbdice.org. Format is "x:DOGEaddress" but it can be more complicated. When DOGE address is misconfigured, pool donates reward to some pool DOGE address.
1) check that DOGEaddress in password field is after "x:"; "x" could be just "x" or definition of mining difficulty, like "diff_16384"
2) check how password is passed to the miner. Some miners combine username and password in one parameter, like
cgminer -O "$USERNAME:$PASSWORD"
(or --userpass). This doesn't work with this pool because ":" is used as separator in password field! You have to pass username and password in separate arguments, like
cgminer -u "$USERNAME" -p "$PASSWORD"
(or --user and --pass)
The problem with pool ltc.tbdice.org is that it doesn't report miner status in good way and it is difficult to find such configuration problem... Other problem is that it uses ":" as separator in password field! Other pools, like ZERGpool, use "," as a separator and that is better option...
This works:
cgminer -o stratum+tcp://tbdice.org:13333 -u "LUNyycVonDH9aQMZn1fxyUeu8N3yS8w7ud.RIG1" -p "x:DFeviTwbDbJXgjPRS6zxe74Z4hodvRrTKP:yourmail@somedomain.com:type=51"
This doesn't work, password is "damaged":
cgminer -o stratum+tcp://tbdice.org:13333 -O "LUNyycVonDH9aQMZn1fxyUeu8N3yS8w7ud.RIG1:x:DFeviTwbDbJXgjPRS6zxe74Z4hodvRrTKP:yourmail@somedomain.com:type=51"
I had this problem with a small ASIC miner, I only configure pool parameters to the HTML form and firmware starts cgminer in the background; firmware started cgminer with "-O $USERNAME:$PASSWORD" and this damaged the password field, and pool tbdice received password without DOGE address... I had to login to my ASIC miner (manufactured by AntMiner) and modify the script in the firmware, the script that started cgminer. It is possible that other miners from AntMiner
have similar "bug".
I have only one miner so it was "easy" to find that something is wrong. I think that when miner has several devices those mine to the same wallet and several of them are configured correctly and one or two have some configuration problem, it could be difficult to notice the problem...
BTW, I am new with tbdice pool, I have not found any block yet. It is possible that there is some other problem and found block is sent to wrong wallet...
