Quote from: smoothrunnings on March 04, 2014, 03:30:09 PM

Quote from: jedimstr on March 04, 2014, 03:24:34 PM

Quote from: smoothrunnings on March 04, 2014, 02:30:56 PM

Quote from: roy7 on March 04, 2014, 02:04:43 PM

Quote from: smoothrunnings on March 04, 2014, 11:55:43 AM

Quote from: jedimstr on March 04, 2014, 11:48:04 AM

-a bitcoinAddress

do I need to add anything to the bitcoin.conf?

Not to change the node fee payment address. -a sets that address, as jedimstr said above.

So I don't need the disablewallet=1 in bitcoin.conf correct, only need to add the -a {address} to my P2Pool startup string?

No, you don't "need" it... but I use disablewallet=1 anyway since I only use bitcoin-qt (or bitcoin core since that's what we're calling it these days) for it's blockchain RPC and not as a wallet.

Note: disablewallet=1 only works on bitcoind/bitcoinqt OMG10 and 0.9.0 rc2 at the moment (that I know of).

Not sure what OMG10 is? I use bitcoin-qt 0.8.6 on my P2Pool.

Bitcoin OMG10 is the last updated version from the test build of Bitcoin-qt client from the Litecoin Devs (contributing back into the main bitcoin core development). Check it out here: https://bitcointalk.org/index.php?topic=320695

It had a lot of the features that made it into 0.9.0 release candidates and 0.8.6 before they were released.

I don't think -disablewallet is available in the regular 0.8.6 release of bitcoind/bitcoin-qt.