Developers of new alt-coins should also release the right p2pool config immediately when a coin is launched.
This should become a standard practice, so that every p2pool node uses the exact same configuration creating one homogeneous mega pool. I've seen multiple p2pools for the same coin because multiple persons create different configurations. P2pool is pretty useless if the nodes for the same coin do not all act as one.
I like p2pool a lot but I still fail to find correct configurations for new alt-coins.
This should become a standard practice, so that every p2pool node uses the exact same configuration creating one homogeneous mega pool. I've seen multiple p2pools for the same coin because multiple persons create different configurations. P2pool is pretty useless if the nodes for the same coin do not all act as one.
I like p2pool a lot but I still fail to find correct configurations for new alt-coins.
Yes I agree completely! How can we enforce this?
I think
https://github.com/Rav3nPL/p2pool-rav.git
has the most complete network.py files for most altcoins. So if you want to add a new coin, probably the best way would be to clone that and do a merge request afterwards. That way there won't be 1001 different versions of p2pool on github, each of them working for exactly one altcoin
Just my 2 cent.
... and thanks a lot @TVB for the hard facts.
Yeah, only if people would submit a merge request. That would be ideal.
I will probably start a new fork especially for that.