Author

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 123. (Read 89163 times)

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
That is not at all the response I get when I check that site. Besides, the pool is running fine as I can see, but routing across the earth is often funky.

See:
https://www.internetweathermap.com/
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I've shut down the asicminer prisma proxy port as there were very few remaining users, and some occasional unintentional abusers, and confused users. I can't imagine there are many still in operation out there but sorry about any inconvenience if you were trying to use them.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
newbie
Activity: 37
Merit: 0
Hi !

pool solo.ckpool.org is not available, already two hours.
you have the same?
hero member
Activity: 666
Merit: 516
Fuck BlackRock
I hate mining anything not CPU mineable. I love mining altcoins thought to be dead for 0 profit lmao. However... I decided to experiment. Ran cpuminer with 12 threads til my computer got loud enough for me to say I'll never try that ever again! but congrats to the lottery winners here hehe:

Code:
cpuminer-gw64-corei7 -a sha256d -o stratum+tcp://solo.ckpool.org:3333 -u 1JBsrJK59ppfV4xqW9uNiYRA4NdLtDxXEf.0 -p x
** cpuminer-multi 1.3.1 by tpruvot@github **
BTC donation address: 1FhDPLPpw18X4srecguG3MxJYe4a1JsZnd (tpruvot)

[2022-02-01 20:16:59] Starting Stratum on stratum+tcp://solo.ckpool.org:3333
[2022-02-01 20:16:59] 12 miner threads started, using 'sha256d' algorithm.
[2022-02-01 20:17:02] Stratum difficulty set to 10000
[2022-02-01 20:17:02] sha256d block 721424, diff 26643185256535.465
[2022-02-01 20:17:03] CPU #11: 7108 kH/s
[2022-02-01 20:17:03] CPU #3: 6808 kH/s
[2022-02-01 20:17:03] CPU #2: 6808 kH/s
[2022-02-01 20:17:03] CPU #10: 6831 kH/s
[2022-02-01 20:17:03] CPU #1: 6809 kH/s
[2022-02-01 20:17:03] CPU #9: 6809 kH/s
[2022-02-01 20:17:03] CPU #8: 6787 kH/s
[2022-02-01 20:17:03] CPU #7: 6787 kH/s
[2022-02-01 20:17:03] CPU #6: 6787 kH/s
[2022-02-01 20:17:03] CPU #5: 6765 kH/s
[2022-02-01 20:17:03] CPU #4: 6765 kH/s
[2022-02-01 20:17:03] CPU #0: 6765 kH/s
[2022-02-01 20:17:56] CPU #5: 6721 kH/s
[2022-02-01 20:17:57] CPU #1: 6662 kH/s
[2022-02-01 20:17:57] CPU #3: 6656 kH/s
[2022-02-01 20:17:57] CPU #7: 6643 kH/s
[2022-02-01 20:17:57] CPU #6: 6637 kH/s
[2022-02-01 20:17:57] CPU #10: 6635 kH/s
[2022-02-01 20:17:57] CPU #9: 6635 kH/s
[2022-02-01 20:17:57] CPU #11: 6619 kH/s
[2022-02-01 20:17:57] CPU #2: 6606 kH/s
[2022-02-01 20:17:58] CPU #8: 6497 kH/s
[2022-02-01 20:17:59] CPU #4: 6394 kH/s
[2022-02-01 20:18:00] CPU #0: 6305 kH/s
[2022-02-01 20:18:50] CPU #5: 6589 kH/s
[2022-02-01 20:18:51] CPU #7: 6581 kH/s
[2022-02-01 20:18:51] CPU #3: 6552 kH/s
[2022-02-01 20:18:51] CPU #1: 6538 kH/s
[2022-02-01 20:18:51] CPU #6: 6562 kH/s
[2022-02-01 20:18:52] CPU #2: 6499 kH/s
[2022-02-01 20:18:52] CPU #11: 6484 kH/s
[2022-02-01 20:18:52] CPU #9: 6466 kH/s
[2022-02-01 20:18:52] CPU #10: 6461 kH/s
[2022-02-01 20:18:55] CPU #8: 6246 kH/s
[2022-02-01 20:18:55] CPU #4: 6343 kH/s
[2022-02-01 20:18:57] CPU #0: 6251 kH/s
[2022-02-01 20:19:45] CPU #5: 6558 kH/s
[2022-02-01 20:19:46] CPU #7: 6556 kH/s
[2022-02-01 20:19:46] CPU #3: 6542 kH/s
[2022-02-01 20:19:46] CPU #1: 6550 kH/s
[2022-02-01 20:19:46] CPU #6: 6520 kH/s
[2022-02-01 20:19:47] CPU #2: 6506 kH/s
[2022-02-01 20:19:48] CPU #11: 6457 kH/s
[2022-02-01 20:19:48] CPU #10: 6436 kH/s
[2022-02-01 20:19:48] CPU #9: 6385 kH/s
[2022-02-01 20:19:52] CPU #4: 6363 kH/s
[2022-02-01 20:19:52] CPU #8: 6263 kH/s
[2022-02-01 20:19:54] CPU #0: 6225 kH/s
[2022-02-01 20:20:40] CPU #5: 6550 kH/s
[2022-02-01 20:20:40] CPU #7: 6558 kH/s
[2022-02-01 20:20:41] CPU #3: 6559 kH/s
[2022-02-01 20:20:41] CPU #1: 6546 kH/s
[2022-02-01 20:20:41] CPU #6: 6548 kH/s
[2022-02-01 20:20:42] CPU #2: 6520 kH/s
[2022-02-01 20:20:42] CPU #11: 6538 kH/s
[2022-02-01 20:20:42] CPU #10: 6548 kH/s
[2022-02-01 20:20:43] CPU #9: 6550 kH/s
[2022-02-01 20:20:47] CPU #4: 6480 kH/s
[2022-02-01 20:20:48] CPU #8: 6434 kH/s
[2022-02-01 20:20:51] CPU #0: 6342 kH/s
[2022-02-01 20:21:35] CPU #5: 6521 kH/s
[2022-02-01 20:21:35] CPU #7: 6542 kH/s
[2022-02-01 20:21:36] CPU #6: 6512 kH/s
[2022-02-01 20:21:36] CPU #3: 6401 kH/s
[2022-02-01 20:21:37] CPU #1: 6351 kH/s
[2022-02-01 20:21:37] CPU #11: 6525 kH/s
[2022-02-01 20:21:38] CPU #10: 6452 kH/s
[2022-02-01 20:21:38] CPU #9: 6486 kH/s
[2022-02-01 20:21:38] CPU #2: 6352 kH/s
[2022-02-01 20:21:43] CPU #4: 6342 kH/s
[2022-02-01 20:21:46] CPU #8: 6211 kH/s
[2022-02-01 20:21:49] CPU #0: 6129 kH/s

EDIT: Honestly I think you guys are pioneering a way to more efficiently but better mine Bitcoin because -ck has used his brain and knowledge of the guts of the majority of pool mining code/operations to realize there's still a place for a "Timechain" focused strategy with the right amount of efficiency and the guerilla like tactics to not just brute force with hash power or be YAP (yet another pool) consolidating to act like the big fish farms... You guys are sort of picking the right places to focus and mining through a "path" that works for people with far less hash power and its gonna definitely work. Why would anyone prefer making bits and pieces of pool payouts when one big score would make up for multiple years of their lives at this time? I have always disliked pool mining. Which is why when I could've bought the hardware years back when this game got super expensive I decided to invest instead and spend my time learning instead of waiting for pool payouts Smiley

Godspeed!
legendary
Activity: 1492
Merit: 1021
Congratulations to bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet with approximately 1.14PH!

Code:
[2022-02-01 08:27:35.681] Possible block solve diff 36770979250673.867188 !
[2022-02-01 08:27:35.728] BLOCK ACCEPTED!
[2022-02-01 08:27:35.730] Solved and confirmed block 721310 by bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet
[2022-02-01 08:27:35.731] User bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.731] Worker bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.767] Block solved after 5496218477727 shares at 20.6% diff

https://btc.com/btc/block/721310

amazing stuff, congratulations to this home miner!
newbie
Activity: 16
Merit: 2
Hi Guys,

I've been a member of the forum for a while, mostly reading and learning from all the posts

I recently joined to solo mine with my S19J, hope everyone is having a good day

Looking forward to hopefully being one of the lucky folks here!

{
 "hashrate1m": "91.9T",
 "hashrate5m": "97.9T",
 "hashrate1hr": "101T",
 "hashrate1d": "102T",
 "hashrate7d": "80.1T",
 "lastshare": 1643741784,
 "workers": 1,
 "shares": 22182935989,
 "bestshare": 1113380751.511688,
 "bestever": 112790275837,
 "worker": [
  {
   "workername": "bc1qlven2a2hvknx7p3ump3n7npl555cj7hxfnv2x0",
   "hashrate1m": "91.9T",
   "hashrate5m": "97.9T",
   "hashrate1hr": "101T",
   "hashrate1d": "102T",
   "hashrate7d": "80.1T",
   "lastshare": 1643741784,
   "shares": 22182935989,
   "bestshare": 1113380751.511688,
   "bestever": 112790275837
  }
 ]
}
full member
Activity: 582
Merit: 149
Awesome!!! Congrats and let's keep hitting em!!!
member
Activity: 150
Merit: 10
Yes congrats!  Great to see all these blocks found.  Hopefully Willi's runs will hit again as well!
member
Activity: 100
Merit: 15
Hi. I've tried using both the . and then the _ and get same result. It still shows network as Dead for ckpool via port 3333. I've tried the other ports too per the CK Pool Instruction.

@HagssFIN
There are 2 common reasons for not being able to connect:
1. The most common one is that you have a typo in your bitcoin address, or added a space somewhere, like before the address.
2. You are in a part of the world where routing is blocked to the datacentre where the pool is hosted - this is unfortunately out of my control as I don't block anyone from mining there.

@-ck

Gotta keep on trying. My guess is that the ISP blocked off the port(s) to CK Pool. Thank you all!

Congrats to the lucky miner on the new block! Exciting news!
legendary
Activity: 2674
Merit: 1030
Yes I am a pirate, 300 years too late!
Congrats!!!  I keep hoping to see #265 and my address!!!
member
Activity: 259
Merit: 18
Congratulations to bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet with approximately 1.14PH!

Code:
[2022-02-01 08:27:35.681] Possible block solve diff 36770979250673.867188 !
[2022-02-01 08:27:35.728] BLOCK ACCEPTED!
[2022-02-01 08:27:35.730] Solved and confirmed block 721310 by bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet
[2022-02-01 08:27:35.731] User bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.731] Worker bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.767] Block solved after 5496218477727 shares at 20.6% diff

https://btc.com/btc/block/721310

Congrats..
Love this pool is grabbing these blocks!

Beautiful. You're doing the lord's work -ck
member
Activity: 444
Merit: 15
Congratulations to bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet with approximately 1.14PH!

Code:
[2022-02-01 08:27:35.681] Possible block solve diff 36770979250673.867188 !
[2022-02-01 08:27:35.728] BLOCK ACCEPTED!
[2022-02-01 08:27:35.730] Solved and confirmed block 721310 by bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet
[2022-02-01 08:27:35.731] User bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.731] Worker bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.767] Block solved after 5496218477727 shares at 20.6% diff

https://btc.com/btc/block/721310

Congrats..
Love this pool is grabbing these blocks!
copper member
Activity: 2324
Merit: 1348
Congratulations to bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet with approximately 1.14PH!

Code:
[2022-02-01 08:27:35.681] Possible block solve diff 36770979250673.867188 !
[2022-02-01 08:27:35.728] BLOCK ACCEPTED!
[2022-02-01 08:27:35.730] Solved and confirmed block 721310 by bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet
[2022-02-01 08:27:35.731] User bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.731] Worker bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.767] Block solved after 5496218477727 shares at 20.6% diff

https://btc.com/btc/block/721310

Wow.... Congratulations !
newbie
Activity: 7
Merit: 1
My PC is Windows 11. I downloaded cgminer-4.11.0, but cgminer.exe was missing. I think you need a build, but can anyone please tell me how to do it?
legendary
Activity: 2405
Merit: 1459
-> morgen, ist heute, schon gestern <-
Hi. I've tried using both the . and then the _ and get same result. It still shows network as Dead for ckpool via port 3333. I've tried the other ports too per the CK Pool Instruction.

@HagssFIN
There are 2 common reasons for not being able to connect:
1. The most common one is that you have a typo in your bitcoin address, or added a space somewhere, like before the address.
2. You are in a part of the world where routing is blocked to the datacentre where the pool is hosted - this is unfortunately out of my control as I don't block anyone from mining there.

you may try the passthrough then.
stratum+tcp://rfpool.org:3334
It is still running with users on it, so I keep it alive.
 
https://bitcointalksearch.org/topic/m.54581374
newbie
Activity: 17
Merit: 0
Congratulations to bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet with approximately 1.14PH!

Code:
[2022-02-01 08:27:35.681] Possible block solve diff 36770979250673.867188 !
[2022-02-01 08:27:35.728] BLOCK ACCEPTED!
[2022-02-01 08:27:35.730] Solved and confirmed block 721310 by bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet
[2022-02-01 08:27:35.731] User bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.731] Worker bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.767] Block solved after 5496218477727 shares at 20.6% diff

https://btc.com/btc/block/721310


CONGRATULATIONS    Grin Grin Grin Grin Grin
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hi. I've tried using both the . and then the _ and get same result. It still shows network as Dead for ckpool via port 3333. I've tried the other ports too per the CK Pool Instruction.

@HagssFIN
There are 2 common reasons for not being able to connect:
1. The most common one is that you have a typo in your bitcoin address, or added a space somewhere, like before the address.
2. You are in a part of the world where routing is blocked to the datacentre where the pool is hosted - this is unfortunately out of my control as I don't block anyone from mining there.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Congratulations to bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet with approximately 1.14PH!

Code:
[2022-02-01 08:27:35.681] Possible block solve diff 36770979250673.867188 !
[2022-02-01 08:27:35.728] BLOCK ACCEPTED!
[2022-02-01 08:27:35.730] Solved and confirmed block 721310 by bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet
[2022-02-01 08:27:35.731] User bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.731] Worker bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.767] Block solved after 5496218477727 shares at 20.6% diff

https://btc.com/btc/block/721310
Jump to: