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

[hurricandave]

Here is a few quotes from Bitcoin Wiki, you know, just too intentionally confuse you further!!!   https://en.bitcoin.it/wiki/Main_Page


Difficulty is a measure of how difficult it is to find a hash below a given target.

The Bitcoin network has a global block difficulty. Valid blocks must have a hash below this target. Mining pools also have a pool-specific share difficulty setting a lower limit for shares.



The target is a 256-bit number (extremely large) that all Bitcoin clients share. The SHA-256 hash of a block's header must be lower than or equal to the current target for the block to be accepted by the network. The lower the target, the more difficult it is to generate a block.



Mining is the process of spending computation power to secure Bitcoin transactions against reversal and introducing new Bitcoins to the system[1].

Technically speaking, mining is the calculation of a hash of the a block header, which includes among other things a reference to the previous block, a hash of a set of transactions and a nonce. If the hash value is found to be less than the current target (which is inversely proportional to the difficulty), a new block is formed and the miner gets the newly generated Bitcoins (__ per block at current levels). If the hash is not less than the current target, a new nonce is tried, and a new hash is calculated. This is done millions of times per second by each miner.



The work performed by a miner consists of repeatedly increasing "nonce" until the hash function yields a value, that has the rare property of being below a certain target threshold. (In other words: The hash "starts with a certain number of zeroes", if you display it in the fixed-length representation, that is typically used.)

[1714218676]

1714218676

[1714218676]

1714218676

[1714218676]

1714218676

[1714218676]

1714218676

[lungbubble]

Here is a few quotes from Bitcoin Wiki, you know, just too intentionally confuse you further!!!   https://en.bitcoin.it/wiki/Main_Page


Difficulty is a measure of how difficult it is to find a hash below a given target.

The Bitcoin network has a global block difficulty. Valid blocks must have a hash below this target. Mining pools also have a pool-specific share difficulty setting a lower limit for shares.



The target is a 256-bit number (extremely large) that all Bitcoin clients share. The SHA-256 hash of a block's header must be lower than or equal to the current target for the block to be accepted by the network. The lower the target, the more difficult it is to generate a block.



Mining is the process of spending computation power to secure Bitcoin transactions against reversal and introducing new Bitcoins to the system[1].

Technically speaking, mining is the calculation of a hash of the a block header, which includes among other things a reference to the previous block, a hash of a set of transactions and a nonce. If the hash value is found to be less than the current target (which is inversely proportional to the difficulty), a new block is formed and the miner gets the newly generated Bitcoins (__ per block at current levels). If the hash is not less than the current target, a new nonce is tried, and a new hash is calculated. This is done millions of times per second by each miner.



The work performed by a miner consists of repeatedly increasing "nonce" until the hash function yields a value, that has the rare property of being below a certain target threshold. (In other words: The hash "starts with a certain number of zeroes", if you display it in the fixed-length representation, that is typically used.)

Didn't confuse me at all.  It was merely me thinking in terms of *real* solo mining.  Apparently solo.ckpool.org doesn't behave the same way.  It was my understanding that solo mining that produces accepted work completed the block.  I was right.  Its just that this isn't the same as solo mining even though it is represented as "solo mining".

[hurricandave]

 Its just that this isn't the same as solo mining even though it is represented as "solo mining".

As your knowledge grows, your vernacular will become refined. Whilst blurring the implied indifference of clarification.

[Mikestang]

Its just that this isn't the same as solo mining even though it is represented as "solo mining".

It is solo mining, the only difference being you are not mining against your own node and you are using Ck's architecture which should increase your chance of a successful block solve being accepted by the network, in exchange for 1% of the block reward.  From the home page:

Advantages over regular solo mining:
Mining at solo.ckpool.org avoids the overheads of running a full bitcoin node that requires both great storage and bandwidth for optimal performance.
Solo.ckpool.org is extensively connected to high speed low latency bitcoin nodes for rapid block change notification and propagation.
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.

[lungbubble]

 Its just that this isn't the same as solo mining even though it is represented as "solo mining".

As your knowledge grows, your vernacular will become refined. Whilst blurring the implied indifference of clarification.

I don't see how that's relevant as solo mining, such as mining to your own wallet, is different than this "solo mining".  It wasn't a matter of vernacular, it was a matter of solo.ckpool.org changing the behaviour of the program such that it deviated from what one would normally expect from regular solo mining.

[lungbubble]

Its just that this isn't the same as solo mining even though it is represented as "solo mining".

It is solo mining, the only difference being you are not mining against your own node and you are using Ck's architecture which should increase your chance of a successful block solve being accepted by the network, in exchange for 1% of the block reward.  From the home page:

Advantages over regular solo mining:
Mining at solo.ckpool.org avoids the overheads of running a full bitcoin node that requires both great storage and bandwidth for optimal performance.
Solo.ckpool.org is extensively connected to high speed low latency bitcoin nodes for rapid block change notification and propagation.
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.

Yes, but if a block is "accepted" via normal solo mining, then that means you found A solution to the actual block.  On ckpool, your submissions are "accepted" but are not necessarily actual solutions to the block.  Or at least that's per your communication.

[hurricandave]

There are no configuration options and all miners will initially start out at diff 1024 but" the pool" offers full vardiff support from ultra low speed devices to any sized massive pooled solo farms. While shares have no intrinsic value at all with this solo mining, they provide useful feedback to miners wishing to monitor their performance locally.
-ck
Page 1, Post 2.

"The Bitcoin network has a global block difficulty. Valid blocks must have a hash below this target. Mining pools also have a pool-specific share difficulty setting a lower limit for shares."
quote from WIKI

[lungbubble]

There are no configuration options and all miners will initially start out at diff 1024 but" the pool" offers full vardiff support from ultra low speed devices to any sized massive pooled solo farms. While shares have no intrinsic value at all with this solo mining, they provide useful feedback to miners wishing to monitor their performance locally.
-ck
Page 1, Post 2.

"The Bitcoin network has a global block difficulty. Valid blocks must have a hash below this target. Mining pools also have a pool-specific share difficulty setting a lower limit for shares."
quote from WIKI

Right, I didn't see that post on the first page for some reason and I had actually read through...well...I guess most of them on the first page, I would say all of the page but I guess i would have seen that had I done so.

[Mikestang]

Yes, but if a block is "accepted" via normal solo mining, then that means you found A solution to the actual block.  On ckpool, your submissions are "accepted" but are not necessarily actual solutions to the block.  Or at least that's per your communication.

Your understanding is the same as mine and appears correct.  CKsolo functions like all pools do, in that it "accepts" shares regardless of if they are greater than network difficulty, and like I mentioned (and CK is quoted above) this is shown as feedback so you can see your miner working.

You could set the vardiff to equal network difficulty, then you would only see an accepted share if it had the potential to be a block solve.

[-ck]

Yes, but if a block is "accepted" via normal solo mining, then that means you found A solution to the actual block.  On ckpool, your submissions are "accepted" but are not necessarily actual solutions to the block.  Or at least that's per your communication.

Your understanding is the same as mine and appears correct.  CKsolo functions like all pools do, in that it "accepts" shares regardless of if they are greater than network difficulty, and like I mentioned (and CK is quoted above) this is shown as feedback so you can see your miner working.

You could set the vardiff to equal network difficulty, then you would only see an accepted share if it had the potential to be a block solve.

Additionally a lot of drivers internally use the share counter to give you the hashrate of the device and if no shares are ever accepted they won't display a meaningful hashrate. Shares mean "your share of the block reward" on a regular pool but they do not mean that on this pool since only the block finder gets the block reward (minus my fee.)

[AtraxPool]

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.

[-ck]

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.

[AtraxPool]

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

[-ck]

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.

[AtraxPool]

https://github.com/kanoi/cgminer-binaries/tree/master/AntS3

It seems to be no longer available were would I pickup the updated firmware from now?

[kano]

https://github.com/kanoi/cgminer-binaries/tree/master/AntS3

It seems to be no longer available were would I pickup the updated firmware from now?

https://bitbucket.org/TheKano/cgminer-binaries/src/
then click on AntS3

[AtraxPool]

https://github.com/kanoi/cgminer-binaries/tree/master/AntS3

It seems to be no longer available were would I pickup the updated firmware from now?

https://bitbucket.org/TheKano/cgminer-binaries/src/
then click on AntS3

Great, Thanks.

[Avirunes]

Block Hit by 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY. Congrats !! 

https://btc.com/000000000000000000a4e67b4d80f7b478c5a83afcf4ab2da64894a057109e2a

[-ck]

Block Hit by 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY. Congrats !! 

https://btc.com/000000000000000000a4e67b4d80f7b478c5a83afcf4ab2da64894a057109e2a

Code:

[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

https://www.blocktrail.com/BTC/block/000000000000000000a4e67b4d80f7b478c5a83afcf4ab2da64894a057109e2a

[madmartyk]

Congrats to the lucky blockfinder!!!!