[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved!

[bugreg]

How long does it take for a user to appear under http://solo.ckpool.org/users/?  I began mining last night, but when I try to enter my wallet address I get a user not found error.  Thanks!

[1714221094]

1714221094

[1714221094]

1714221094

[1714221094]

1714221094

[1714221094]

1714221094

[1714221094]

1714221094

[-ck]

How long does it take for a user to appear under http://solo.ckpool.org/users/?  I began mining last night, but when I try to enter my wallet address I get a user not found error.  Thanks!

What hardware, what hashrate? If you have an insignificant hashrate it could take hours before you show up.

[bugreg]

I have 5 usb miners with a hash rate around 9GH/s.  I started last night.

I'm using bfgminer

[-ck]

I have 5 usb miners with a hash rate around 9GH/s.  I started last night.

I'm using bfgminer

Yes that is an insignificant hashrate. If you were using decent mining software such as cgminer, it would support the stratum standard for setting your diff with the --suggest-diff option which would allow the pool to set the diff according to your choice of diff without waiting for you to submit shares. Nonetheless shares are meaningless when solo mining and only used on this pool as feedback to miners to know they're successfully mining. If you wait long enough shares will start being accepted and then the pool will show your hashrate.

[ComputerGenie]

...hash rate around 9GH/s...

At current diff, you're at about likely to hit a block every 1,034,600 days (2,834.5 years), on average. 

[navbit]

I have 5 usb miners with a hash rate around 9GH/s.  I started last night.

I'm using bfgminer

Yes that is an insignificant hashrate. If you were using decent mining software such as cgminer, it would support the stratum standard for setting your diff with the --suggest-diff option which would allow the pool to set the diff according to your choice of diff without waiting for you to submit shares. Nonetheless shares are meaningless when solo mining and only used on this pool as feedback to miners to know they're successfully mining. If you wait long enough shares will start being accepted and then the pool will show your hashrate.

Hi, I'm new to solo mining with bitcoin.

I'm getting below response after submitting the solved block

{"reject-reason":"Above target","result":false,"error":null,"id":6}

Would you/someone please help me to understand if target, markel and data is correct. I'm trying to write small program just to understand it properly.

Below few details:

JobId:59e1661b0001a6d6
Merkel Root:21e8ee900ff9b9792bc57a43f1697c6497eb3032911644bfedae27576ba6c49e
Target:703d0ad7a3703d0ad7a3703d0ad7a3703d0ad7a3703d0ad7a3703d6210000000
Data:20000000421b6c89f3189ed6f8cc66f9bf6d1a42e24f462700249196000000000000000021e8ee9 00ff9b9792bc57a43f1697c6497eb3032911644bfedae27576ba6c49e5a39ce7d18009645000000 00
Nonce:2514513048
Hash:000000083f8ed4dfae7e7828b83295c62fec400cea97f4269be23a549eb76aa8
Difficulty:4000
Time To Solve(sec):264.3119839

[kfactor]

...hash rate around 9GH/s...

At current diff, you're at about likely to hit a block every 1,034,600 days (2,834.5 years), on average. 

But, this could be your year

[-ck]

First of all thank you Con for making your ckpool software available.  I have one question that I've googled quite a bit but am still unclear what the answer is.

I am running ckpool without CKDB support, and my question is whether or not the rewards for solving a block will go to the BTC address provided by the worker or not?

So for example if someone else wanted to connect to my ckpool instance and used their btc address to connect with, and they solve a block, will they get 99% of the block reward or does it go to the bitcoin address saved in my ckpool.conf file?

That's really a ckpool software question, not a question for this pool. The answer is it goes to the bitcoin address in the conf file though. Only solo.ckpool.org uniquely sends it to username addresses, and no, the code for that is not public.

[Icon]

well i got a question, solving 1/1 diff blocks.. am i wasting my upload bandwidth?

btw it finally accepted my shares now i am flooding 1/1 diff shares

333 mh/s ftw!

Icon

[-ck]

well i got a question, solving 1/1 diff blocks.. am i wasting my upload bandwidth?

It's hardly any bandwidth at all.

[wavelengthsf]

Congrats to 1B5nA9AyLxtRmA16S4YCXR5D1r9Z9j1wBg

[727miner]

Congrats to 1B5nA9AyLxtRmA16S4YCXR5D1r9Z9j1wBg for solving block # 500,433! What a huge block too - 23.35445524 BTC!!  

[NotFuzzyWarm]

Damn, wasn't me and my sticks pointed here...
Congrats to whoever got it, it was a very nice FAT one!

[HagssFIN]

Wow, the block reward and transaction fees are almost the same size with this one.  

Congratulations!

[HerbPean]

Holy cow, that's some ****** luck

{
 "hashrate1m": "1.24P",
 "hashrate5m": "1.39P",
 "hashrate1hr": "1.38P",
 "hashrate1d": "152T",
 "hashrate7d": "29.6T",
 "lastshare": 1513882723,
 "workers": 1,
 "shares": 194000228356,
 "bestshare": 10162266815006.53,
 "bestever": 10162266815006,
 "worker": [
  {
   "workername": "1B5nA9AyLxtRmA16S4YCXR5D1r9Z9j1wBg",
   "hashrate1m": "1.24P",
   "hashrate5m": "1.39P",
   "hashrate1hr": "1.38P",
   "hashrate1d": "152T",
   "hashrate7d": "29.6T",
   "lastshare": 1513882723,
   "shares": 194000228356,
   "bestshare": 10162266815006.53,
   "bestever": 10162266815006
  }
 ]
}

[o_solo_miner]

Congrats to 1B5nA9AyLxtRmA16S4YCXR5D1r9Z9j1wBg

 

Congratulation also from me, for that block!

[Gws24]

Holy crap! 10.85445524BTC in fees  .

Congrats to 1B5nA9AyLxtRmA16S4YCXR5D1r9Z9j1wBg.

[-ck]

Another very lucky and very fat block   23.35 BTC is by far the largest reward seen on a block on the solo pool in the 12.5BTC block reward days.

Code:

[2017-12-21 12:49:34.546] Possible block solve diff 10162266815006.533203 !
[2017-12-21 12:49:34.828] BLOCK ACCEPTED!
[2017-12-21 12:49:35.132] Solved and confirmed block 500433 by 1B5nA9AyLxtRmA16S4YCXR5D1r9Z9j1wBg
[2017-12-21 12:49:35.132] User 1B5nA9AyLxtRmA16S4YCXR5D1r9Z9j1wBg:{"hashrate1m": "1.81P", "hashrate5m": "1.66P", "hashrate1hr": "1.38P", "hashrate1d": "144T", "hashrate7d": "28.4T"}
[2017-12-21 12:49:35.132] Worker 1B5nA9AyLxtRmA16S4YCXR5D1r9Z9j1wBg:{"hashrate1m": "1.81P", "hashrate5m": "1.66P", "hashrate1hr": "1.38P", "hashrate1d": "144T", "hashrate7d": "28.4T"}
[2017-12-21 12:49:35.134] Block solved after 558164732853 shares at 29.8% diff

https://btc.com/0000000000000000001bb297b8d0fa8a218f0b5de5a1987412d40ff2aa583a2d

[kapnmike2009]

can anyone assist with nicehash connection to ckpool

error:
Pool host: de.ckpool.org
Pool port: 3333
Pool user: 1LpK6ZGaVguMytWWRuabnGJB2KrLTp5tyo
Pool pass: x
Algorithm: SHA256

Resolving pool host de.ckpool.org... OK
Establishing connection with proxy... OK
Establishing connection with pool 88.99.146.100:3333... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received mining.set_difficulty... Pool difficulty too low (provided=4000, minimum=65532)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received mining.set_difficulty... Pool difficulty too low (provided=4000, minimum=65532)
Waiting for pool to send higher difficulty.
Received authorization result... OK
Error: Read timed out
Your pool is shown as incompatible therefore we encourage you to contact pool operator to make sure that the pool is using minimal/starting pool share difficulty which is compatible with our service (and thus compatible with today's miners), please send them link to our FAQ on this topic: https://www.nicehash.com/index.jsp?p=faq#faqb3. Thank you!

[Mikestang]

Holy crap! 10.85445524BTC in fees  .

Congrats to 1B5nA9AyLxtRmA16S4YCXR5D1r9Z9j1wBg.

Daaaaaayyyyyuuuuummmm