donschoe / p2pool-n Goto Github PK

Crashing on my Windows 7 64bit box. Followed the instructions and have everything installed (successfully compiled vtc_scrypt.pyd with MinGW) When I run run_p2pool.py with --net vertcoin it gets to 'Initializing work...' then drops back to the command line. The line it's stopping on in main.py is 'yield node.start()'. Windows event log reports application error for python.exe with the faulting module being 'vtc_scrypt.pyd'...

Hello!

I am not sure this is an issue, but I don't know how to contact you other way.
Me and other p2pool-n ops need subj very much. As you now, with merged-mining MON and PLX you mine on vertcoin p2p network and other 2 currencies goes solo, so after recent network growth solved blocks on MON/PLX become very rare for p2pool miners. As a result p2pool network hashrate decreases because miners retarget their workers on centralized pools. To avoid this, I think, p2pool must implement multi-sharechain support to allow miners to merge-mine on several p2p networks.
We going to start fundraising on VertcoinMarket to complete this task so I want to ask your advice on how long development may take, reasonable payout for such project or may be is it even possible.
Please respond.

Best regards, Dmitry. [email protected]

https://github.com/johndoe75/p2pool-node-status
http://vtc.coinpools.de:9171/static/

I feel honored that you have included https://github.com/johndoe75/p2pool-node-status which is my attempt to create a more modern and clean p2pool web interface to your p2pool repository.

But is it possible that if you have bug fixes you either open an issue on my repo or put in a merge request? That way the main repo could stay more easily in sync with your code.

P2Pool on VTC is the first time I started using it. I just discovered ltc's block period is artificially low because of their dust problems. Spread for vtc networks.py should have been 12, not 3, I think to match the way all of the other coins do it (based on BLOCK_PERIOD). An argument could be made for more than 12. But 3 is what causes 1-2 GPU miners to have such huge variance, because the share window is 1/4 the "normal" size.

Changing it now would require a new identifier and forking to a new p2pool network. But might be worth it. Not sure... also this does reduce dust. But it also causes so much confusion by tiny miners.

I tried starting up a vertcoin instance alongside a vertcoin2 instance and got this error:

Error binding to P2P port: Couldn't listen on any:9346

thanks