And now it's confirmed [2018-02-05 04:14:42.517] Possible block solve diff 5413901829396.665039 !
[2018-02-05 04:14:42.694] BLOCK ACCEPTED!
[2018-02-05 04:14:42.784] Solved block 507708 by 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.300_1
[2018-02-05 04:14:42.784] User 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc:{"hashrate1m": "5.76P", "hashrate5m": "5.75P", "hashrate1hr": "5.76P", "hashrate1d": "5.68P", "hashrate7d": "5.37P"}
[2018-02-05 04:14:42.784] Worker 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.300_1:{"hashrate1m": "1.31P", "hashrate5m": "1.32P", "hashrate1hr": "1.32P", "hashrate1d": "1.31P", "hashrate7d": "1.24P"}
[2018-02-05 04:23:27.249] Hash for block height 507708 confirms block was CONFIRMED
So it's in the confirmed blocks: http://ckpool.org/blocks/507708.confirmedCongratulations everyone and thanks again to our core hasher wetsuit  |
|
|
|
W00t \o/ [2018-02-05 04:14:42.517] Possible block solve diff 5413901829396.665039 !
[2018-02-05 04:14:42.694] BLOCK ACCEPTED!
[2018-02-05 04:14:42.784] Solved block 507708 by 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.300_1
[2018-02-05 04:14:42.784] User 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc:{"hashrate1m": "5.76P", "hashrate5m": "5.75P", "hashrate1hr": "5.76P", "hashrate1d": "5.68P", "hashrate7d": "5.37P"}
[2018-02-05 04:14:42.784] Worker 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.300_1:{"hashrate1m": "1.31P", "hashrate5m": "1.32P", "hashrate1hr": "1.32P", "hashrate1d": "1.31P", "hashrate7d": "1.24P"}
So fresh it's still waiting on confirm |
|
|
|
I didn't say anything was wrong with the pool...
When I check in open wrt, the avalon interface it shows a constant 6.8Th/s but the ckpool users page is less constant. Sometimes showing similar sometimes showing close to half.
You think there are intermittent times when only one miner is hashing? this seems to be a recent occurrence.
A minute ago all was normal....
The pool can only estimate based on your submitted shares which will not be submitted regularly enough to guarantee accurate reporting over a small time frame; only a long one. Usually the 15 min hashrate is the most accurate "short term" hashrate estimate. |
|
|
|
The first version of the new web interface is now live with great thanks to an otherwise very new user, morktadela! Give him your thanks Go to http://ckpool.org and refresh the page to see. Some details are missing, like the blocks page and the new miner.status page, but will come in time. All the direct links are still there and you will always be able access them directly if you don't wish to use the gui version Thanks Morktadela! ck, I believe the luck % on user page is incorrect, need to multiply value by 100. Shows as 1%.  Noted and was reported. Morktadela is hard at work at fixing it  |
|
|
|
also someone who is starting out mining liking isn't going to begin with an asic but if you tell them to fuck off they likely won't use your pool when they do get an asic
No, someone starting out should read an intro to mining before ploughing into what you did: https://bitcointalk.org/index.php?topic=2415854.0 |
|
|
|
Thanks for the info, I really appreciate it!
"Could be that, since you're mining at such a low hashrate, the share was already stale when you found it. Also see my remark at the end of this post"
Yea that makes sense. I know that I have very little computing power to the point where its not profitable but I'm kind of doing it as a lottery and to learn how to mine and maybe get an ASIC later.
I'm just using a laptop with a nvidia gtx 1050 4GB as a dedicated miner but I haven't heard the fans kick in at all nor has it warmed up hardly. I'd like to keep trying though and see if I can get some shares accepted.
How can I optimize the configuration, I basically just had the url my username and password and -I 9 but I started coming across things like thread concurrency and commands like this setx GPU_MAX_ALLOC_PERCENT 100 but I don't know how to set the batch file up with those? Could you help me with that? I'll pay it forward if I continue mining.
Just stop doing it please as it has almost nothing in common with modern bitcoin mining so it doesn't even serve as a learning experience. You're wasting your time, power, and risking destroying your GPU, and non-asic miners aren't welcome here as you consume as many resources as a 1PH miner. |
|
|
|
The first version of the new web interface is now live with great thanks to an otherwise very new user, morktadela! Give him your thanks Go to http://ckpool.org and refresh the page to see. Some details are missing, like the blocks page and the new miner.status page, but will come in time. All the direct links are still there and you will always be able access them directly if you don't wish to use the gui version |
|
|
|
Pool restarted without any issues, most miners just reconnected without any drop in hashrate. Apart from some minor theoretical bug fixes, the pool stats diff will now show 1 decimal place precision, and there is now an extra page of information that can be referenced by the pool stats page which shows all active miners sorted from biggest to smallest. This is a very busy page but includes some extra information which some have been desiring. http://ckpool.org/pool/pool.miners |
|
|
|
I'm doing some minor maintenance on the pool code and will be restarting the pool within the next hour for the updates. Hopefully there should be minimal downtime all going well.
EDIT: I won't be around long enough after the restart to ensure everything's okay so I'll hold off till tomorrow at least.
Is that just this pool (pool.ckpool.org) , or is solo (solo.ckpool.org) also included. Just want to know since solo is my backup and if both going down, I will probably add a third to rig just in case down for awhile and at least I can keep hashing during updates. It will only be this pool. The planned restart will happen now within the next hour. |
|
|
|
Was wondering if there was any major profitability differences from this ckpool, kano pool and slush over lets say a few months?
There is no magical way to change mining profitability, it comes down to fees and luck. The fee here is zero. The luck I have no control over. All I can do to offset any other issues where losses occur is minimise the risk of block orphans and never mine empty blocks, which I've put great effort into doing. |
|
|
|
|
I'm doing some minor maintenance on the pool code and will be restarting the pool within the next hour for the updates. Hopefully there should be minimal downtime all going well.
EDIT: I won't be around long enough after the restart to ensure everything's okay so I'll hold off till tomorrow at least.
|
|
|
|
|
pool.ckpool.org now points to this pool, thanks.
|
|
|
|
I want to ask is possible to update s3 to latest version cgminer? is possible?
No. |
|
|
|
[2018-02-01 21:56:52.413] Accepted client 6 share diff 45963207.4/400/1.97K: 000000000000005d7131f04834ff91223a962303d4b72ed8df802bd0b44e8009 Saw this in the log of the proxy. Is this a "close" share? I saw recent blocks are have 4 additional 0000? Do you think diff 45963207 is close to 2603077300218? I know is low Diff share. But is that how block is found when hash has additional leading 0's? The more leading 0's closer to block for that share alone? I thought it is possible to find block at any Diff? no? - Luck? It's closer yes, but a very very long way away. That is indeed how you find a block, but you need a shitload more zeroes and it's possible though unlikely. Hashrate first and luck second is how you find one. |
|
|
|
[2018-02-01 21:56:52.413] Accepted client 6 share diff 45963207.4/400/1.97K: 000000000000005d7131f04834ff91223a962303d4b72ed8df802bd0b44e8009 Saw this in the log of the proxy. Is this a "close" share? I saw recent blocks are have 4 additional 0000? Do you think diff 45963207 is close to 2603077300218? |
|
|
|
So.. does this look right? I think I'm hashing away! {
"hashrate1m": "13.3T",
"hashrate5m": "13.5T",
"hashrate1hr": "7.46T",
"hashrate1d": "440G",
"hashrate7d": "63.8G",
"lastshare": 1517518697,
"workers": 2,
"shares": 9008586,
"bestshare": 8294237.55550756,
"bestever": 8294237,
"worker": [
{
"workername": "1PvVLNAcsWXk7gCZjUyH1cLpQXXYFKcFTQ",
"hashrate1m": "13.3T",
"hashrate5m": "13.5T",
"hashrate1hr": "7.46T",
"hashrate1d": "440G",
"hashrate7d": "63.8G",
"lastshare": 1517518697,
"shares": 9008586,
"bestshare": 8294237.55550756,
"bestever": 8294237
}
]
}Please try and include stuff like that in code tags as I've done in your quote. Yep, looks good, good luck! |
|
|
|
sorry guys, MRR switched my rigs to kano during the outage and never switched back and i didn't even know about it. just noticed the hash rate drop now and had to switch the rigs back manually.
Best news I've heard all day, have a merit point |
|
|
|
I've been playing around with the website and flask to see if I could build something. It's only a start... http://35.196.38.106/Thanks for that. I hate to tell you this, but it's funny, someone else has already been working on an interface and they've made more good progress so I don't want to see you duplicate work. Hold off doing anything else with it as hopefully I should have something to put up soon. This? http://ckpool.org/test.htmlNo, not that. Much more featured. |
|
|
|
The pool is choosing the diff. That config only affects local mining to the proxy. I setup a full node and bitcoind I will look into setting up a small private pool at a later date once I learn what I have now. What has that got to do with the solo pool which this thread is for? |
|
|
|
|
Show Posts
