I have connected my GPU miner to solo ck pool, but i cannot see my stats when i navigate to the address. It says 404 not found. http://solo.ckpool.org/users/1AHrgz7AYHwtScn7VVQBDfuRyzBb9kDazpBut in my cg miner i see the connection is successful and Im already mining with a small hash power 30 Mh/s. Any reason for this guys? Please don't do that. You are only wasting power and shortening the life of your GPU trying to mine bitcoin. You don't see any stats because your hashrate is so low that you're not even registering on the pool since you haven't even submitted a single share. If you want to do fun very low hashrate "lottery" solo mining, find yourself a cheap usb stick and use that instead. |
|
|
|
Hi there CK,
Can I use the old U3v2 from BM for solo mining?
Thanks
Yes. You can use any ASIC miner to solo mine here, from the 333MH USB mining sticks upwards  |
|
|
|
[2017-09-11 04:02:26.116] Possible block solve diff 4153260211492.718262 !
[2017-09-11 04:02:26.320] BLOCK ACCEPTED!
[2017-09-11 04:02:26.510] Solved and confirmed block 484634 by 12iSvuwsDwUCFKpXnUmtFJNGPmMm2Yt6cS.2x2x2
[2017-09-11 04:02:26.510] User 12iSvuwsDwUCFKpXnUmtFJNGPmMm2Yt6cS:{"hashrate1m": "655T", "hashrate5m": "662T", "hashrate1hr": "666T", "hashrate1d": "672T", "hashrate7d": "673T"}
[2017-09-11 04:02:26.510] Worker 12iSvuwsDwUCFKpXnUmtFJNGPmMm2Yt6cS.2x2x2:{"hashrate1m": "15.8T", "hashrate5m": "15.1T", "hashrate1hr": "13.6T", "hashrate1d": "13.7T", "hashrate7d": "13.3T"}
[2017-09-11 04:02:26.512] Block solved after 379870970050 shares at 41.2% diff
Congratulations A number of users are STILL trying to mine on this pool with a non-btc address username. You will have your IP address blocked if you continue to do so since the pool will keep rejecting you indefinitely. Please check the credentials you are using on this pool and if you find you are blocked and have corrected it, please contact me to have you IP address un-blocked. |
|
|
|
But GPU mining have for other coins not only bitcoin
Right, and the official cgminer is for bitcoin mining ONLY. |
|
|
|
Sorry if these are dumb questions: In looking at my cgminer for my lottery ticket miner, i can see: Accepted 54d53ab5 Diff 773/90 GSD 0 pool 0
I get that share is proof my miner is working on finding a block, but I have a couple of noob questions: 1) Is "54d53ab5" the nonce the miner submitted, or is part of the hash? 2) Does the diff 773 refer to the hash produced by the submission above or something else? Thanks, just trying to understand this a little more 54d53ab5 are the first non zero characters in the hash of the share you discovered. Diff 773 says what diff that particular hash share was, and 90 is the current pool share diff so since your share diff was greater than or equal to 90 cgminer showed you that it's submitting that share. There would have been many other shares below diff 90 and they never show up on the display since cgminer only shows you shares that meet your target pool diff. |
|
|
|
|
Not in the bitcoin mining section which is where you posted.
/locked.
|
|
|
|
Where is the best place to rent hash from?
Mining rig rentals gives you the most control but Nicehash is usually cheaper. Bear in mind that the prices are basically dependant on how many people are renting at the time so if demand for rentals is low the price will be cheaper so watch before you rent. |
|
|
|
By the way, I metered one of my bitcoind processes. With 8 peers, I'm getting around 2.2 kB/s up, 3.4 kB/s down. It might be possible to keep a Bitcoin full node synced with just a 56k modem. If anyone else is curious: sudo iftop -B -f "port 8333". That assumes all of your peers are on that port for either the source or the destination, as mine are. You can verify that manually with bitcoin-cli getpeerinfo. This is with btc1 1.14.5.
The network is actually surprisingly quiet at the moment with mempools actually draining close to empty. This is very different to what happens during spam transaction floods. Best to plan for the worst case scenario. |
|
|
|
I was looking on https://btc.com/stats/pool/Solo%20CKI notice that next to the DIFF it shows status like : Difficulty 1.71T / 888.17G 926.20G / 923.23G 2.96T / 923.23G Is the first value the hashrate that cracked each block? The first value is the diff of the share that cracked the block. btc.com has no way of estimating the hashrate of the block solver, only the pool does. You can see the same value in my announce post earlier: [2017-09-03 04:17:45.672] Possible block solve diff 1706914113535.543945 !
|
|
|
|
Ok, so I have been with sulshpool for about a month and I'm about to hit 1 BTC today,
I am going to switch my farm over to this pool for a month and see what my yields are. (if I can fugue out how to set it up)
I'm running 10 Avalon 741's that go from 70 Th/s - 80-Th/s.
DJ
Awesome, welcome aboard and be very patient, but it'll be worth it in the end. See if you can convince as many friends to join you too |
|
|
|
Hi guys Need some help ........ I have antminer s9 and i am resident of Middle East ..... before starting solo mining i Use to sell my hashrate on Nice Hash where i see my Blocks status everyday my machine found more then 5 blocks. anyways it was others luck.
I have set my machine as
stratum+tcp://solo.ckpool.org:3333
where diff is showing 12.1K
Is it okay or i have to change settings?
That's fine. Ignore the diff on this pool and let the pool manage it. |
|
|
|
Congratz to the lucky blocker!
Would that be a large rental that hit the block?
No, (s)he's been hashing long term on this solo pool and cracked quite a few blocks over an extended period. |
|
|
|
[2017-09-03 04:17:45.672] Possible block solve diff 1706914113535.543945 !
[2017-09-03 04:17:45.953] BLOCK ACCEPTED!
[2017-09-03 04:17:46.192] Solved and confirmed block 483272 by 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY.134
[2017-09-03 04:17:46.192] User 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY:{"hashrate1m": "363T", "hashrate5m": "353T", "hashrate1hr": "355T", "hashrate1d": "366T", "hashrate7d": "348T"}
[2017-09-03 04:17:46.192] Worker 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY.134:{"hashrate1m": "15.2T", "hashrate5m": "13.1T", "hashrate1hr": "12.2T", "hashrate1d": "11.8T", "hashrate7d": "11.8T"}
[2017-09-03 04:17:46.194] Block solved after 527550640548 shares at 59.4% diff
|
|
|
|
Ok great, should I update the miners with the kano update the are all showing.
Fri Jan 9 20:41:34 CST 2015
Kernel Version 3.10.12
cgminer 4.6.1-1
If it's not too much effort, yes, there were some worthwhile improvements in his changes but no magic performance increases. |
|
|
|
Have a small number of s3 miners I pointed at the pool they all use the same worker name the BTC address.
I guess when doing this they work as single units?
Would I need to use the proxy code to connect the miners into a consolidated connection?
Some advice on setting DIFF for the miners would help also as I see they all seem to have vared DIFF reading.
None of this matters. Single unit or spread out it makes no difference, it's only a matter of choice on your part as to how you wish to tell them apart on the pool (or not.) The only reason to proxy them would be to decrease your internet bandwidth requirements. Vardiff also will have no effect either. Just let them mine away. |
|
|
|
|
Show Posts
