This is the exact file I'm using:

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

Delete all the #include "../" include's in src/remote/remotebitcoinminer.h. Replace with one include: #include "../headers.h". That works for me.

Yes but you'd be on the hook for any fraud that that someone committed.

To get the card you need to send photo ID. epassporte had the same requirement and so do similar services (Neteller, etc).

Some changes I had to make to the latest source to get building on Linux:

1. I had to add the following lines to the end of cmake-bitcoinr/CMakeLists.txt

IF(NOT WIN32)
   TARGET_LINK_LIBRARIES(bitcoinr pthread)
ENDIF(NOT WIN32)

It needed pthread to link on Linux. I made it 'NOT WIN32' in case it's needed on Mac too.

2. In src/remote/remotebitcoinheaders.h, removed the "../blah.h" includes and replaced them all with a single:

#include "../headers.h"

This got things included in the right order. Not sure if that's the optimal fix.

Just a heads up - I've updated the server to the latest version of puddinpop's code. Existing running clients will have disconnected for a short time and should have automatically reconnected. To get the benefits of the new server you should update your remote mining client to the latest version. I've updated the pool page with this:

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

One of the nice features of the new client is it tells you how many blocks the server has generated, and how many coins you'd earn based on your hash rate if the server were to generate a block. Also, less bandwidth utilization!

I'm definitely interested in seeing a version of your CPU miner that works against the pooled server. If someone else doesn't get to it I'll try and see what's involved in a few days.

Thanks, I've updated the my pool server to use this. I like the extra information the remote client shows!

I'll be keeping it going as long as puddinpop doesn't mind the use of his code. I'll keep updating the page on my site when things change. If anything it's an interesting experiment in how workable pooled mining is.

puddinpop updated new versions of the software so at some point I'll have to bring the server down and start the new version. This means all currently connected clients will be disconnected for a bit. I don't know if it automatically reconnects or if they have to be restarted.

I updated the instructions to include this step:

Overwrite the $SOURCEDIR/src/remote/remotebitcoinheaders.h with http://www.bluishcoder.co.nz/bitcoin-pool/remotebitcoinheaders.h

It changes the include files so compilation works.

What happens to the existing label functionality? I have a webapp that uses a label to get an address then uses the address. Will this still work or will I have to change the app to use accounts?

The problem is you need an address to have coins sent back to you. I guess you could have a client that ran, prompted for the address, then connected to the hardcoded server. Is that what you mean?

I've started a pooled mining server using puddinpop's remote mining version of bitcoin being discussed in the technical forum: http://bitcointalk.org/index.php?topic=1458.0

Due to high difficulty levels it will take a long time for a CPU based miner to generate a block and get 50 coins. By joining in the pooled effort you combine your efforts with everyone else in the pool. The server ensures everyone is working cooperatively so the average time to generate the coins for the entire pool is based on the sum of their hash values. The pool server then distributes the 50 coins based on the contributions of the people in the pool. See the technical thread for more details.

I've put a page up containing the latest version of puddinpop's software and instructions on how to connect to my server: http://www.bluishcoder.co.nz/bitcoin-pool/

There is currently no version of the miner for GPU's but hopefully one will be available soon. Currently there are 26 clients with a combined khash of 25,000.

I started a webpage with details: http://www.bluishcoder.co.nz/bitcoin-pool/

I'll start a thread once I've got the GPU situation and/or some linux binaries sorted.
Actually probably better just to  a thread. Thread here: http://bitcointalk.org/index.php?topic=2027.0

Unfortunately it seems there's no GPU enabled remote miner client. What is your GPU setup? CUDA or OpenCL? Windows, Linux or Mac?

I'm fine with keeping it running. It runs on a VPS which isn't doing much else. I'll be monitoring the CPU usage and bandwidth but it looks like it doesn't use much.

@davidonpda, I ran it previously but stopped since no one was using it and the client got outdated. I restarted it with puddinpop's recent version yesterday when I posted the IP address. The number of clients, as bober182 noted, has ranged from 2 to 10.

What's needed is a larger number of people to contribute (and hopefully someone with a GPU) so that the lesser powered CPU clients can start getting some benefit from being involved.

I'm not sure if that will happen though as the GPU clients are probably more likely to want to keep mining for themselves.

puddinpop, there seems to be a typo in cmake-bitcoinr/CMakeList.txt. The references to 'bitcoind' in TARGET_LINK_LIBRARIES should be 'bitcoinr'.

Yes each instance of remoteminer only uses one core. The idea (I assume) is to run multiple instances for each core. It will always be a little slower than the normal client due to the communication overhead of talking to the remote server. It should work on guest accounts and the 50BC is split based on the khash contributed to the solution of each connected miner. puddinpop will be able to explain more on this since they wrote the code. I'll try and get a GPU miner connected to up the khash rate soon.

I have a server running you can connect to if you want to test it out. You can connect to it using the windows binaries in the original post. See http://www.bluishcoder.co.nz/bitcoin-pool/ for IP address and other details.