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

[Gws24]

Great idea

In essence.. The guys pointing huge amounts of hashing power to the pool make my chance of getting that one solving hash even bigger. "It's the pool and it's size what matters." From this you can calculate your "luck factor."

Unless I'm misreading what you mean you're wrong. All that matters is your own hashrate because you're SOLO mining. Just because you do it through a pool doesn't change a thing compared to running bitcoind yourself and mining on that (edit: except that ckpool takes 0.5% if you do solve a block).

EDIT: Every share you solve has a chance of being a block solver. How many shares you can solve depends solely on your own hashrate and the difficulty, not on the total hashrate of the pool.

[thestakes]

Great idea

In essence.. The guys pointing huge amounts of hashing power to the pool make my chance of getting that one solving hash even bigger. "It's the pool and it's size what matters." From this you can calculate your "luck factor."

Unless I'm misreading what you mean you're wrong. All that matters is your own hashrate because you're SOLO mining. Just because you do it through a pool doesn't change a thing compared to running bitcoind yourself and mining on that (edit: except that ckpool takes 0.5% if you do solve a block).

EDIT: Every share you solve has a chance of being a block solver. How many shares you can solve depends solely on your own hashrate and the difficulty, not on the total hashrate of the pool.

Hmm.. But a large pool will "cloud" many shares and distribute them. So you can factor your own hashrate against the pool as opposed to the overall hashrate. That way increasing your "luck factor." The overall hash "cloud" and your single instance in that will not weigh against a large pool with a shared hashrate. That's what I mean. Shares are being solved equally over the Net, but a large pool will "suck in" a significant portion of shares, thus mining in this pool wil change your overall "luck factor" as opposed to "going it alone on the Net." It's about "time" and "volume." Am I wrong?

[ads2003uk]

Looking at Ghash stats they used to be regularly in finding runs of consecutive blocks over a 24hr period but now it seem sthey find 3/4 consecutive with the largest gap between being 34 blocks.. for a size of that pool and a gap that big just shows it's not all about the size of the pool.

[aurel57]

Great idea

In essence.. The guys pointing huge amounts of hashing power to the pool make my chance of getting that one solving hash even bigger. "It's the pool and it's size what matters." From this you can calculate your "luck factor."

Unless I'm misreading what you mean you're wrong. All that matters is your own hashrate because you're SOLO mining. Just because you do it through a pool doesn't change a thing compared to running bitcoind yourself and mining on that (edit: except that ckpool takes 0.5% if you do solve a block).

EDIT: Every share you solve has a chance of being a block solver. How many shares you can solve depends solely on your own hashrate and the difficulty, not on the total hashrate of the pool.

Hmm.. But a large pool will "cloud" many shares and distribute them. So you can factor your own hashrate against the pool as opposed to the overall hashrate. That way increasing your "luck factor." The overall hash "cloud" and your single instance in that will not weigh against a large pool with a shared hashrate. That's what I mean. Shares are being solved equally over the Net, but a large pool will "suck in" a significant portion of shares, thus mining in this pool wil change your overall "luck factor" as opposed to "going it alone on the Net." It's about "time" and "volume." Am I wrong?

The way I understand it every miner here is independent of each other. You are solo mining here no different than if you were doing it yourself on your own pool. The difference is most people dont know how or have the time to set up their own pool, so you pay CK a small share to use his pool, only if you find a block.

[Gws24]

Great idea

In essence.. The guys pointing huge amounts of hashing power to the pool make my chance of getting that one solving hash even bigger. "It's the pool and it's size what matters." From this you can calculate your "luck factor."

Unless I'm misreading what you mean you're wrong. All that matters is your own hashrate because you're SOLO mining. Just because you do it through a pool doesn't change a thing compared to running bitcoind yourself and mining on that (edit: except that ckpool takes 0.5% if you do solve a block).

EDIT: Every share you solve has a chance of being a block solver. How many shares you can solve depends solely on your own hashrate and the difficulty, not on the total hashrate of the pool.

Hmm.. But a large pool will "cloud" many shares and distribute them. So you can factor your own hashrate against the pool as opposed to the overall hashrate. That way increasing your "luck factor." The overall hash "cloud" and your single instance in that will not weigh against a large pool with a shared hashrate. That's what I mean. Shares are being solved equally over the Net, but a large pool will "suck in" a significant portion of shares, thus mining in this pool wil change your overall "luck factor" as opposed to "going it alone on the Net." It's about "time" and "volume." Am I wrong?

The way I understand it every miner here is independent of each other. You are solo mining here no different than if you were doing it yourself on your own pool. The difference is most people dont know how or have the time to set up their own pool, so you pay CK a small share to use his pool, only if you find a block.

This. @thestakes There is no such thing as sucking in shares from the net since every miner or pool generates its own shares. I Think that you are confused by the term 'pool' for this service. Although there is a total pool hashrate it doesn't mean a thing since you're solo mining; it's just a nice statistic to see how many hashrate is pointed at ckpool.

Another way of looking at it is this. Mining solo or in a pool with a given hashrate over the very long term will result in the exact same amount of bitcoins being mined. The only thing a (regular) pool does for you is making payouts much more regular since the block rewards are shared between miners and the bigger the pool hashrate the more regular it becomes. Because the block reward isn't shared on ckpool you are solo mining and it doesn't matter how big the total hashrate is.

Hope I explained it, if not then I'm sure Con or Kano will come along and do a better job. Thing to remember is that only your own hashrate and the difficulty matter and nothing else.

[Gws24]

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.

[philipma1957]

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?

[cisahasa]

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

[philipma1957]

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

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

[fresca]

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?

[os2sam]

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.  

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

[os2sam]

but I don't exactly see it that way because each mining node is competing against all the others.

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

[os2sam]

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.

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.

[Gws24]

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

[fresca]

but I don't exactly see it that way because each mining node is competing against all the others.

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

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.

[thestakes]

Hope I explained it ..

Yes, thanks.

[gallery2000]

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?

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

[bonds]

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?

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

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

[Krak]

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

1. No.
2. How is that relevant?

[os2sam]

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)?

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.