My November Jupiter is working fine (660 GH/s with 2% HW errors and 0.1% rejects), although I am using the cgminer-tune binary from here and I am using --load-balance to split my hashing between btcguild and eligius.

My only problem is that when the miner initially starts up, there are a few moments of insanity until the first vardiff adjustment makes the share difficulty reasonable.  I wish there was a way to specify a starting difficulty other than '2'.  I'd probably pick something like 64.  Then my Jupiter and BitFury rigs would vardiff up to something like 256/512 and my BFL Singles would vardiff down to 16/32 as appropriate.  I gather that wizkid057 is working on an enhancement to bfgminer, which is fine, but won't help me on devices that have their own mining software (e.g. my BitFury).

Yes, and in that example case making any statement of "what I earned over the past couple months" is not statistically meaningful.

That example was for 322 MH/s which is insanely small given current bitcoin difficulties.  The only reason to be mining with 300 MH/s at all is if you are betting on another 100-fold increase in the BTC/USD exchange rate making your handful of satoshis valuable someday.  Or alternatively if you don't care about profits and are just mining for the fun of it.  Whatever the reason, definitely don't bother mining on p2pool with that amount of hashrate.

cgminer no longer supports scrypt or GPU mining.  Check here for some folks that may be able to help:  https://litecointalk.org/index.php?topic=6925.0

p2pool have never been good for small miners.  All that has changed is how much hashrate qualifies as a "small miner".  Bitcoin difficulty has increased 1000x in the last 18 months.  Today's 10 GH/s miner is just as screwed as a 10 MH/s miner from 18 months ago.

I would go with "over time" = at least 100 times whatever your expected time to find a share is.

As I said, it will be xxx.xxx.xx.249.  So if your home network is 192.168.1.x, then it will be 192.168.1.249.  Or if your home network is 10.0.1.x, then it will be 10.0.1.249, etc.  So figure out the IP address of some other computer on your network and then change the last number to 249.

Just to make sure we are on the same page...  This is not something that you plug into a computer via USB.  It is a computer.  You plug in the ethernet cable, a USB Keyboard, a monitor via HDMI and when you power it on and you will see Linux boot up.  If you don't want to attach a USB keyboard and monitor, you can ssh into it by connecting to pi@xxx.xxx.xxx.249 where xxx.xxx.xxx is the prefix of whatever your internal network is (it used to be hard coded to 192.168.1.249 but that changed with v3 so that it tries to detect your normal network IP and then just uses a .249 address on that subnet).  Alternatively you can just point your web browser at http://xxx.xxx.xxx.249 and you can do the basic configuration steps from there.

Please be more specific on what you have tried and more importantly what you are stuck on.  "It's not working" is not something we can give a meaningful response to.

Luck

And p2pool.info has been moved to forrestv's servers.  If you get any errors right now, they are probably related to us making DNS changes and the errors will go away over the next hour as your DNS cache expires.  If you still see errors after a few hours, let us know.

Not that I know of.  However, I re-exported the database as .sql files as well.  Note, these are still SQL Server specific.  Also, they are massive (as compared to the binary .bacpac file), so I moved all the data exports to its own repository:

https://github.com/ervwalter/p2pool.info-data

The source code is now on GitHub:  https://github.com/ervwalter/p2pool.info

I'll work with forrestv to get it up and running on a new official server and then will transfer the domain name to him.  It's open source and so other are welcome to setup their own unofficial copies of the site, if they want to play with it for some reason.  Out of the box, the easiest (but not the cheapest) way to deploy it is on Windows Azure.  It's as simple as setting up a web server and a database server there and then pushing the code to the web server using git.  Setting it up on a non-Azure windows server is probably relatively straightforward as well (and may be much cheaper), but the specifics are left as an exercise for the reader.

Awesome.  I'll find you on IRC sometime or send you a PM to discuss the details and to help get it up and running elsewhere.

It's not the SQL Server that is the problem.  It's the web server.  The site does a lot of number crunching every time it calculates block durations, luck, etc.  That's CPU expensive, so it also caches essentially all of the results in memory (which include, among other things, hashrate data points for every 5 minutes for the past year+, so lots and lots of data in RAM on the web server).  I imagine there are other inefficiencies as well that are in the code, but I have not taken the time to investigate and track them down.  You're welcome to do so once the code is on GitHub.

It would fit fine on a server if it was by itself, but it's not.  It's on the same virtual machine as my other site with is much more popular and a more intensive web application.  There's just not room for the p2pool app on that VM anymore.  If the p2pool app used minimal resources, it would be fine, but it doesn't.

The Future of p2pool.info

As some of you know, I developed the p2pool.info website back when p2pool first started to take off because I was looking for a way to understand the blocks that p2pool finds, the pool's hashrate over time, etc.  This was at a time before p2pool has its own local web interface built in.

I no longer mine on p2pool info myself, but I've been happy to continue hosting p2pool info for the benefit of those that do because it currently runs on the same web server as one of my other non-bitcoin related project, and I'm already paying for those servers anyway.

Unfortunately, things have changed in the past few weeks.  My other web application has grown in popularity, and p2pool.info itself has doubled in popularity in the past two weeks (mostly with hundreds of new users out of China).  The result is that the p2pool.info activity no longer fits easily on the same server hardware as the other site. To keep my other web site up and running smoothly, I need to move p2pool to its own server, but that is not a cost I am willing to cover.

There are a couple options here.  

Option 1 is to just let p2pool.info fade away into history.  p2pool now has a decent web interface built in, and maybe that is good enough for everyone.

Option 2 is for someone else to take over ownership of p2pool.info (and assume all the costs).  The catch is that p2pool.info is not built with technologies that the typical bitcoin fan is probably used to (it's not linux/php/python/mysql/etc).  The application is an ASP.NET MVC application written in C# (and HTML/JS) and SQL Server as the backend database.  It's currently hosted in Windows Azure, but in theory could be hosted on any IIS/WIndows host without significant development changes.

What happens next is probably up to the community, and my short term plans are compatible with both options.

1. Sometime in the next few days I will make the code of p2pool.info open source and post it on GitHub.

2. I will also take create a data bump from the SQL Server database and make it also available on GitHub so that anyone that wants to host it can load all the existing historical data about p2pool.

3. I will take p2pool.info offline, or more probably will replace it with a static page that explains the situation.

I know p2pool.info is popular and is used by almost 1000 people per day.  Ideally, someone will want to take the code and host it elsewhere.  In fact, if someone wants to commit to doing that in the short term, I'd be happy to delay #3 for a bit to allow them time to get the replacement servers up and running.

Or if someone wants to read the code, understand what it's doing, and rewrite it in PHP/Phython/NodeJS/etc, I'm also cool with that.  I'm also willing to transfer the p2pool.info domain name to forrestv or anyone else established in the community that the community reaches consensus on so that the domain can continue to be used.

I'm sorry to be pulling the rug out with such short notice, but I have to do something along these lines to get my other web application working reliably as quickly as possible.

No, they have all been sold.

I have a cron job that backs up my wallet to Dropbox every 15 minutes...

These have all been sold.  Thanks all.

Ok, I'll await your PM.

This auction is for 5 Casascius Physical Bitcoins.  These coins were purchased directly from Casascius and have never been circulated.  The holograms are unopened and intact.

Terms

• This auction will run until at least 2:00am UTC on November 12th based on the forum's clock.
• Any bid in the last 5 minutes of the auction will extend the auction until at 5 minutes pass without any additional bids (i.e. each last minute bid will add another 5 minutes to the auction until the bidding dies down).
• You can bid on coins individually or as a set as long as your are crystal clear on what your bid is for.
• Shipping within the U.S. is included via Priority Mail from the U.S. Postal service. Shipping outside the U.S. is entirely at the buyer's expense (including any customs or related fees).

1 BTC Coins, 2011 Series 1

There are three 1 BTC 2011 coins available.  These are the version with the typo in the hologram (casascius is spelled casacius in the repeating part of the hologram).

Starting bid: 1.5 BTC each
Buyout price: 3 BTC each



5 BTC Coins, 2012

There are two 5 BTC 2012 coins available.  These also have the hologram with the typo.

Starting bid: 6.5 BTC each
Buyout price: 10 BTC each