hey cK
are you allowing miningRR to mine on solo?
if so how do i get it going?
Sure. Either the regular mining address as it says, which has 10,000 starting difficulty, or port 4334 which has 1 million starting difficulty. I don't know what MRR constraints are on mining diff. |
|
|
|
Hi i want to mine with cgminer-3.7.2-windows, with my 750gtx-ti, yes i know i would probably never get some or little pay outs but i just want to try it out.
No. You will never get any payout whatsoever. Zilch. Nil. Nothing. Nada. You might earn 1 cent in a year. To get into the payout queue might take you 50 years at that rate. Just don't do it at all. Mining bitcoin with a GPU - any GPU, is completely futile. There's a reason I completely stopped supporting GPU mining and consciously removed it from cgminer, so please don't even go looking for support for it. I actively discourage people from doing it because it shares virtually NOTHING with how bitcoin is currently mined and is a futile - and potentially very expensive - exercise. |
|
|
|
Thanks for the heads up. In principle it sounds like a good idea but there isn't a single bit of data that needs to be secure coming from the website. There are no logins, all data is readily available to anyone, and there are no accounts and all statistics are relatively anonymised being tied only with a bitcoin address. Intercepting to read the data which is readily available anyway, and spoofing that data to change something won't achieve anything at all that I can think of? |
|
|
|
I've updated the opening post to more accurately reflect our current hashrate as we seem to be continually leaking miners...  |
|
|
|
CK, can you confirmed that actually I already received all those payout from ckpool? bcoz the indodax exchange asked me to cross check with you first before claiming. thank you
Use a reliable block explorer that will definitively show you. Look for all the coinbase deposits into that address. https://btc.com/14iGADd2pLwe8BxXV4VNeR4T6NBBupA2wc |
|
|
|
question from newbie: - unable to decode the output address - and indodax dont want to credit all payout from CKPool why all the BTC payout from CKPool always got message like this ? unable to decode output address? until today the indodax exchange did not want to credits all my payout from CKpool to my wallet. please advice. my BTC addrs: 14iGADd2pLwe8BxXV4VNeR4T6NBBupA2wc screen captured: https://imgur.com/a/kPEAVS5 Some ancient web wallets wouldn't work with generation transactions because the deposit address was obfuscated and then sent to another receiving address. You need to either choose a better wallet (and everyone should be using their own wallet, not a web wallet or worse, an exchange) or take it up with your wallet provider. |
|
|
|
... a Block Solved indeed - but, seriously after such a wait, did it have to be one with only 56 Tx (transactions)?
Never seen a block with transactions so low...
I guess beggars can't be choosers... We have our block and so on to the next & the next & the next...
Good hashing everyone!
Well, at least the block solve here added another 150 generation transactions... alas that ain't worth anything in transaction fees though  |
|
|
|
so at 223.9 we have over 100 to go to 348.
Waiting for Block Confirmation - BUT: "solvedby": "32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k", "date": "[2018-10-07 03:13:34.720]", "hash": "00000000000000000008b7233b8abb1519d0a1bc6579e209955539c303f3e6b1", "shares": 18841177514981, "diff": 252.7And there it is!!! No new record. Hurray! [2018-10-07 03:13:34.606] Possible block solve diff 32295853758649.984375 !
[2018-10-07 03:13:34.703] BLOCK ACCEPTED!
[2018-10-07 03:13:34.815] Solved block 544704 by 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k.worker
[2018-10-07 03:13:34.815] User 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k:{"hashrate1m": "48.9P", "hashrate5m": "49.5P", "hashrate1hr": "49.5P", "hashrate1d": "48.8P", "hashrate7d": "32.1P"}
[2018-10-07 03:13:34.815] Worker 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k.worker:{"hashrate1m": "45.2P", "hashrate5m": "45.7P", "hashrate1hr": "45.7P", "hashrate1d": "45.2P", "hashrate7d": "28.9P"}
[2018-10-07 03:34:38.635] Hash for block height 544704 confirms block was CONFIRMED
|
|
|
|
Hi i have set everything up and i am mining now. But when i put in my address to check my status i get 404 not found. It has me mining for over a hour now and still not showing up any clue why or how to fix this?
My guess is your hashrate is so extraordinarily low (or non-existent) that you haven't registered even a single share yet. It its showing around 600 Mhash/s with GUIminer. Would that confirm its because i haven't registered a share? Yes, that's an extraordinarily slow hashrate, and my guess is you are GPU mining. Do some reading, and then stop doing that entirely. It's a futile thing to do with bitcoin. |
|
|
|
Hi i have set everything up and i am mining now. But when i put in my address to check my status i get 404 not found. It has me mining for over a hour now and still not showing up any clue why or how to fix this?
My guess is your hashrate is so extraordinarily low (or non-existent) that you haven't registered even a single share yet. |
|
|
|
Happy 200% everyone And back down again thanks(?) to yet another fucking difficulty rise. |
|
|
|
Friends, my miner says the last share was 75 hours ago:
Restart your miner? Looks like you have a problem at your end... |
|
|
|
I was talking about configurations. So just entering the wallet as user is enough just in case luck is on my side one day?
That's all... I was being facetious. |
|
|
|
do I need to do more?
You need a veritable shitload more luck, otherwise you'll end up with nothing. |
|
|
|
Can anyone explain what this exactly means?
"All you need to confirm you are mining to your own address is to examine the coinbase and template sent to you over stratum."
Look back one page on this thread. |
|
|
|
Wherever you may be in the world, it's a good BLOCK day...
"solvedby": "16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W",
"date": "[2018-09-22 13:37:38.354]",
"hash": "00000000000000000024edd8f3a64ffee9eb5eed5c40b1b8732e2bc62b83648e",
"shares": 2586161188904,
"diff": 36.2
Here in N.America - Good Morning!
# $ BTC
[2018-09-22 13:37:38.188] Possible block solve diff 7621922690389.884766 !
[2018-09-22 13:37:38.351] BLOCK ACCEPTED!
[2018-09-22 13:37:38.375] Solved block 542549 by 16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W
[2018-09-22 13:37:38.375] User 16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W:{"hashrate1m": "141P", "hashrate5m": "141P", "hashrate1hr": "125P", "hashrate1d": "66P", "hashrate7d": "14.4P"}
[2018-09-22 13:37:38.375] Worker 16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W:{"hashrate1m": "141P", "hashrate5m": "141P", "hashrate1hr": "125P", "hashrate1d": "66P", "hashrate7d": "14.4P"}
[2018-09-22 13:37:50.033] Hash for block height 542549 confirms block was CONFIRMED
|
|
|
|
Shout out and thanks again to Morktadela, these graphs are pretty slick.  |
|
|
|
solvedby": "16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W",
"date": "[2018-09-21 16:28:52.228]",
"hash": "00000000000000000011295a0bd4892bc3a71643cd9f64c51ea1e4aa9d11e7a6",
"shares": 7002436220062,
"diff": 97.9
Woot! Update: Confirmed [2018-09-21 16:28:52.024] Possible block solve diff 16401257796138.492188 !
[2018-09-21 16:28:52.223] BLOCK ACCEPTED!
[2018-09-21 16:28:52.489] Solved block 542414 by 16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W
[2018-09-21 16:28:52.489] User 16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W:{"hashrate1m": "104P", "hashrate5m": "96.6P", "hashrate1hr": "34.3P", "hashrate1d": "1.93P", "hashrate7d": "1.49P"}
[2018-09-21 16:28:52.489] Worker 16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W:{"hashrate1m": "104P", "hashrate5m": "96.6P", "hashrate1hr": "34.3P", "hashrate1d": "1.93P", "hashrate7d": "1.49P"}
[2018-09-21 16:34:02.169] Hash for block height 542414 confirms block was CONFIRMED
|
|
|
|
|
Website graphs are updated courtesy of Morktadela (thanks!) They should show correct scale now, though you'll need to empty browser caches and reload the page to get them.
|
|
|
|
* -ck drops a pin No, I have no idea why the hashrate is falling. Hopefully it's power issues in disaster affected areas and not big miners abandoning in droves. |
|
|
|
|
Show Posts
