Quote from: Bitcoinasourus on May 22, 2014, 01:47:34 PM

Quote from: svk31 on May 21, 2014, 08:08:18 PM

Quote from: svk31 on May 21, 2014, 07:54:56 AM

I've added PLX tracking and payment capabilities to the proxypool code, it works the same way as MON does. If you're mining on my node, please send me your VTC and PLX address if you'd like to also receive PLX, by mail to the node email address or by PM here. I'm confident tracking is working, payments should work too but will need to find a block first for confirmation.

I'm at work now but will try to add PLX to the front-end this evening, and then if I have time this weekend I'll push it to github for anyone interested.

VTC/MON/PLX p2pool Node
Running on the ~~third~~ second VTC p2pool Network, very low DOA rates and stable, restarted this morning to add PLX and switch network.
MON balance is currently positive so you'll get paid as soon as you hit the threshold for payouts.
Fee: 0.5%

Frontends:
MON/VTC/PLX: http://109.24.254.169/proxypool/
Traditional: http://109.24.254.169:9172/static/

To connect your miner use the following setting:

"url" : "stratum+tcp://109.24.254.169:9555",
"user" : "",
"pass" : ""

Update: IT'S WORKING

I've successfully updated the proxypool payout script and sharelogging as well as the frontend in order to handle PLX. You can see it in action by following the link in my signature.

I just tested the transactions by sending 15 PLX to the p2pool account, and the script immediately sent me my due of 7.9 PLX. It also correctly tagged shares as paid. I can't find a block explorer for PLX so at the moment the transaction hash link is a dead-end, but the sum is correct.

Feel free to hop on if you want to triple mine but also support the p2pool. I'll try to get the code available this weekend but I'll be a bit low on time..

Been mining on your node since I seen it. I don't see my wallet address in the list of hashrates any more?

Is it showing up now? Don't forget to send me your PLX address

I encountered a bug in the payout script earlier today, I believe it was constructing a transaction with user="none" which is the default value when no PLX address has been set, and it made the script crash. I've now corrected it and it's running fine. When the script crashed it made all the addresses disappear from the "Active users" category, as no new shares had been registered in the last 5 minutes. Unsurprisingly this all coincided with Teamviewer servers taking a crap, meaning I couldn't log onto my pc to fix things..