Quote from: m3ta on June 15, 2014, 11:01:58 AM

Seems like something's wrong:

[2014-06-15 11:49:53] Accepted 01686b83 Diff 46.5K/1000 BAJ 0
[2014-06-15 11:53:12] Accepted 2980ecd3 Diff 1.58K/1000 BAJ 0

Node updated: 2014-06-15 12:02:15

0.00 H/s 0.00% no shares yet

There were no blocks between 11:44 and 12:04.
So, those stats are fishy.

The node operator didn't answer this so I will, p2pool issues pseudo shares. Those shares are purely for keeping track of your hash rate and making graphs look pretty. To get a payout from p2pool, you need to enter the p2pool sharechain which works like the btc blockchain. The minimum difficulty share to get into the sharechain for the past month at least has been over 1m. Actually as I'm writing this post, the current difficulty to get into the sharechain 1,197,521.57. if you go to p2pool.io and look @ share difficulty it'll tell you what you miner needs to submit at any moment to get into the sharechain as it updates with each share that's added to keep the sharetime at 30 seconds. So based on what I saw here, if you log showed 1.2M/1000 BAJ 0 then I'd be a little concerned, but like the bitcoin share chain, latency can play a role too. If you submit a share a second too late or the pool decides to orphan your share for another submitted at the same time, that could cause you to also be showing now shares yet. If you look at the stats page at p2pool.io and find your address, you want your DOA% to be at or below the global pools DOA%, because that'll decrease your chances of submitting a dead share. I hope this helped explain this.