[Quick Start]

Besp.in Bitcoin mining pool is a cluster of publicly available P2Pool servers. No registration is required; just use your Bitcoin payment address as the username and any password. P2Pool uses the PPLNS method to determine rewards; Besp.in has a 1% mining pool fee.

My aim is to provide highly reliable servers for miners to use. Each server has a dedicated  Intel Xeon E5-2680v2 CPU; bitcoind and P2Pool each have their own dedicated SSD. Automatic monitoring scripts are monitoring bitcoind and P2Pool and will restart those processes if they happen to go down. Even so, in case there is a problem that does not resolve itself, you can email me at support@besp.in.

Quick Start
Point your miner to the servers below to start mining:

Server location	Server address
US	http://us-1.besp.in:9332/
US	http://us-2.besp.in:9332/

Example CGMiner command line:

Code:

cgminer -o http://us-1.besp.in:9332/ -u YourBitcoinAddress -p han

You can check current payouts and other statistics at any P2Pool node:
http://p2pool.info/
http://us-1.besp.in:9332/
http://us-2.besp.in:9332/

If people are interested, I will add more servers to the cluster. I am thinking of adding some servers in the EU as well. What do you think?

Of course, running servers like this costs a lot of money, which I am paying out of my pocket right now. Donations are welcome: 13BfYHeYoPYSvvAJzeX1k2gGZ4AcPUs5Hu

- Nik.

Hi,

I'm looking at setting up a small cluster of P2Pool nodes for anybody to use, and was wondering what a good high-availability configuration looks like.

Since I'm going to set up more than one server, I'd ideally like the mining clients to automatically switch over to a different server in the cluster if the server they're connected to goes down. I can think of two ways to do this:

1. DNS. I'll provide a server address such as http://us.example.com/. "us.example.com" will resolve to multiple IP addresses (multiple A records), each of which is a node in the cluster. Do current miners support this form of failover?

2. Load balancing. If the miners do not support DNS-based failover, I could put a load balancer in front of the actual nodes in the cluster. However, I'm concerned that the load balancer itself will add some latency to the connections, so I'd rather not go this route.

Can somebody shed some light on this? Thanks!

- Nik.

(I'm not a newbie to Bitcoin. Just posting here because I just signed up for a new account and can only post in this forum. Would be great if somebody could move this thread to the appropriate Mining/Pools subforum.)