I'll try to set a github repo up today. I have to decide whether to branch from forrestv or rav3nPL - I think the second makes more sense because Rav3n is the king of altcoin p2pool, but so far I went with forrestv.

There are two P2P_PORT variables (4 if you count testnet), the client's P2P_PORT which is defined in p2pool/bitcoin/networks.py, and P2Pool's own P2P_PORT which is defined in p2pool/networks.py. It would be impractical to use the same port numbers there - you would get a conflict unless you run the client on a different interface. So I just kept with the 'tradition' of using the same RPC & P2P_PORT as the client, but raising one number - like with bitcoin, client's RPC/P2P ports are 8332/8333, P2Pool's ports are 9332/9333.

The IDENTIFIER & PREFIX variables are indeed random (although 16 characters IICCC*), and serve as a fingerprint. Keeping them consistent is also indeed the best way to keep a strong P2Pool network. One thing though - if we're going to change values, whether it be block period or spread or whatever, it would be a good idea to generate a new fingerprint to avoid internal conflicts.

*If I Can Count Correctly

We should call them zombie shares instead of dead shares. People like zombies. :p

For tips on how to improve your miner configs: section in the official P2Pool wiki and section latencies of the P2Pool efficiency guide.

I found the scrypt_readme file included with cgminer to be incredibly useful.  Much better than trying to copy other people's config.

It basically boiled down to:
1. Delete all the .bin files
2. Start cgminer with minimum flags
3. Build the intensity up until you start getting errors, then drop it by 1
4. Turn up the GPU clocks 25 at a time until the GPU crashes, then turn it down by 25

Job's an orange vegetable.

This is hard to tell. There are combinations of miner hardware (sha256) and configurations that do not fit P2Pool all too well. Though dead shares do not directly count toward your payout, they are still part of the overall process of finding blocks. P2Pool works a little differently with regards to its share system in that it's like a mini block chain, so latency is more important than with regular pools. If you think your rig has latency issues, it is thinkable that it could work better with regular pools. However, P2Pool is usually credited with a higher payout than regular pools. For one, the fee on a P2Pool is the overall fee, while on normal pools the actual fee depends on the automatic & manual payout fee + the configured payout threshold. In addition, by default P2Pool has a 0.5% block bonus - meaning that you get at least 1/200th share in the overall payout on blocks you find regardless of how much hash the other miners are supplying.

For the best answer, I think you'd have to see what you get averaged over a fixed number of blocks at different pools.

Alright everyone!

We will be doing the update in a few hours! I read that a few of you want to help with testing the new update and I would love your help!

I will be at #CGAnomaly on freenode IRC if you want to participate! I will need someone who can compile a windows wallet!

All three P2Pool nodes including anomalypool pay out per P2Pool protocol, which is that a block found = instant payout. If you're not receiving anything even though you had a share in the payout (see the Payout or Graphs tab on any node) and a block was found, then you're on a different chain.. In that case, try restarting your wallet as described earlier in the thread (make a backup of the data directory, move it out of the way, copy your cryptograhpicanomaly.conf and wallet.dat, make sure you add the nodes from https://bt.irlbtc.com/view/437950.msg4961802#msg4961802).

This did work for me. Shoulda thought of it before. 

Thanks.

Did it the third time and it worked, odd.



I used the nodes from this thread and my p2pool node (148.251.15.235) was as the first one in the conf file. Only for the third time clearing the roaming data worked for me, so it`s ok now.

I've taken down my node for now while I help test the new update. The block explorer and my p2pool node will be back up soon once we get this update working.

First time didn't work, still stops at 9:28. Trying again.

OK it worked, I added a USA based node at the top of the conf and got my payments past 9:28