Testerx: Alternate cryptocurrency pools are a feature that's been implemented in other forks of SimpleCoin, so it should be doable. I will put it on the list as a future feature.

Xenland: Your code sure goes places.

I'm real busy with the end of the semester right now, so I'm not really doing anything besides occasional bugfixes. Hopefully once I finish some final projects I'll be back at it!

I fixed the issue that BitCoins06 pointed out.

Unfortunately it's the last few weeks of the semester for me, so I'm very busy with class projects. I'm hopefully going to be working on this a lot more once the semester ends in May.

For the time being I'll keep fixing bugs as they're reported and maybe get started on database abstraction.

Hello all,
In my quest to start my own small mining pool I found that SimpleCoin has been out of development and no longer even worked because of a change in MyISAM! I have decided to fork it and keep developing it as SimpleBTC. Right now it is just SimpleCoin with updates and bugfixes, but for the first major release I am planning to have templating and database abstraction in place.

Features:

• Proportional or PPLastNShares
• Instant or Automatic cashout available with positive balance!
• Worker monitor for less downtime
• Current Round Payout estimation
• JSON account/worker monitoring API
• Dynamic stats/setting caching (more responsive/less overhead)
• Live round stats
• Stats charting
• Memcached support
• Process locking
• Handling large stats on replication server
• Active development

Future Development
Multiple database support (via PDO), templating, redesigned interface, news page, etc...

Demonstration
The tiny pool at http://bitcoin.nmtbaycon.org will almost always be running the development version!

Download
There is not yet a "stable release" although the repository is always in working order (since the code in the repo is run in production!).

Repository, Issue tracker, etc
https://github.com/jcrawfordor/SimpleBTC

Hopefully this is useful to someone out there. Questions/comments? Reply here, PM me, email me, whatever!

I'm also thinking about building a mining rig. What manufacturer's 7950 did you end up buying? I'm looking in to picking up some AMD cards to put in a spare machine for this purpose.

I've been involved in bitcoin on and off for a while now, including mining for a while with about a 500 mhash/sec output. Someone recently proposed starting a mining pool and that got me back in to it, mostly because of my interest in working on some of the software for mining pools - it's in a very poor state right now.

This is not really announcement-ready yet, but I've just started on an overhaul fork of the SimpleCoin web frontend that I'm calling SimpleBTC. Right now I'm just working on bugfixes but over the next few days I'm hoping to make some serious improvements, initially just under the hood to make it more maintainable and easier to install. Take a look here: https://github.com/jcrawfordor/SimpleBTC.

Hello,

I'm working on setting up a bitcoin mining pool right now, really just as a personal amusement for the weekend. I'm running in to a couple of problems right now that I would like to ask this community about, but I don't think I'm likely to get a response in this forum since they're reasonably advanced in nature. Here's the two problems:

* As noted elsewhere the memory consumption of bitcoind seems to increase continuously until it's killed for OOM reasons. I see people talking about using a watchdog process or just running bitcoind in a while loop to restart it each time it's killed, but these seem like kludgy solutions. I'm using a watchdog process to restart it and ulimit to try and keep its consumption from impacting other software right now but I'm curious about solutions being used by others.
* pushpoold says in its config file that you should not set it to connect to the bitcoind on the RPC port (8332) or you will get 500 errors. It has port 8333 (the P2P port I believe) set instead. When I run it with this default it sits for a while and then times out (error about no response being sent), but if I change it to use port 8332 it works just fine. I don't see a problem with using 8332 but the config file warns against it so I wanted to ask someone with more experience on the matter about this.

Other than that things have gone alright. I'm using simplecoin as a frontend, and I plan to make some modifications to it and release those modifications as open-source. I'm also planning to write up a guide on how I created the pool server since I haven't seen a lot of thorough documentation in this area.

Thanks.