Last time I checked, every other calculator was still using the same hash rate for Groestl and Myr-groestl. In fact myr-groestl is giving you 2x hash on the same card.
Looks like it's waaaay over reporting for some weird reason, both server side and client side (using sgminer) -
Myriad-Groestl (MYR) Groestl. Actual real-time payouts per 10 MH/s are more in line with what GroestlCoin (GRS) is paying out (around 250-260 coins per day). That's mining on
http://myriadcoin-groestl.miningpoolhub.com . I'm now also mirroring on the P2Pool at
http://eup2pool.cryptopools.com:3333/static/ . Will let them go for 24 hours and will report back then with those results.
24 hour results:
Actual gross payouts on
http://myriadcoin-groestl.miningpoolhub.com before the 1% pool fee = 655 coins per 10 MH/s, just slightly under the What To Mine estimate. (My initial preliminary projections were off due to the inordinate amount of time for this PPLNS pool to ramp up.) Not bad. Just about .0025 BTC at current market prices.
The P2P results won't be ready until tomorrow since the payouts are STILL ramping up there (never met a P2P pool that I didn't hate, but let's give it a fair chance . . . at least there hasn't been missing payout periods . . . yet).
Then I'll have to give qubit a test drive . . .
Myriad-Groestl (MYR) Groestl
48 hour results671 coin daily gross payout (before the 1% pool fee)
per 10 MH/s (
adjusted, real, groestl hashrate)
383 coin daily gross payout (before the 1% pool fee)
per 17.5 MH/s (
over reported hashrate)
It's not quite a 2x hashrate over reporting. I calculate that it is closer to 1.75, which is to say, there is a 75% over reporting of the equivalent groestl hashrate. Another way of looking at it is with a scrypt equivalent hashrate, which would be ~1,100 kH/s, or a ~3,300 kH/s X11 equivalent, or a ~500 kH/s scrypt-n giving you a .00229 BTC daily yield. The comparison coins I've mined with same machines/clones with exact same configurations are: GroestCoin, DiamondCoin, DarkCoin, VertCoin, ExeCoin, and DOGE (although DOGE is archive data since I haven't mined it for some time now).
The P2P pool took 36 hours to fully ramp up, so those results will be delayed once again.
And I've now got another “mirror” machine on Myriad-Qubit(MYR) Qubit.
Hope this information is useful.
The Myriadcoin Qubit total 24 hour gross payout before 1% pool fee was 680 coins at an adjusted groestlcoin 10 MH/s hashrate equivalent (in this case, the Qubit hashrate was about 55% of the groestl 'benchmark'). The block find percentage over this time frame was 101.85%
On the side by side mirror machine for Myriad-Groestl over the same time period the gross payout was 670 at an adjusted groestlcoin 10 MH/s hashrate equivalent. The block find percentage over this time frame was 114.64%
Why would anyone mine Qubit? The energy consumption is only about 7% more than Groestl, but does that justify just a few more coins? The machine is worked quite a bit harder than what you would expect from only a 7% increase in power use however. Many people have commented that with Groestl you can play a game while mining, and my testing shows that's not possible with Qubit. So with a lot lighter load on the machine, and lower energy costs as well, Groestl looks to be the clear winner, yet again.
P2P pool mining is by far and away the big winner here. THIS IS THE FIRST P2P POOL I HAVE LIKED!!! 24 hour payouts are now averaging 890 coins (at an adjusted groestlcoin 10 MH/s hashrate equivalent).
So the no-brainer here is to set everything on the Myriad-Groestl P2P using the traditional pool as a failover. I'm going to keep things evenly divided for another few days testing before going all in though.
(I'm not even going to bother testing Skein as I've read that same machine, same config results yield little over half what Groestl produces, and my math based on simple division of theoretical coins paid out daily by the network hashrate bears that out - not worth the time.)
BTW, anyone notice that DGB is still averaging less than 200 blocks a day. In fact, less than 100 blocks in the last 24 hours. They're beginning to recognize the issue, but they're still trying to convince us that it's due to multipool attacks.