Join a pooled bitcoin mining effort

[doublec]

yeah, that seems a bit strange,
most of the time we've been around 90-100clients at ~80 000khash/s,
then i noticed >150clients but the hashrate didnt change at all, still was ~80 000k.

Yes, this is interesting. My server is suffering quite a bit of load. It's sitting at 80%-100% CPU utilization with 120 clients. I don't know if this would affect the rate. Possibly someone is connecting and attempting to cheat?

Sometime next weeks I plan to move to puddinpop's latest code and binary drop. This will mean a complete restart of the pool and the chance to move to the 'contributed' distribution method. see the first post here under 'distribution type':

http://bitcointalk.org/index.php?topic=1458.msg16906#msg16906

What are pool contributors thoughts? Change to this method?

I might also move to a beefier server.

[theymos]

What are pool contributors thoughts? Change to this method?

I would prefer "contributed". It seems more fair.

[FreeMoney]

How do the generate transaction coins actually work? I mean generally, nothing about pooled mining. Are the coins actually no good yet? Or is the client set to stop them from being used for 120, but that could be circumvented?

What happens if you have pooled generate coins go to mtgox or mybitcoin? When would they be available? Would they be completely invisible for 120 blocks? Or immediately available?

Generations can't be spent for 100 blocks. Transactions that try to spend them before that will be rejected by the network. The client has an additional 20-block safety margin.

This limit exists because generation transactions within a smaller chain become invalid when merged into a larger chain. If this limit didn't exist and the network was split for a few hours, hundreds of people could find their transactions invalidated if their transactions use any coins from recent generations.

It's impossible to view non-mature generations using stock bitcoind. They will be invisible to MtGox/MyBitcoin until they have matured.

Thanks!

I think you'd do well if we implemented the "pay for good posts" idea.

[BitLex]

What are pool contributors thoughts? Change to this method?

i'd say 'contributed'....i think.
it's a nice advertizer when you can tell people "join the pool and you will get coins, guaranteed!",
that's a nice feature the mainline doesn't have.

I might also move to a beefier server.

the beefier the better. 

what kind of CPU runs the current server?

[doublec]

what kind of CPU runs the current server?

It's running on a linode VPS [1] so is a virtual linux instance sharing resources on a machine with other virtual linux instances.

[1] http://www.linode.com

[Kiv]

I'd been running my i5 for days with no luck, then the first day I joined the pool I had 1.24 bitcoins waiting for me when I got up in the morning

Psychologically this is much more satisfying than getting nothing and then 50. Now if only GPU mining worked on the pool...

[BitLex]

thought about those fraction-of-a-bitcent transactions for short-time-users too,
maybe there could be a required minimum connection time, or a minimum contributed hashcount, or a minimum of 0.01btc or something like that.

 

[theymos]

Bitcoin will randomly discard any sub-0.01 balance you have, so it would probably be better to round down to the nearest 0.01. The server can keep a running sub-cent balance for addresses, and pay them when they reach a cent. If an address doesn't contribute for a while, their balance can be returned to the pool. This also solves the problem of people who don't contribute much.

[doublec]

I plan to switch the pool to puddinpop's latest server version at 5:00 am Monday 6 December UTC. That's 5 hours from the time I posted this. This will require contributors to update the miner software. I'll post here when the switch is done. The server will use the 'contributed' method.

[doublec]

I updated the server on 173.255.205.10 early since there were only 4 clients connected. Instructions updated here:

http://www.bluishcoder.co.nz/bitcoin-pool/

Basically you need the new client binary. The windows version is now called remoteminer-cpu.exe and the arguments to it require '=' instead of a space between the '-address' and its value (and '-server' and its value).

There's also a remoteminer-cuda.exe for those with a cuda compatible GPU.

Let see how well this handles load. If it's fine I'll take down the other server.

[bober182]

I have updated and am on the new server but even after generating for 3 minuits it says Address XXXXXXXXXXX not found in block being solved. why?

[doublec]

I've noticed this too. I asked puddinpop about it in the other thread.

[FreeMoney]

I updated the server on 173.255.205.10 early since there were only 4 clients connected. Instructions updated here:

http://www.bluishcoder.co.nz/bitcoin-pool/

Basically you need the new client binary. The windows version is now called remoteminer-cpu.exe and the arguments to it require '=' instead of a space between the '-address' and its value (and '-server' and its value).

There's also a remoteminer-cuda.exe for those with a cuda compatible GPU.

Let see how well this handles load. If it's fine I'll take down the other server.

Me too, not found. Did you switch to contributed and rounding is causing this?

Contributed method is bad imo.

[BitLex]

Address XXXXXXXXXXX not found in block being solved

same here on both, cpu and cuda miner,
cuda-miner does less than half of what i get using m0's (or puddinpops older cuda-versions).
m0's = 45M
remote-cuda= 17M

[doublec]

cuda-miner does less than half of what i get using m0's (or puddinpops older cuda-versions).
m0's = 45M
remote-cuda= 17M

puddinpop noted to expect this:

Also, there is an experimental remote CUDA client included in the release.  Expect half the hash rate you get with the regular CUDA miner built into the standard client.

[doublec]

Me too, not found. Did you switch to contributed and rounding is causing this?

Contributed method is bad imo.

Why is it bad? I asked before switching and the majority of the responses requested contributed.

[BitLex]

puddinpop noted to expect this

noticed that, just wanted to confirm it.  

it works, that's a start.

[kiba]

Code:

Attempting to connect to :8335

Error?

[BitLex]

your missing the ='s, it's not spaces anymore like before,
 -server=173.255.205.10 -address=XXXXX
should work

[doublec]

it works, that's a start.

If there were 100 cuda clients in the pool we'd get a block every 5 hours or so.