Search results

Here's a snip of my log from around 13697 [3276] socket closed [3276] disconnecting node 191.239.5.76:1152 [3276] received block 0000000161403db84ba8d85f5aa1d113428ec5c8c12bb56f4c4f386aafa940cf [3276] Committing 4 changed transactions to coin database... [3276] SetBestChain: new...

If you're using -printtoconsole, a patch was made recently to bitcoin that fixes this problem: https://github.com/bitcoin/bitcoin/commit/283e405c063acfca304acbff505badcbbcb814c9 edit(testnet): sometimes when my P2Pool node sends submitblocks to the daemon i get the error: ERROR: AcceptBlock() ...

When transferring out of a p2pool address I just keep reducing the transfer amount to get the input count down until it goes through, then do multiple transfers. Maybe there's a better way?

It's nice to have a safety-net, but the checkpoint server could also be a source of problems. Seems like it would require considerable effort to continuously make sure it's running properly. If it's running only for limited times there's less chance of problems happening over time. I'm not...

Would it be possible / a good idea to implement checkpoints so that they are accepted for only limited times? Seems like they should only be needed for a short time after hardforks.

Testnet p2pool seems to be working well, using the daemon git forkfix along with dstorm's fb2c8ac p2pool commit. When running p2pool during the fork last week it was obvious there was a major problem. Will keep an eye on the logs for the messages listed in the OP.