Yes it's correct. Mining bitcoin on GPUs and CPUs became obsolete 4 years ago. |
|
|
|
Let's not labour on what other pools are doing shall we?
Yep, I agree  Better to focus on building up pool.ckpool, attract more miners etc.. this should do it!  Hah that looks like the imagination episode. Let's all imagine what it's going to be like when we start finding blocks. |
|
|
|
and another. He hit 1 thurs, 2 fri and 1 sat. Wonder what kind of hashrate he has. Whatever the answer is, one thing's for sure: Mr Shit Arse has more hashrate than us. Let's not labour on what other pools are doing shall we? |
|
|
|
I was just cleaning up some bookmarks and noticed that my old saved title of this thread was this: BITMAIN announces Antpool: Pushing forward DecentralizationIt's interesting that somewhere along the line they removed that "Decentralization" part from the thread title, just like they're trying to do in real life  Pretty sure I edited out for false advertising. |
|
|
|
 so, it's not merged in the code ? What's not merged, BIP148? Of course not, there isn't remotely universal acceptance by core devs. I understand BarryCoin is having the same problem Still a Barrycoin supporter, ck?  Who's barry? I certainly did not support his agreement's proposal in the form they agreed to, only the concept of 2MB+segwit, but that's all offtopic here. |
|
|
|
|
Original poster hasn't come back and question answered enough. Locking thread.
|
|
|
|
Caveat: I understand the site is minimalistic and am not complaining about that at all but,
I glance at the stats every now and then (maybe once a day) to make sure all the miners are running. The rates seem to be correct but my 7 day always seems to be low (as if one is down). Is that a bug and I should ignore the 7d and just watch the 24h?
"hashrate1m": "111T",
"hashrate5m": "107T",
"hashrate1hr": "104T",
"hashrate1d": "104T",
"hashrate7d": "89.6T",
"lastshare": 1497624984,
Have you been mining here for 4 weeks? The value is an exponentially decaying average with a time constant of 7days which isn't quite the same as your average for only the last 7 days. It's close enough to the same value normally that I let people assume that's what it is. |
|
|
|
so, it's not merged in the code ? What's not merged, BIP148? Of course not, there isn't remotely universal acceptance by core devs. |
|
|
|
That moment when you see that "poopbut" finds a block using ckpool and you're mining in ck's own pool but you can't luck into a block...
Fucking poopbut and his fucking ckpool blocks. He should be mining here dammit. For those who don't know what the fuck we're talking about, some entity calling himself poopbut is mining with ckpool software. https://www.blocktrail.com/BTC/block/0000000000000000004258d80aee673833c9b2e93dcd1a20525fbd37bc95c8d5See encoded coinbase message for his name and ckpool signature. He doesn't even know how to change the default block size in bitcoind, leaving it at a pitiful 750kb. Come on damnit, we need to find a "lucky" block for ourselves. The Chinese say 8s and 6s are lucky so we need to find a block by 88.6% diff. |
|
|
|
|
Just reminding everyone we're still here, even if we're not trying to mine Jihancoin.
Diff rises again soon so we're forever asymptoting towards 100% but never quite getting there, so let's just find a block and not worry about that hurdle.
|
|
|
|
Like I said earlier, I don't want to see this thread turn into another pointless flamewar with everyone posting their own opinions about segwit/core/blocksize/BU/Ver/classic/XT/fuckme . Stick to the topic please.
OK, so (given what you deleted) the topic isn't about the long-term scalability and usefulness (or lack thereof) of segwit (and thus the crux of the agreement); what is the topic?  What the progress of solutions to the stalemate are and what the current state of support, likelihood of acceptance is and so on... There are plenty of flamewars elsewhere to discuss people's personal opinions regarding the rest. |
|
|
|
|
Like I said earlier, I don't want to see this thread turn into another pointless flamewar with everyone posting their own opinions about segwit/core/blocksize/BU/Ver/classic/XT/fuckme . Stick to the topic please or I'll just delete your posts.
|
|
|
|
My stats on there don't seem to be changing but my miners are mining which is odd. Post here or PM me the address. |
|
|
|
Random ~related factoid: Gbminers (2% of the network) just mined a segwit block. https://blockchain.info/block/00000000000000000010dd7c2f8762277fe958ac983a4069d7e6767970c45515Now I'm aware they use ckpool and there's the possibility they simply upgraded to a more recent ckpool which enables segwit by default but they would have to be complicit in using a recent enough core bitcoind which is segwit capable, so I'm guessing it's a conscious choice and not by accident. However they're missing the default commitment suggesting it's not the latest ckpool. They consciously did remove their EC flags in their coinbase which pretty much confirms it. Perhaps this will be the ultimate answer... after all the shouting and threats and attacks, everyone will one by one simply enable segwit after all...? |
|
|
|
Thank you for that information. I'm getting this error when I try that. cgminer: --icarus-timing=short: unrecognized option. I tried to download from here http://ck.kolivas.org/apps/cgminer/ but it flagged as malware, can anyone confirm this is the correct link? the 4.10 version? It's the correct link and definitely not malware. The icarus timing feature is irrelevant today and you shouldn't be using it. Thanks, I've now tried with and without the icarus command, it seems to make no difference. What I can't understand now is why the speed is still at 336Mh/s regardless of the speed figure, I tried 200 and 225, I believe I should be getting 1.6 and 1.8Gh/s at those settings. It's seeing it inappropriately as an asicminer usb stick which did 336. Try a powered hub, pull it out and put it back in a few times and see if it initialises differently. |
|
|
|
i m running cgminer with 5 gridseed asic usb miners on a raspberry
There is no gridseed nor altcoin support in the official cgminer so you must be running an unofficial fork of cgminer which means you need to seek support from them. |
|
|
|
Thank you for that information. I'm getting this error when I try that. cgminer: --icarus-timing=short: unrecognized option. I tried to download from here http://ck.kolivas.org/apps/cgminer/ but it flagged as malware, can anyone confirm this is the correct link? the 4.10 version? It's the correct link and definitely not malware. The icarus timing feature is irrelevant today and you shouldn't be using it. |
|
|
|
|
Show Posts
