Quote from: luthermarcus on April 27, 2015, 03:55:47 PM

Quote from: jonnybravo0311 on April 27, 2015, 03:49:52 PM

Quote from: luthermarcus on April 27, 2015, 03:47:06 PM

I'm also have an issue of not recieving funds from the last block that was found it gives me an amount but it doesn't show up in my wallet transactions.
I was hoping to use my exchange to cut down on fees. I know they say not to do that but i have been doing it on my exchange from all of my mining and it works just fine. Is there a reason for me not to on the p2p network.

Unlike most other pools, p2pool pays you from the reward generation transaction. In other words, you get newly minted coins. Some exchanges don't play nicely with newly minted coins - they expect the coins to come from a known input transaction, not generated. That's why you don't mine to an exchange.

I really don't like the idea of mining to a wallet that could crash potentially bad idea. Maybe there should be an added change in code to support exchange deposits would be nice. Thanks dude the fast replies.

That would be up to the exchanges. They'd have to alter their code to allow for generated coins.

As for wallets crashing, if you're mining on your own p2pool node, sure that's bad because the p2pool code requires a connection to a functional Bitcoin daemon. Then again, you're taking that chance no matter on which pool you're mining. Heck, you can mine to a paper wallet if you really want to. As long as you've got the public/private keys in your control it doesn't matter.

Personally, I run a p2pool node on a VPS. The Bitcoin daemon is compiled and built with no wallet functionality. It's job is to feed the p2pool node work. The addresses I use for mining are completely separate of that box. I make regular backups of my wallet.dat file and keep those backups stored safely. If I execute any large transactions, I make a backup immediately afterwards.