Bitcoin Institute

Suggestions for pooled BTC mining?

10 messages BitcoinTalk vess, Ground Loop, FreeMoney, Olipro, Andrew LeCody, Insti August 18, 2010 — September 1, 2010
vess August 18, 2010 19:40 UTC Link to this message

I was wondering today about how to get a pool of mining together: that is, users who wish to could all go in together on mining the next block. The actual block signer signs over the block to the group. Splitting could happen any number of ways.

This would really help new users who want to generate some BTC, a key problem for adoption right now. And, it would encourage slow-computer users to participate in block generation, something that is not very motivating right now for many.

Obviously, there’s the ‘cheater’ problem: a user has no incentive to share once he/she has generated the block. I can’t figure out how to solve that without a client that is patched.

Does anybody else have technical suggestions about accomplishing this? Even patched clients present some interesting problems: one thought I had is that you could include all the transactions to the group inside your block, but that would of course require you had 50+ BTC to start with, or the transactions would be invalid.

Of course, the client can just stay mum about generation until it’s matured, then send it off, and you’d only know once you got your portion.

Thoughts?

Ground Loop August 18, 2010 22:51 UTC Link to this message

I’m puzzled.  Why would anyone do this?

Effectively, we’re already pooled today.  Over the long haul, every 10 minutes, someone gets 50 bones, and it’s apportioned based on CPU speed.

If a slow machine isn’t worth running hot for months on end to search, then why would it be welcomed (at greater value) to a pool including faster machines?  Seems to me that if you found a group of like-minded honest individuals, you’d end up with a cluster of really slow machines, rarely finding a treat, and doling out pennies to each.  Further, anyone inclined to join the pool is already running their machine anyway.

I guess I’m missing the point.

FreeMoney August 19, 2010 00:24 UTC Link to this message
Quote from: Ground Loop on August 18, 2010, 10:51:38 PM UTC

I’m puzzled.  Why would anyone do this?

Effectively, we’re already pooled today.  Over the long haul, every 10 minutes, someone gets 50 bones, and it’s apportioned based on CPU speed.

If a slow machine isn’t worth running hot for months on end to search, then why would it be welcomed (at greater value) to a pool including faster machines?  Seems to me that if you found a group of like-minded honest individuals, you’d end up with a cluster of really slow machines, rarely finding a treat, and doling out pennies to each.  Further, anyone inclined to join the pool is already running their machine anyway.

I guess I’m missing the point.

Just to reduce the variance so that you can get 1BTC/day instead of 50 every 7 weeks. If there was an easy and secure way I guess I’d be a little interested.

Olipro August 19, 2010 05:40 UTC Link to this message
Quote from: Ground Loop on August 18, 2010, 10:51:38 PM UTC

I’m puzzled.  Why would anyone do this?

for precisely the same reasons people run lottery syndicates.

problem is, in a lottery syndicate, obviously you will know who paid into the ticket fund and who didn’t.

How do you plan to verify someone in the syndicate is actually trying to solve blocks?

The best way I can think of is by measuring their average number of hashes per second and then have a secondary target their client must achieve which acts as a proof of work for the syndicate to know that this person is dedicating their CPU resources to generation.

About a week ago in IRC we had a discussion about how to do this, I believe mycroftiv is looking into implementing this kind of system.

It would be your basic client-server setup, the server sends each client a set of data to hash and a starting nonce. The data of course being the block header. The client would generate hashes as quickly as possible looking for a winner, but in order to keep the server informed about how fast it is working (so the BTC can be distributed by CPU-time) the client would create a hash of every 1,000 hashes and send these “meta-hashes” to the server. The server can randomly chose a meta-hash to check, it would then run the same 1,000 hashes and see if they generate the same meta-hash. If the meta-hashes don’t match, then the client is lying. You don’t have to worry about the clients stealing the winning block because the proxy transaction is already signed over to an address that only the server owns.

Ground Loop August 21, 2010 04:42 UTC Link to this message

It seems like this could be accomplished via UI change..

Instead of presenting 50.00 on generated block, compute how long it took and “trickle” the coins into the wallet to feel better about them for longer.

So once you generate a block, you would see pennies start appearing.  Hopefully they would trickle in for as long as it takes to generate your next block, more or less.

😊

(I kid, I kid..)

Insti August 21, 2010 08:57 UTC Link to this message
Quote from: nimnul on August 21, 2010, 8:54:30 AM UTC

What are possible attacks?

The public key I use on the coins I actually generate is different from the one I provide to you, which will never generate.

Edit: Hmm. This would require generating a separate hash. And it would seem silly to throw away a winning hash to spite the group. I should think more before posting.

What about: once I generate a block I leave the syndicate without paying my 50 in?

Insti August 24, 2010 18:15 UTC Link to this message
Quote from: nimnul on August 24, 2010, 5:55:29 PM UTC

If you give generated coin to pool and leave pool it’s not an attack.

But it’s an attack if you keep your generated coin and leave.

You can join the pool again and leave again after first generation without giving anything.

If you repeat this forever, you will be getting 2x more coins a month than without pooling. Or you can participate in N different pools at the same time and get N+1 times more money than would be possible.

First, if there are 5 members in the pool, you don’t get 10 coins each time a coin is generated - you get a share proportional to your CPU power share in the pool. Your share is measured by “pool proof-of-work” as I explained earlier.

Let all pool generated 50 easy blocks, and you generated 10 and then generated one hard block. So you get 10 coins from pool and 50 coins from your own generation.

If everyone else behaves like you, pool will not work as nobody will give any bitcoins to the pool.

I don’t understand this post. Are you trying to explain how leaving early is an attack?

Edit: I do think leaving early is an attack.

Quote from: aceat64 on August 19, 2010, 5:45:58 AM UTC

About a week ago in IRC we had a discussion about how to do this, I believe mycroftiv is looking into implementing this kind of system.

It would be your basic client-server setup, the server sends each client a set of data to hash and a starting nonce. The data of course being the block header. The client would generate hashes as quickly as possible looking for a winner, but in order to keep the server informed about how fast it is working (so the BTC can be distributed by CPU-time) the client would create a hash of every 1,000 hashes and send these “meta-hashes” to the server. The server can randomly chose a meta-hash to check, it would then run the same 1,000 hashes and see if they generate the same meta-hash. If the meta-hashes don’t match, then the client is lying. You don’t have to worry about the clients stealing the winning block because the proxy transaction is already signed over to an address that only the server owns.

You guys are making the same mistake we did when working on this in the IRC chat. The system I outlined would work for distributed generating and allow you to determine how fast each of the nodes are generating hashes, allowing you to pay out based on how much work each user is putting into the pool.

Ground Loop September 1, 2010 01:01 UTC Link to this message

Not to get all mathy, but if your machine is poking along at 150 khash/sec, you’re effectively generating (contributing) about 0.01 BTC/hr for the pool.