So I'll admit that I momentarily gave in to temptation and posted the following post in the CM thread in response to what miners are reporting as "an unusual reduction in profit for the last few days". I left it up for a couple minutes and then decided to delete it. I figured though that it was better not to kick the hornets nest, even after we secretly played soccer with it.
I'll share it here for all to see, as it brought me a lot of joy to write. For your viewing pleasure:
My "profit graph" just tanked by half and the hashrate (which was "suppressed" for a good while) went back to "normal". I guess whatever we were mining the last few days is not profitable anymore at all, so we switched and the next best coin that we're mining now is not that profitable either.
I wonder what that could be
Hmmm... if I was going to take a stab at it, I would say part of the reason is that CM has been mining on a fork of a coin for 4 days now. I guess the op didn't take the time to watch over his pool and update the client. Sucks for the miners who thought the pool was making them money with their wasted 4GH worth of mining power during that time. It's actually pretty funny running the old client and watching the pool plug away at block after block on the defunct chain.
Oh, and in case you needed proof:
guldencoind getbestblockhash
4ab117917969d896e962eac3d231e4a0cd7d6e52350872336927f356a474b0b9
[root@dell ~]# guldencoind getblock 4ab117917969d896e962eac3d231e4a0cd7d6e52350872336927f356a474b0b9
{
"hash" : "4ab117917969d896e962eac3d231e4a0cd7d6e52350872336927f356a474b0b9",
"confirmations" : 1,
"size" : 249,
"height" : 194492,
"version" : 2,
"merkleroot" : "6418cbb4e728bd63cdcb683571b2d420a371cf50e25d05223bd4ad2d3760682e",
"tx" : [
"6418cbb4e728bd63cdcb683571b2d420a371cf50e25d05223bd4ad2d3760682e"
],
"time" : 1422847904,
"nonce" : 15892272,
"bits" : "1c0116fb",
"difficulty" : 234.90891779,
"previousblockhash" : "b7396a43f6a92e2483b29b4de85cda44c69781b0b7bcc5652630ee2abb513a2c"
}
[root@dell ~]# guldencoind gettxout 6418cbb4e728bd63cdcb683571b2d420a371cf50e25d05223bd4ad2d3760682e 0
{
"bestblock" : "4ab117917969d896e962eac3d231e4a0cd7d6e52350872336927f356a474b0b9",
"confirmations" : 1,
"value" : 1000.00000000,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 e96200b2643f6188c66305cd7b3a28923ab0bf0e OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914e96200b2643f6188c66305cd7b3a28923ab0bf0e88ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"Gf7wGAwJGDLfoHcNCRLKZqpk2EQU5ixA6c"
]
},
"version" : 1,
"coinbase" : true
}
[root@dell ~]# guldencoind getmininginfo
{
"blocks" : 194497,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 324.09852217,
"errors" : "IMPORTANT: Shut down this wallet and download the new version 1.3.1! Very important and mandatory update!!\nBELANGRIJK: Sluit deze wallet af en download de nieuwe versie 1.3.1! Zeer belangrijke update!",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 4783660604,
"pooledtx" : 0,
"testnet" : false
}
Absent op is absent. Too bad for the miners. I wonder if they op will pay for the wasted days of mining... if he even acknowledges his lack of responsibility for his own pool.
-Fuse
Cheers to us for hitting CM where it hurts.-Fuse