Is it still a good idea to mine Dogecoin?
after the static dogecoin block reward implemented today, pool can no longer cherry pick big reward blocks.
Also with the new difficulty algorithm coinwarz and coinchoose are showing different difficulties. and both are incorrect IMHO. Actual difficulty is higher than what both website shows.
Difficulty changes every block now I think or something like that
WafflePool's profit switching system considers each block and its difficulty, reward, exchange depth and price, etc (and throws in a few other offsets). If we are mining Doge, it's because at the difficulty of that block, it was more valuable to mine then the alternatives.
Keep in mind, also, that PoolWaffle has indicated that the new switcher mines multiple coins simultaneously - ala, splitting WafflePool's total hashrate at multiple coins. If you want many miners at once connected to WafflePool, you will notice workers diverge in mining duty on occasion.
This is correct. They also do caching (you'll only notice them changing data every 5min or so), we check literally nonstop. We mine Doge when it is profitable, something else when that something else is profitable, has nothing to do with random block rewards, other than with random block rewards the profitability changed drastically from block to block, now it just shifts slower...
I have no issue with being incorrect; however, there was an announcement on the main waffle site stating that it would be taking advantage of the 2x rewards. Every time the ghash.io jumps, waffle hash loses 20gh. Could be a single miner or could be proxying to ghash. I'm just going on observation and the announcement.
It's a Chinese group - they have posted on these forums as 'sfire' - that is moving the ~20GH/s back and forth. PoolWaffle disabled proxying to GHash as soon as they implemented the tiered bonus scheme.
@PoolWaffle: WafflePool's profitability does seem to consistently climb a bit whenever sfire leaves. Is this really just due to luck? Seems weird to me.
Unlikely due to luck. I mentioned a few posts back about rewriting the stratum endpoints, I think it has something to do with some lag/delays in processing immediately after finding a block, and with 20GHs, that few seconds of delay becomes a much more significant portion of block finding time. Working on rewriting the whole thing now to try to speed it up
