While I was napping, my internal network failed. That essentially killed pretty much everything including the boxes that keep p2pool.info fed with up-to-date data. so the last block didn't appear until I rebooted the machine and there is a small gap in stats. It's running normally again, now.

Sorry.

Holy... I had no idea p2pool.info was your baby...! Great resource and it's greatly appreciated on my end!

On the Current Payout graph, would it be possible to show when a coin was found and we collected the amount on the graph? A dot, or an asterisk or something...

Also, would it be possible to overlay another line, showing how many shares we currently have contributing to our payout share?

The program shows how many shares, stale, and dead, I have had in the current run, but having the currently contributing count available would be useful. I'm thinking of manually setting my difficulty higher, but wanna try and make sure I can keep from having 0-contributing-share periods.

I got identified as the owner of this block, even though I was only relaying it Wonderful to see that p2pool blocks get distributed through 2 networks simultaneously, which should be a huge advantage, even if it was not enough this time.

The timeframe is just one day here? With a handful blocks solved by p2pool a day you cant make emaningful conclusions. Sorry, but again it boils down to variance.. ;-)

Ente

He has 3.5 GH/s and shouldn't really see a lot of share-based variance. His current payout isn't affected by the number of blocks found per day, and it changing that dramatically has to be an indication that something is wrong.

The only thing that you haven't shared/shown is share orphan/dead rate. Is that high? What is shown in the p2pool console window for this line:

The timeframe is just one day here? With a handful blocks solved by p2pool a day you cant make emaningful conclusions. Sorry, but again it boils down to variance.. ;-)

Ente

He has 3.5 GH/s and shouldn't really see a lot of share-based variance. His current payout isn't affected by the number of blocks found per day, and it changing that dramatically has to be an indication that something is wrong.

The only thing that you haven't shared/shown is share orphan/dead rate. Is that high? What is shown in the p2pool console window for this line:

huh, tricky one!It all looks good to me, on your end.Could you paste a whole "block" of info from p2pool? Including sharechain-size, network-hashrate etc? Maybe some split-chain issue, or general share-chain issue? Either that (network probs outside your farm), or some of the graphs do lie..

Well, your payout has gone up again, but it will take a day or so of constant running to push that payout rate back up.

The fee shouldn't affect you, since the --fee tag is only applied to people mining on your node with their payout address as a username, for example if your running a public node. And even if you did do it that way, those fees should be put into the wallet on your P2Pool node.

Well, your payout has gone up again, but it will take a day or so of constant running to push that payout rate back up.

The fee shouldn't affect you, since the --fee tag is only applied to people mining on your node with their payout address as a username, for example if your running a public node. And even if you did do it that way, those fees should be put into the wallet on your P2Pool node. [/quote]

Are you mining to a different address by setting your miner's username to a Bitcoin address? The "current payout" graph only displays bitcoins going to the default address. Did you maybe change your miner's username to a Bitcoin address about 24 hours ago..?

I can't get 0.6rc4 to work anymore. bitcoin-qt is simply "Not responding" all the time. Is there a better version of bitcoin out there?

- use bitcoind instead bitcoin-qt- is the bitcoin.conf right?- is the blockchain completely loaded? (check with bitcoin-qt and/or "bitcoind --getinfo")- you may use either the newest 0.6.x beta or the newest 0.5.y "stable beta"