Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 452. (Read 1514844 times)

he quoted my post in which I refer to his server runs this pool.

Frankly I don't know if he is just kidding.

Call it what you want, but that is competition.  That's the exact reason there are pools and hardware races for new technology.  If your not solving a block, someone else is.

Competition is not against the other miners, but against... Well... Probability.  There's no competition actually, only probability.  A hash of difficulty 1 has no chance of solving a block of difficulty 39B.  A hash of diff 39B or more can "solve" it.  Your miner submits hashes to a pool just to prove to the pool that your miner is working.  Otherwise, you shouldn't have to submit shares below the current network difficulty.  When you solo mine (not in a pool), you don't need to submit hashes below the difficulty.  Pool diff and network diff are two different things about the same concept of the "target".

It actually took me some time to understand this!  :-)

Because you don't have 286541.40 Ths of hashing power.

None of your shares count for anything unless they are a block.
Flooding the server with hundreds of shares per second that count for nothing would be a bad design.
Using a difficulty is - as already stated - simply to show your hash rate in cgminer.

A person with 1PHs (1,000 THs) would expect to find on average "about" one block every 2 days.
It may be 1 minute, it may be 20 days. 2 days is just an average expected value for 1,000THs

Also note that 1PHs would be ~14 million 1diff shares a minute.
Yeah that would be a really bad idea to send that to any computer ... instead you'd send ~20 ~700,000 diff shares a minute.
Same result, either one finding a block would still submit the block, but if it was 14,000,000/minute there's also the fact that the pool would die for various reasons (network, CPU) and you'd probably lose the block if you ever found one.

Only a difficulty share 39.5 Billion or higher will solve the block at this difficulty level.  A diff 1 has no chance of solving a block as it doesn't meet or exceed the current difficulty, neither will a diff 1024.

1. No.
2. How is that relevant?

http://en.wikipedia.org/wiki/Con_Kolivas 

I think ck is a female.  Ck stands for Cynthia King (no relation to Martin Luther King)

Yes, thanks.

If there's no competition, then why am I not solving ALL of the blocks?

Besides this, more importantly, each hash (ie difficulty of 1) has the same probability of solving the block as 1/1024 of a miner hashing at difficulty of 1024 (accepted share with difficulty 1024)?

And when my miner has difficulty set, there are no accepted shares below that difficulty.  So I'm assuming that 934/1024 doesn't show up, because it's not accepted.  My understanding is that 1024 is a larger fraction of 39.5B to be solved.

os2sam is right, the 1024 difficulty of accepting shares is just a way of 'accounting' if you will. It's just a way to measure your hashing speed at the pool side as well as limiting the amount of shares needed to be processed by the pool (instead of processing 1024 diff 1 shares the pool only has to process 1 share).

edit: need to type faster  ; basically what os2sam says above my post

The reason for the 1024 diff at start is so that a really high rate ASIC doesn't overload the pool before the auto-diff adjusts.  And the reason for having the lower diff at all is so that you can verify with the pool stats what your approximate hash rate is to see if it match's, roughly, what your mining software is reporting.  It has no effect on the chances of your finding a block.

There is no competition.  Every hash found has an equal chance of matching or exceeding current difficulty, which is around 39.5 Billion.

No, your diff could be set to 39.5 Billion and you would have the same chance of finding/solving the block.

I noticed the pool starts off with difficulty of 1024 and then after a while mine drops down to one and then climbs up before stopping at 4.  Realistically does the miner need to be able to have accepted shares at the 1024 difficulty before having any remote chance of solving a block.  I read posts about "lottery" mining with low hash miners, but I don't exactly see it that way because each mining node is competing against all the others.  So while in theory a low hash, could take "years" to mine a block, that doesn't account for the competition from other miners that will solve them before.  With your other pool you alluded to needing at least 1PH to have a pool.  Does the same apply for solo mining.  Not 1PH, but something along the lines of being able to accept shares at 1024 difficulty?

good luck.  as for the 1 sp20E it is mining at 1.2 or 1.3 th  about 1644 to 1 chance today

no luck with 100ths, will continue with 4ths for now..

this is a pool only in the sense that we use ck to run a  solo server for us.

So all of us combined allow a block to hit often enough to pay   ck for the use of his server.

If you mine solo truly solo you need to run a pc /server blockchain  and a miner.  so the server need to be pretty fast and costs more power.

We all agree the ck's solo server  is worth a fee from the blocks hit. that is the pool so to speak.

@ck  I am going to run a sp20E at the pool for a while.

It is clocked to do about 1th do I need to do anything special in order to get the correct hashrate?

Made an example to help:

Suppose there are 4 miners with each of them having 1 TH/s and the total hashrate of the bitcoin network is 4 TH/s. Miner a and b are mining together in a regular pool and miner c and d are solo mining.

over 100 blocks the average blocks found will be divided like this:
- regular pool  50 blocks (since miner a and b together have 50% of the total hashrate)
- miner c        25 blocks
- miner d        25 blocks

As you can see, miner a and b despite mining in a pool and sharing block rewards have mined exactly the same amount as if they were solo mining. They get twice as many payouts because they share the reward but each payout is 1/2 of the payout of miner c or d.

Now suppose miner c and d don't want to run bitcoind themselves but still want to solo mine so they point there hashrate at ckpool then the division will become like this:

- regular pool  50 blocks
- ckpool         50 blocks

Since ckpool is comprised of miner c and d and they each have half the hashrate of the total ckpool hashrate each will on average have found 25 blocks. Exactly the same as if they were solo mining on there own.

The difference between the two pools is that in the regular pool miner a and b each get 12.5 BTC when a block is found and miner c OR d gets 25 BTC when a block is found by ckpool.

In the end all four miners will have the reward for 25 blocks on average despite the way they are mining, solo or pool mining.


Ofcourse this is a very simple example but it shows that only your own hashrate in relation to the total hashrate of the network matters and not the total pool hashrate.