|
Bitcoin Core 0.21.1 has just been released with the signalling bit for taproot activation. It's a fairly optimistic release mechanism hoping for a supermajority of miners to activate taproot by 11 August 2021. I have no objection to taproot activation but have been holding off doing any changes to the bitcoin node running on the solo pool given its long term stability. However should taproot get activated, running a node without taproot support will risk creating blocks on an invalid chain. So at some stage in the next week I will be validating the latest bitcoin core node before updating it on the solo pool, so that the pool will also be signalling for taproot. That said, without mining any blocks we're not signalling anything, so it's just a precautionary step in advance. I'll put a notification in the near future when the node has been updated, but it will not cause an interruption to mining.
Mine on.
|
|
|
|
Thanks, everyone! 1PiY here... I've always watched this thread closely over the past 5 years and have always appreciated everyone's support and kindness for one another. Usually I just mine away in the shadows... Keep mining, everyone, it AIN'T over yet! And THANK YOU @ck for making this wild ride a possibility  You're most welcome and congratulations. It takes serious balls to throw that much hashrate at solo mining and it paid off for you. I have 2 questions. I am running a somewhat Dinky 70TH/s setup. Is it possible for the 10PH/s maniacs to literally steal a block from me? Also, I noticed whilst re-reading the intro "Unlike regular pools, ckpool never mines transaction-free blocks due to its ultra-scaleable code which has miners on both new blocks and transactions concurrently." and I was curious what the problems are which are associated with "Transaction-free blocks." Thank you for at least the idea of a lottery pool. I guess I just want to be assured it truly is one. No, there's no stealing of blocks. These days with blocks being only 6.25 BTC, transactions are a bigger part of the reward than ever, regularly constituting over 10% of the reward. Now that bitcoin is exceedingly popular, transaction counts increase and a block without transactions do not benefit the network at large, delaying transactions. There is also the risk of creating an invalid fork when building on transaction free blocks, which has happened in the past, invalidating all blocks built on that fork. |
|
|
|
Hello, newbie here! I'm using cpuminer-multi with -u my_address -a sha256d -o stratum+tcp://solo.ckpool.org:3333 -t 4 with my_address being my wallet public key... It has been running for a couple of weeks now but if I try to check my stats with https://solo.ckpool.org/users/my_address I receive a 404... Can someone please help me understand how to fix this? cpuminer output looks good, I'm receiving jobs from the stratum channel... e.g.:
[2021-02-28 23:41:55] solo.ckpool.org:3333 asks job 4294967295 for block 672620
Thank you! CPU mining for bitcoin is like mining rock for gold with a toothpick. The rock never shows any effect whatsoever and doesn't even known you're mining. That's how the pool is. Please don't waste your time CPU mining bitcoin (or GPU mining for that matter.) |
|
|
|
I also found that hashrate1m is very unstable on high diff 4334 port.（went up and down from 0-max miner hashrate)
This is not happening on regular 3333 port.
That's to be expected with 1 million diff shares unless you have a veritable fuckload of hashrate as you'll only rarely be submitting shares with normal mining hardware - how can you average over 1 minute when you send shares once only ever 5 or 10 minutes? It still doesn't matter as it makes no difference to your chance of finding a block. |
|
|
|
Happy New Year miners |
|
|
|
Thanks very much |
|
|
|
Okay @ ck what address?
to send the 0.017
Sure thing. Just send it to the solo pool address. 1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ Thanks! |
|
|
|
|
Well someone didn't like us finding a block, there was a brief DDoS on the pool, but it only lasted 5 minutes. Not sure if mining was interrupted at all but everything's fine now. Keep on mining.
|
|
|
|
Thanks, everyone! 1PiY here... I've always watched this thread closely over the past 5 years and have always appreciated everyone's support and kindness for one another. Usually I just mine away in the shadows... Keep mining, everyone, it AIN'T over yet! And THANK YOU @ck for making this wild ride a possibility You're most welcome and congratulations. It takes serious balls to throw that much hashrate at solo mining and it paid off for you. |
|
|
|
Uh oh, we got some serious hash trying to steal our block  "hashrate1m": "201P", Congrats to 1PiYJ1VTdY2JbP4CdAgLvZjijpwMQPVEnb for solving block 660588! I hope we don't need again that hughe amount of time to go wild  Well someone was absolutely hammering the pool. Congratulations to 1PiYJ1VTdY2JbP4CdAgLvZjijpwMQPVEnb! A pretty fat block at 7.11BTC. [2020-12-09 06:20:17.971] Possible block solve diff 2040833996125246.750000 !
[2020-12-09 06:20:18.040] BLOCK ACCEPTED!
[2020-12-09 06:20:18.045] Solved and confirmed block 660588 by 1PiYJ1VTdY2JbP4CdAgLvZjijpwMQPVEnb
[2020-12-09 06:20:18.045] User 1PiYJ1VTdY2JbP4CdAgLvZjijpwMQPVEnb:{"hashrate1m": "199P", "hashrate5m": "197P", "hashrate1hr": "169P", "hashrate1d": "58.5P", "hashrate7d": "10.1P"}
[2020-12-09 06:20:18.045] Worker 1PiYJ1VTdY2JbP4CdAgLvZjijpwMQPVEnb:{"hashrate1m": "199P", "hashrate5m": "197P", "hashrate1hr": "169P", "hashrate1d": "58.5P", "hashrate7d": "10.1P"}
[2020-12-09 06:20:18.064] Block solved after 24584522931954 shares at 128.3% diff
Nice quick propagation too on the solo server, with only 70ms required from the bitcoin daemon to fully validate the block. https://btc.com/00000000000000000000234eb03bff844083b81b9440ab2750a41defcc909e2f |
|
|
|
Quick question ... if I run a BTC node in prune mode, will I still be able to mine off it? or does pruning disrupt the mining process! I'm looking into setting up my own ckpool node (for the fun of it)
Yes, but performance would be shit. |
|
|
|
Would mining to this pool with my gaming pc be a waste of time for me because of a low hash rate or is it worth a try?  It would be a waste. PC mining bitcoin became redundant over half a dozen years ago. |
|
|
|
@CK do you have a average diff figure for the last 10 or 20 blocks found on the pool?
Surprisingly close to 100% from memory |
|
|
|
This is probably because you never connected to the pool with this worker (btc address) if you try any random BTC address which didn't submit anything to the pool you will always get Not Found
The requested URL was not found on this server.
Apache/2.4.41 (Ubuntu) Server at solo.ckpool.org Port 443 Are you sure you mined on the solo pool using this address? The usual reason is a hashrate so pathetically small that they don't even submit a single share. What mining hardware are you using? |
|
|
|
Port: 443 and 3335 does not work with me. 3333 works fine.  Port 443 is not there in the config as it's used by the webserver https and not mentioned on the website, and 3335 is uniquely for asicminer tubes. There is absolutely no point using 3335 for anything else. |
|
|
|
(in fact it's relatively lossy and adds latency compared to actually sending all the miners directly to the pool.)
And how are they going to be able to monitor everything without pooling/redirecting the hashrate through their proxy? if the connection was going straight from the miner to the buyer's pool then Nicehash can't operate, what other options do they have? ِ All I did was point out a fact. |
|
|
|
|
Nicehash has always pooled miners through a proxy into very few workers. Doesn't mean anything (in fact it's relatively lossy and adds latency compared to actually sending all the miners directly to the pool.)
|
|
|
|
well you cant actually join the solo run with contributing an S9. you'dhave to chip in some BTC to the cause of renting.
then whatever you contribute, and we hit a block, you will get your % wise back
make sense?
Why not? if you guys manage to hit a block you can check his hashrate/shares and then pay him accordingly, all you have to do is get him to mine to the same wallet using a different worker, actually his idea sounds interesting to me, whoever doesn't have BTC in hand can contribute some hashrate, it will be a bit more difficult to manage once and if a block is hit, but as long as everything is planned for ahead of time then there should be no problems. Well that would be like me pointing my personal hashrate to the solo run addy during the rental.lets say 300Th, and the rentals hit a block. But my personal miners were not even close. I would not be ok with paying some btc to my personal addition or anyone else who just pointed miners to it. While everyone else who put actual $$$ into the rental Process would be out some$$. That’s just me. You'd have to keep track of how many shares his actual worker contributed during the solo run period. That would be the only fair way to give him an appropriate proportion of the reward, but would work. |
|
|
|
...
if your look back thru this thread, you will see they do these runs quite often and have had no issues or need for escrow - I believe the thread is self moderated so ck could have deleted or a forum mod could have deleted it. I haven't deleted anything in a long time. |
|
|
|
Question (possibly for CK himself) - does this pool system cater to other Algos also?
Nope, bitcoin ONLY. |
|
|
|
|
Show Posts
