[2018-11-28 01:46:29.271] Possible block solve diff 106058768599316.140625 !
[2018-11-28 01:46:29.421] BLOCK ACCEPTED!
[2018-11-28 01:46:29.564] Solved block 551773 by 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k.worker
[2018-11-28 01:46:29.564] User 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k:{"hashrate1m": "32.4P", "hashrate5m": "32.2P", "hashrate1hr": "32.2P", "hashrate1d": "26.1P", "hashrate7d": "13.3P"}
[2018-11-28 01:46:29.564] Worker 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k.worker:{"hashrate1m": "32P", "hashrate5m": "31.7P", "hashrate1hr": "31.8P", "hashrate1d": "25.2P", "hashrate7d": "11P"}
Still waiting on confirm  |
|
|
|
...... this block is so stubborn......MAYBE... we need to get a "magic" reboot - -ck?
Maybe... so I'll do something just as effective - nothing. |
|
|
|
|
Well, I'm over this price crash. Anyone wanna join me in some drinks?
|
|
|
|
My SSD space near depleted, blockchain 238GB  . If I use Exodus wallet address, will it work? I just worried if I block the newly generated block will not be recognize as spendable. It will but I recommend staying with your own node instead. Simply change to a pruned node to save space. There is no need to keep the full blockchain if you have limited space. Add something like this to our bitcoin.conf: prune=10000 And that will limit it to using only 10GB of space. The lowest you can set it to is 550 which means only 550MB. |
|
|
|
BLOCK! 13.07BTC (thank you BCH hash war for the increased BTC fees)
[2018-11-15 21:37:39.330] Possible block solve diff 15486663013866.531250 !
[2018-11-15 21:37:39.807] BLOCK ACCEPTED!
[2018-11-15 21:37:40.122] Solved block 550226 by 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k.10x50x9x74
[2018-11-15 21:37:40.124] User 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k:{"hashrate1m": "5.87P", "hashrate5m": "5.92P", "hashrate1hr": "17.4P", "hashrate1d": "10.6P", "hashrate7d": "16.1P"}
[2018-11-15 21:37:40.124] Worker 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k.10x50x9x74:{"hashrate1m": "18.6T", "hashrate5m": "17.8T", "hashrate1hr": "9.52T", "hashrate1d": "563G", "hashrate7d": "81.6G"}
[2018-11-15 21:47:20.449] Hash for block height 550226 confirms block was CONFIRMED
|
|
|
|
CK, what is the last firmware update for the T1's? Thanks ahead of time.
The last one I made which was 20180515_060842. |
|
|
|
Is it technically possible at all for my 9TH/s S9 (only two boards hashing) to solve a block however little chance it may be? I can keep it running forever until it burns if so.
Definitely. Don't forget that even the 1EH mines out there are filled with nothing but S9s and similar hardware anyway, and it's always still a single S9 or T1 or whatever that ends up finding the block. |
|
|
|
would 100 phs do the job in a day?
Nope, not even 100PH is enough to guarantee a block in a day anymore. |
|
|
|
If you don't got an USB Miner on it (2GH min.) it will not be a lottery, it will be a waste of time and energy.
Can you explain? He's saying the minimum you should mine with would be a 2GH SHA-256 USB miner. Anything else, PC, Laptop, GPU, is too slow to even consider it a lottery device. which is wrong,but what do I know. a cpu doing 50mh or 0.05gh vs gpu doing 100mh or .1gh vs a stick doing 2000mh or 2.0gh vs a stick doing 20000mh or 20.gh vs a stick doing 40000mh or 40gh all are lottery in my book Except that an RPi does something like 50kh. Still a lottery, but you know... |
|
|
|
[2018-11-07 02:16:06.919] Possible block solve diff 7517687118560.174805 !
[2018-11-07 02:16:07.148] BLOCK ACCEPTED!
[2018-11-07 02:16:07.535] Solved block 549077 by 3QQVkgdqrMc7Tmk6oWtCc5odf9LeHD8UNa.141
[2018-11-07 02:16:07.535] User 3QQVkgdqrMc7Tmk6oWtCc5odf9LeHD8UNa:{"hashrate1m": "233T", "hashrate5m": "220T", "hashrate1hr": "216T", "hashrate1d": "216T", "hashrate7d": "234T"}
[2018-11-07 02:16:07.535] Worker 3QQVkgdqrMc7Tmk6oWtCc5odf9LeHD8UNa.141:{"hashrate1m": "13T", "hashrate5m": "11.9T", "hashrate1hr": "11.9T", "hashrate1d": "11.8T", "hashrate7d": "11.8T"}
[2018-11-07 02:52:26.987] Hash for block height 549077 confirms block was CONFIRMED
|
|
|
|
Offhand, do you know the oldest bitcoin version that is supported? I am looking at the code below, with a small modification that I made. if (sdiff >= diff) {
if (new_share(sdata, hash, id)) {
LOGINFO("Accepted client %s share diff %.1f/%.0f/%s: %s",
client->identity, sdiff, diff, wdiffsuffix, hexhash);
result = true; LOGDEBUG("stratifier.c Ln 6223 submitblock <hexstuff>"); // parse_upstream_block(ckp, val);
} else {
Oh, and as for Bitbucket, it's just yet another login / password / interface to deal with. I'll deal with it. I don't know what bitcoin version, sorry. That is for a successful plain share, not a block solve! You don't need a login/pass etc. just to clone a repo, but whatever. github didn't offer what I wanted around the time I started working on ckpool. |
|
|
|
I want to set up an isolated lab where I read the software sources, execute for a bit, and see what happens.
In my particular scenario I will use an earlier version of the reference bitcoin client and download about 10,000 blocks. The difficulty will be 1 at this point.
I will use cgminer and ckpool as well, to develop what skill I can at understanding stratum and how to configure the servers and what they do.
Toward that end I have made the most recent version of ckpool, and started it with
ckpool -l 7 -A -H
and ckpool.conf points only to my local setup.
I appear to retreive getblocktemplates, pass info up to cpuminer/minerd, do the magic and send results back to ckpool. ckpool.log and the consoles for cpuminer and ckpool make sense to me.
I don't grok how to get the new block submitted to my local bitcoind.
For what it's worth, I am looking at line 6225 of stratum.c. That seems to be one place where I might expect a submitblock to happen, but it does not.
My understanding of "upstream" and whether it is necessary / possible to set up a proxy to make this happen is a bit wobbly.
Oh, and while I am posting, I thought I would mention that I am pretty familiar with GitHub, but not so much with the repository where ck has his source located. Is there a GitHub bridge (fork) to his efforts, or do I need to figure out the new repository as part of all this effort.
Old versions of the bitcoin daemon do not have the features required for ckpool to work completely, though I don't know how old you're talking about. There's nothing in line 6225 that has anything to do with submitting a block? test_blocksolve goes to line 5949 which sends it to local_block_submit and in there line 2061 submits it to generator_submitblock and so on. Bitbucket is the only authentic git repository for my source, so not sure why you need to look elsewhere? |
|
|
|
Im trying to check my stats, but always get
Not Found
The requested URL /users/3Fe4qhf9fc7VjhdmXCNdpaMPymSrDGiHGR.0 was not found on this server.
Apache/2.4.10 (Debian) Server at solo.ckpool.org Port 80
The usual reason for this is your hashrate is so pitifully small that you haven't even found a single share yet, but you're using a worker name instead of a user name, so get rid of the .0 at the end. |
|
|
|
Thanks CK I kind of guessed that would be the answer.
Last time I buy bitmain products that for sure.
Gotta be realistic - cost/power/performance ratios are everything in mining; if shitmain give you the best, there is still a reason to buy them. Having said that, they've had nothing new in 2 years and what looks like 2 failed attempts to fabricate their next gen hardware so things aren't looking in their favour any more... |
|
|
|
Is there any way to fix the "bestshare" showing as 0 on antminers?
Got a batch and none of them show any best share in the gui.
Sent bitmain email asking about it and they told me " Its the pool not the miner" which I know to be false..
I know this is down to the shitty fork bitmain did of of CK's fantastic work.
CK I would be forever in your debt if you could help me fix this please.
Since it's a bitmain firmware problem how exactly do you want me to fix it? My guess from looking at their shitmain firmware years ago is it only works with power-of-2 difficulties. However, since their shitware doesn't support suggest-diff then you're screwed unless you set up a proxy and fix the difficulty to some power of 2 value in the proxy. Sure is a ridiculous workaround for dodgy shitware. |
|
|
|
Hey ck, if it is not too much to ask, can you add the average hashrate and duration of the miner that solved the block, i know blocktrail is not yours and that you will need to make another statistic page, i just moved from antpool solo mining to ck solo. antpool has this solo statistics which shows all blocks found by miners running solo on their pools with the duration and avg hashrate. i know history means nothing but it's quite motivating to see someone with 300gh (yes gh) solving a block in less than 3 months  . i am sure ck pool has more impressive results to show. I have no historical records like that, though each time I post a block solve message here, the miner's details are with it. |
|
|
|
|
Hi all. The datacentre that hosts the pool will be doing maintenance work from 12am to 6am GMT-5. They don't anticipate any interruptions to connectivity, but just in case, make sure you all have a backup set up (and not the solo pool since it's hosted in the same datacentre).
|
|
|
|
Once again the power of lamb does it.
Be right back, going to go stock up on some lamb... |
|
|
|
[2018-10-23 03:38:58.818] Possible block solve diff 10203388133060.582031 !
[2018-10-23 03:38:58.979] BLOCK ACCEPTED!
[2018-10-23 03:38:59.148] Solved block 546962 by 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k.worker
[2018-10-23 03:38:59.148] User 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k:{"hashrate1m": "17.2P", "hashrate5m": "17.1P", "hashrate1hr": "16.9P", "hashrate1d": "17.3P", "hashrate7d": "21.4P"}
[2018-10-23 03:38:59.148] Worker 32LA7cmsj35LH7cK1MjvwyoLEmYpuWAD9k.worker:{"hashrate1m": "14.1P", "hashrate5m": "14P", "hashrate1hr": "13.8P", "hashrate1d": "14.1P", "hashrate7d": "17.9P"}
Still waiting on confirm but I don't see any competing blocks. |
|
|
|
Is it better to change payout address now or when pool get large again?
Old address will wind down faster if the pool is bigger. |
|
|
|
|
Show Posts
