Going out for a whisky tasting tonight. The blocks should come tumbling!
|
|
|
[2018-07-24 16:19:55.781] Pool 2 message: Block 533447 solved by 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX.ms27x73 @ ckpool.org! congratulation it's not a block until it's a confirmed block "solvedby": "3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX", "date": "[2018-07-24 14:19:54.173]", "hash": "0000000000000000002486f411037311ae477671702d750906970d9114df2263", "shares": 17024539438787, "diff": 328.7 confirmed by: 533,448 (00000000000000000006f520c533b1475acf94bef71a49815bb9330775a02aac) ugg a 328% Thankful that is over. I started looking for a support group instead of this support thread. With that, pool average now 114.54705882 [2018-07-24 14:19:53.908] Possible block solve diff 7705791223912.064453 ! [2018-07-24 14:19:54.072] BLOCK ACCEPTED! [2018-07-24 14:19:54.665] Solved block 533447 by 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX.ms27x73 [2018-07-24 14:19:54.665] User 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX:{"hashrate1m": "36.3P", "hashrate5m": "36.1P", "hashrate1hr": "35.8P", "hashrate1d": "31.7P", "hashrate7d": "14.5P"} [2018-07-24 14:19:54.665] Worker 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX.ms27x73:{"hashrate1m": "18.9T", "hashrate5m": "19T", "hashrate1hr": "17.8T", "hashrate1d": "13.3T", "hashrate7d": "3.71T"} [2018-07-24 14:34:34.686] Hash for block height 533447 confirms block was CONFIRMED
https://btc.com/0000000000000000002486f411037311ae477671702d750906970d9114df2263About fucking time is all I can say.
|
|
|
That T2 turbo getsALLEGES an impressive 75W/TH in efficiency mode = 18TH@1350W The higher performance modes are less efficient.
Fixed that for you.
|
|
|
We now have more hashrate than kano pool, if this after effect of the whale's visit holds.
please don't mention it. but we are at 218ph and they are at 206ph You're supposed to ask: block?
|
|
|
And they're gone without finding a block A block popped up in solo instead. However we seem to have gone up in hashrate concurrently anyway.
|
|
|
Block! [2018-07-22 17:22:20.193] Possible block solve diff 23683866120071.511719 ! [2018-07-22 17:22:20.288] BLOCK ACCEPTED! [2018-07-22 17:22:20.297] Solved and confirmed block 533171 by 1H67vwBC97j3vgJzFoyXxQzU1YghgQxHFK [2018-07-22 17:22:20.297] User 1H67vwBC97j3vgJzFoyXxQzU1YghgQxHFK:{"hashrate1m": "3.03P", "hashrate5m": "2.35P", "hashrate1hr": "1.93P", "hashrate1d": "298T", "hashrate7d": "58.3T"} [2018-07-22 17:22:20.297] Worker 1H67vwBC97j3vgJzFoyXxQzU1YghgQxHFK:{"hashrate1m": "2.98P", "hashrate5m": "2.36P", "hashrate1hr": "1.93P", "hashrate1d": "297T", "hashrate7d": "58.2T"} [2018-07-22 17:22:20.298] Block solved after 3445508972477 shares at 66.5% diff
https://btc.com/0000000000000000000be26df80d6659e3f7ed21dc4d021ff543fe9352fd601c
|
|
|
A big pool failover has made the hashrate hit new record highs. Here's hoping we get some blocks while they're here.
1 16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W 116PH/s 7.44PH/s 1.08PH/s 3 153,128,698,502 116011120086 100% 152,665,090,361 0.07389008 is he still here? Yes he is. I know who it is too since he's been communicating with me and they'll be here for at least half a day.
|
|
|
A big pool failover has made the hashrate hit new record highs. Here's hoping we get some blocks while they're here.
|
|
|
Can someone clarify the ramp up/ramp down again for me? I'm a small miner and have less than 100 gh at the moment. I've been mining here for months and managed to earn $1.06 as of a few days ago (not sure my herp/derp numbers as this was from the computergenie site.
Anyway, I get a problem with my miner and had to take it offline for 48 hours before I could start it again... Only to see my prior work is essentially erased and now I'm sitting at $0.05 in pending payouts.
So my question is if it is even worth my time mining here. I can't guarantee my miners won't have downtime in the months to years it will take to get in the payout pool, and if my prior work gets superceded by the guys with the real hashrates in only a few hours I will never earn a payout.
I don't expect to turn a profit mining, I do it to support the network but if I'll never even get a miniscule payout I might as well join the solo pool and give up here.
I would argue that 100gh of gear should solo mine Your numbers are tiny the power used is more then the 3 cents a day you would earn. At 3 cents a day it will take you more then a year to get to 10 dollars which is when you would be paid as I think we are paying at about the 10 dollar level. You start getting into the queue for a payout once you've accumulated the dust limit which is only 5640 satoshi or 0.00005640 BTC, so much less than 10 dollars, but on average small miners are postponed about 11 blocks at the moment from when they hit the payout limit.
|
|
|
Can someone clarify the ramp up/ramp down again for me? I'm a small miner and have less than 100 gh at the moment. I've been mining here for months and managed to earn $1.06 as of a few days ago (not sure my herp/derp numbers as this was from the computergenie site.
Anyway, I get a problem with my miner and had to take it offline for 48 hours before I could start it again... Only to see my prior work is essentially erased and now I'm sitting at $0.05 in pending payouts.
So my question is if it is even worth my time mining here. I can't guarantee my miners won't have downtime in the months to years it will take to get in the payout pool, and if my prior work gets superceded by the guys with the real hashrates in only a few hours I will never earn a payout.
I don't expect to turn a profit mining, I do it to support the network but if I'll never even get a miniscule payout I might as well join the solo pool and give up here.
Work is not "erased". Your payout simply dropped from not contributing for 48 hours so you'll get paid for all the shares you submitted before that and any you submit after that. There is no such thing as "superseding" someone else's work. It's silly to worry about downtime thinking that somehow you won't get paid for it - of course you won't get paid for the period you're not mining... but it has no effect on the period you are mining for. The ramp up/down is about 2 weeks long. If it's not worth mining here, then it's not worth mining ANYWHERE with such a small hashrate. This pool has the fairest small miner/dust payout management you'll find anywhere.
|
|
|
I don't think some people will ever do the math. I hear about people mining in places where the electricity costs are .20/kwh and they are running something like an S7 and they wonder why they aren't making any money let alone getting any kind of a payout at their pool of choice. Once it is pointed out to them they shouldn't be mining with an S7 where electricity rates are high, they usually reply that mining is just a hobby to them. Go figure.
This is not as simple as people are being stupid by the way. When I first started mining, I was mining with GPUs that cost more in electricity to run than the worth of BTC it earned at the time. We did it for many reasons; a combination of it being fun, interesting, challenging, we felt like we were contributing to the network and bitcoin growth on the whole, and we earned some bitcoin that may or may not have been worth something in the future. We did NOT just bet on bitcoin's value going up as a way of earning money. If you are mining at a cost equal to or greater than it earns you in bitcoin, and doing so for "profit", you are betting on the value of bitcoin going up - and it's the hardest possible way to earn bitcoin given that equation; it's more effective to just convert $ to BTC, but then you lose all the other aspects I mentioned earlier. So mining with an S7 or 2 or 3 at a loss is not as stupid as it appears really, but mining with hundreds of them thinking you're earning money probably isn't the smartest thing in the world to do...
|
|
|
Looking at the BTC.com page and the CKPool stats, one has to smile A trend is developing...... could it be a block a day keeps the doctor away? But I'm still here... must be some other doctor.
|
|
|
Block!
[2018-07-19 18:23:17.489] Possible block solve diff 5653866502445.497070 ! [2018-07-19 18:23:17.601] BLOCK ACCEPTED! [2018-07-19 18:23:17.612] Solved block 532663 by 1ME5MsDjRUide4AHFpWRrAWnghZsxYh4f2 [2018-07-19 18:23:17.612] User 1ME5MsDjRUide4AHFpWRrAWnghZsxYh4f2:{"hashrate1m": "11.5T", "hashrate5m": "12T", "hashrate1hr": "13.8T", "hashrate1d": "13.8T", "hashrate7d": "13.8T"} [2018-07-19 18:23:17.612] Worker 1ME5MsDjRUide4AHFpWRrAWnghZsxYh4f2:{"hashrate1m": "11.5T", "hashrate5m": "12T", "hashrate1hr": "13.8T", "hashrate1d": "13.8T", "hashrate7d": "13.8T"} [2018-07-19 18:24:19.974] Hash for block height 532663 confirms block was CONFIRMED
A small miner found it! https://btc.com/00000000000000000031c8a3e6a01c4397759c462f0d1bd66d24a370453933f5http://ckpool.org/blocks/532663.confirmed
|
|
|
There is no legit link for any windows binary any more. The only legit ones were on my website, and antivirus scans falsely tagged them as malware and there was no way to appeal the tag so I've given up on windows binaries entirely and removed them all from my site. Anyone mining today should be mining with linux and most hardware is using a controller device that already runs linux.
|
|
|
Whats the best way to calculate average pool luck? Isnt there a website that compares like CK, Kano, Slush ect somewhere and shows whos lucky and whos not?
Organofcorti used to have an excellent blog that he'd update monthly with all sorts of great statistics along with regular other analytical articles. However, then he had a baby and had no time to waste on free shit for the bitcoin world that no one valued enough to donate to him so he's abandoned it. No one else has taken up the baton to replace him on that work - 95% of miners are big housed corporations with deals with their pools and don't give a shit about such useful information. His blog no longer even exists.
|
|
|
We got a block!
"solvedby": "36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V", "date": "[2018-07-18 02:18:24.765]", "hash": "0000000000000000002d0773eb2f3941848bcbc6c9affb55b94a0ecd2b24fe7a", "shares": 18019747098717, "diff": 348.0 [2018-07-18 02:18:24.531] Possible block solve diff 6250860075537.911133 ! [2018-07-18 02:18:24.719] BLOCK ACCEPTED! [2018-07-18 02:18:25.055] Solved block 532376 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0 [2018-07-18 02:18:25.115] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "113P", "hashrate5m": "113P", "hashrate1hr": "112P", "hashrate1d": "109P", "hashrate7d": "102P"} [2018-07-18 02:18:25.115] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "83.6P", "hashrate5m": "83.5P", "hashrate1hr": "82.8P", "hashrate1d": "79.6P", "hashrate7d": "72.8P"} [2018-07-18 02:18:52.217] Hash for block height 532376 confirms block was CONFIRMED
https://btc.com/0000000000000000002d0773eb2f3941848bcbc6c9affb55b94a0ecd2b24fe7ahttp://ckpool.org/blocks/532376.confirmed
|
|
|
The pool does not care about different speed miners using the same name as they will all be aggregated together. But that said -- not sure what effect that will have on the diff each miner uses. The aggregate hash rate will be the sum of all miners under the name and I suspect that will result in *all* of the miners using higher than optimal diff.
Each connection has its own diff so it doesn't matter if you use the same workername. Using different workernames is only there for the convenience of the user. If it's of no utility to you then just use the same workername.
|
|
|
That's just ridiculous... It was bad enough when they kept flagging cgminer as a fucking trojan.
|
|
|
Time to fire up the BBQ and break out a bottle of red then...
|
|
|
|