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.
|
|
|
Where are you at? is that USD? What did I offer hosting for a while back? Cause I'll do the same for you till fall with my second 30a 240 line. Maybe two or all three will fit?
Oh philip that batch of psu's are shipped already. I think our broker did well know more when it lands.
We have another 4 hours till a "morning block". -ckpool likes to start the day off right. Block? %
I'm in .au which means that's about 30c USD/kWh. I don't have the time and care factor to pay for and try and manage remote miners. I'd rather just sell them. Thanks though.
|
|
|
Same here as the heatwave continues except Avalons punch right through it. 87 temp and humidity in the basement all summer long boards at 90C and loving it. This A721 miner just turned 3 years old.
It's not a matter of functionality as the T1s work perfectly... it's the 43c/kWh electricity rate. I only mine when they're being used as heaters.
|
|
|
And now the weather's improved down South here so much that I again can't afford to leave any miners on. Anyone want to buy 3 Dragonmint T1s?
|
|
|
My miner keeps showing a crapton of accepts.... what is this? Feedback that you're mining.
|
|
|
starting to get worried here fellas What exactly are you worried about? We have 140PH on board and are only just over 100% diff on the current block.
|
|
|
AH HAH!
Does cksolo have asicboost upstream? i donot have latest version dammit thank you for quick reply
Yes it does. Hey -ck,
I just wanted to tell you... You're awesome.
Much Love Brother <3
Thanks man, but I'm not into guys. Cheers
|
|
|
Hey -ck im trying to add a dragon t1 to my ckproxy what do i need to put on the url line for it to connect? i put stratum+tcp://192.168.0.12:3334 didnt like it i put 192.168.0.12:3334 didnt like it im using this (192.168.0.12:3334) on my s9's and they connect fine Do you have the latest ckproxy from git to ensure you have working support for asicboost and are connecting to a pool upstream that has asicboost?
|
|
|
The rules of the mining section are clearly outlined, more explicitly than any other area of the forum: https://bitcointalk.org/index.php?topic=2415854.0We moderate thousands of threads, we cannot be expected to explain the rules in private that are explicitly outlined every time someone breaks the rules.
|
|
|
On the solo.ckpool.org website it says: All you need to confirm you are mining to your own address is to examine the coinbase and template sent to you over stratum.
Just out of curiosity, could someone tell me how I can confirm this? i.e. how can I examine the coinbase and template sent to me over stratum? I'm running an S9 solo. Just testing my luck I believe there may be online tools to do so, but you can do it yourself with the latest version of cgminer and your own bitcoin daemon, using cgminer's --decode option. The instructions are with cgminer and in one of the last posts on the cgminer thread as well, but you'll need a linux box and a bit of know how to get it going.
|
|
|
Pretty much as I've expected from Halong from the very start and stated here from day-1 of the thread. The one single Kudo I'll give them is that they actually delivered a product that closely met their initial specs -- aside from requiring pool support of AB which they failed to mention to Investomers who pre-ordered and only told the public about a month or so before miners were delivered.
I still tend to think that Halong was a testgoat/shell corporation backed by Inno just to see if a miner using AB would be a salable item and supported by enough pools to be viable: If pools refused to support it only Little Dragon LLC and Halong would get the black eyes.
Given Inno has released firmware for the T1 that rebrands it with the innosilicon logo I would say you're spot on! As I said earlier, Halong is not Inno, nor was it backed by Inno. Halong was standalone with bold goals that contracted Inno to create their hardware. Things did not go according to plan. Inno are now running with a chip they made for Halong. I doubt you'll hear from Halong as an entity again. China and patent laws are fun things.
|
|
|
Noticed the graph update. Is it looking how you want it or closer at least -ck?
Yes it is. Note that the graph only does anything if you leave the page up on your browser.
|
|
|
Currently 54.7. At current network difficulty, our overall hashrate moves extremely slowly.
|
|
|
we are under 85ph what happened?
The current hashrate is seriously fucked up and no representation of the pool's performance of late. Honestly I have no idea why.
|
|
|
The current hashrate is seriously fucked up and no representation of the pool's performance of late. Honestly I have no idea why.
|
|
|
I should travel more if this is the case. So long.
|
|
|
That is now officially our luckiest 24 hours by far, just as I have to stop mining myself since the weather is warming up, and stop getting any rewards myself soon...
[2018-09-06 18:32:03.358] Possible block solve diff 30017888435090.492188 ! [2018-09-06 18:32:03.548] BLOCK ACCEPTED! [2018-09-06 18:32:04.046] Solved block 540231 by 1LKB9eyRsCktjtZ1wjsHERNipieT3nDTA1 [2018-09-06 18:32:04.046] User 1LKB9eyRsCktjtZ1wjsHERNipieT3nDTA1:{"hashrate1m": "195T", "hashrate5m": "185T", "hashrate1hr": "179T", "hashrate1d": "173T", "hashrate7d": "166T"} [2018-09-06 18:32:04.046] Worker 1LKB9eyRsCktjtZ1wjsHERNipieT3nDTA1:{"hashrate1m": "195T", "hashrate5m": "185T", "hashrate1hr": "179T", "hashrate1d": "173T", "hashrate7d": "166T"} [2018-09-06 18:49:24.788] Hash for block height 540231 confirms block was CONFIRMED
"diff": 21.3
Small miner! https://btc.com/block/540231
|
|
|
|