Quote from: offbyone on April 30, 2014, 04:45:50 AM

I have a public p2pool node and I'm on the mailing list. I haven't received any instructions yet and I haven't seen updates to the donSchoe github repo for monocle. It would be nice to give p2pool operators or private node operators a head start to at least get the pool nodes ready and prepare the eventual switch over. I'm not even sure how to run the p2pool daemon with monocle support enabled and about any other considerations.

Can you post those instructions at least ?

There will be no changes to the p2pool code before launch. You could merge-mine monocle now if you had the wallet by just starting p2pool with

Code:

run_p2pool --net vertcoin --merged http://monoclerpcuser:monoclerpcpassword@127.0.0.1:monoclerpcport

Since forrestv implemented merged mining support for Namecoin in p2pool some time ago. It's a bit on the proof of concept level though and has since been kind of forgotten by the maintainer I think.

Anyway, the problem with that solution is that it is essentially solo-mining for the p2pool operator (there is no sharechain for the auxilliary chain, that being Monocle in this case). If you connect to it with a vtc address as your username it will still pay out vertcoins to that address as shares are found, but all monocle blocks will have its payout sent to the local wallet on the p2pool node.

Which is why we are releasing a temporary solution (my p2proxy payment scripts) for public nodes, so that they can pay their miners. What p2proxy does is sit between the p2pool node software and the miner and maintains its own shares (with a difficulty different from that of p2pool). This is done to allow it to credit miners for work even when a share hasn't been found yet (like a regular pool). This means that the monocle blocks and Vertcoin p2pool shares that get found will be paid out to the pool's wallet (or some other address if you want) and paid to the miners addresses once the coins mature. But I'm not done updating p2proxy for monocle merged mining yet.. and I now I need to get back to finishing that up.

There will be a better solution later on but it requires a significant amount of time and testing, so it will not be out in time for launch (it was never planned for launch).