- statistics for 2012 so far (Jan 1st ... now): 36 days / 45 blocks = 0.8 days per block (and not 0.42).- statistics for the last couple of days would be even worse.

If you're gonna do that, you'll also need to average the "averages" p2pool printed since Jan 1st. Otherwise you're comparing apples and oranges...

The "average" p2pool prints is just the pool hashrate displayed another way; it's not really an average, it's an expected average if the hashrate stayed at whatever it is when it's being printed.All you've shown so far is that the pool hashrate is likely increasing, which doesn't really come as a big surprise...

btw ... I didn't bring in my definition of average - I only quoted the output of p2pool ("Average time between blocks: 0.42 days"). And that's just not correct.

That is a very rough average based on the current difficulty level combined with the estimated hashrate. Since the difficulty and estimated hashrate change every 10 seconds, you can't accurately compare the quoted average over a period of minutes, let alone weeks.

Hashing blocks has huge variance. While the average time for p2pool to find a block might be 10 hours, there's about a 10% change it'll end up being 30 hours.

One block found is one block found. If the pool size is 1, 10 or 1000.

The statistics (and maybe more) is simply wrong.

The "Average time between blocks" datum is misnamed. It should be "Expected time between future blocks" or better yet "Expected time until next block". It does not average historical data, but estimates the future based on the current Bitcoin difficulty and P2Pool hash rate.

What we really need is a frontend/installer for P2Pool, perhaps we need to get a bounty going.

Is that really necessary? On Windows, you can now just unzip the executable file and double-click it, and on Linux it's just ./run_p2pool.py (clicking it in a GUI might work too). However, Uukgoblin has been working on a little GUI configurator - see here: https://github.com/goblin/p2gui/blob/master/screenshot.png

I still really think running with bitcoin, or a miner would help speed adoption...or better yet make a bundled set, with preconfigured p2pool, bitcoin, and miner. Set it and forget it. I flipped through the BTC source -- you should just be able to add another tab in QT, right?

What we really need is a frontend/installer for P2Pool, perhaps we need to get a bounty going.

Is that really necessary? On Windows, you can now just unzip the executable file and double-click it, and on Linux it's just ./run_p2pool.py (clicking it in a GUI might work too). However, Uukgoblin has been working on a little GUI configurator - see here: https://github.com/goblin/p2gui/blob/master/screenshot.png

I can't speak for anyone else, but i'm pretty dumb and my spare time is dwindling more everyday. IMHO, anything that makes the transition to p2pool easier will make the concept more popular.

What we really need is a frontend/installer for P2Pool, perhaps we need to get a bounty going.

Is that really necessary? On Windows, you can now just unzip the executable file and double-click it, and on Linux it's just ./run_p2pool.py (clicking it in a GUI might work too). However, Uukgoblin has been working on a little GUI configurator - see here: https://github.com/goblin/p2gui/blob/master/screenshot.png

Believe it or not, just "double-clicking" on it doesn't let you use any options/flags. Some of us like those things. Like the ability to set a fixed payout address. Personally I wrote script files for both my linux and windoze boxes. But there are a fair amount of people who don't know how to make a .bat file, and set it to auto-run at start-up.

While I personally use cgminer and p2pool because I think that they are the best of the choices out there, it is far easier to set up GUIminer and DeepBit. Why? No command line, no flags to set, no "why the fuck are my shares so low" etc...

Face it man, the majority of "miners" will spend 5 minutes setting up a miner and a pool, and walk away. They will never take the step to something better if it involves more work.

What we really need is a frontend/installer for P2Pool, perhaps we need to get a bounty going.

Is that really necessary? On Windows, you can now just unzip the executable file and double-click it, and on Linux it's just ./run_p2pool.py (clicking it in a GUI might work too). However, Uukgoblin has been working on a little GUI configurator - see here: https://github.com/goblin/p2gui/blob/master/screenshot.png

I can't speak for anyone else, but i'm pretty dumb and my spare time is dwindling more everyday. IMHO, anything that makes the transition to p2pool easier will make the concept more popular.

+1

If I don't have to spend time setting up the p2pool miner, I won't want to spend time setting up the miner. So, easier the better.

I just joined p2pool and so far it seems pretty tremendous. I have some questions.

1. Is it recommended to give an address with the -a flag and keep this address the same always? Does it make a difference?

2. If I close and open again p2pool, do I lose any of the work that I did? The 'current payout' seems to go back to 0. If I have a bunch of 'accepted' in the cgminer but still 0 shares in the p2pool, then reconnect, do I lose the work that I did? This is probably a silly question but I want to make sure

2. If I close and open again p2pool, do I lose any of the work that I did? The 'current payout' seems to go back to 0. If I have a bunch of 'accepted' in the cgminer but still 0 shares in the p2pool, then reconnect, do I lose the work that I did? This is probably a silly question but I want to make sure

Your work is remembered by the network, so nothing is lost. If you specify an address, your p2pool will show the correct "current payout", as it can see your shares in the chain. If it generates a new address, it shows the payout to that address. Don't worry, if a block is found while your previous shares are still valid, you will get paid at both addresses.

with latest cgminer (2.2.1) using dynamic intensity forces a single therad per GPU, so I've set it to dynamic right now, let's see what happens.

Hi Guys,

after a _long_ weekend I'm now able to mine for p2pool correctly

I've made several changes and I don't know which one was the good one (or ones), so I list them here:

installed ntpd, xubuntu does not install it by default, and my time was 4 seconds behind correct time, this did not give any problems with other pools, but maybe p2p is time-sensitive

started cgminer with -g 1, I was setting intensity to default from cgminer menu when started, but maybe it is not the same thing since this way just a single thread is created per GPU

started cgminer with --submit-stale as per forum message which states that current cgminer 2.2.1 needs it when running with p2pool

pointed my miner to my p2pool pc (which is at work, while miner at home) using office IP instead of symbolic-name because symbolic name has a very short TTL and maybe miner was spending time to resolve it

Anyway, right now I've been mining for more than a day, with just three DEAD ON ARRIVAL shares and 65 good ones