Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 135. (Read 2591920 times)

Sure. But look at my graph. smooth and steady at 0.9something for many hours then jumpily climbing... That's not what you would expect to see.

Edit: you would expect to see some climb after we found two blocks so quickly but it still doesn't look correct.

Edit2: Check this monthly chart, especially the circled areas. Looking at this one makes me think it doesn't support the fork hypothesis as much as I had thought though.

The pool rate is always jumping about - it's normal. failovers, restarts, miners coming & going etc.

Here's the thing that should be concerning to others: Look at the pool rate. That was hanging out at slightly below 1.0PH for a while and then climbs jumpily back up to over 2.0. Now, because that happened *after* I restarted, more than likely that is just something my p2pool instance is seeing but possibly that represents hashing power that wasn't being applied to the longest chain. Unfortunately, the fact we got a block at the same time may have affected things. But again, I'm not even sure if this fork idea is even credible so I'm getting into very infirm territory now. My instance was getting that 1.0PH from somewhere (I know I wasn't generating it )

Anyway, I will keep monitoring the stats and I should be able to see if others also lose shares if it happens to me again. Also, it looks like I can use the outbound traffic as a trigger to let me know I need to pay attention. Of course, I will likely lose shares then as well but I'll give it a go for another block or 3.

If anyone is interested, I'll be using the address in my signature for the mining.

Edit: Another interesting point is that before two of the "Resets" my share was climbing to way more (0.035 and 0.025) than what it typically has been (0.02) which would potentially indicate a fork type scenario.

It's a tricky one. Try limiting your bitcoind connections with:


..in your conf file, even if it doesn't help, it will ensure that your bandwidth stays free. It might also be that your p2pool sharechain is corrupted somehow - have you tried deleting it & redownloading?

It shouldn't but see the graph posted above.

bitcoind is left as the default (I believe and is on QOS (which I also have to switch off when I am using the dumb Cisco phone). P2pool is unrestricted and is normally fine for bandwidth. Version is 14.0 which is the latest afaik.

That would have been my question as well, but using a version earlier than 14 would result in no shares submitted at all, and hence no expected or actual payouts.  To be honest, I've never seen the behavior Richy_T is reporting here.  Yes, I've seen shares drop off the chain; however, it is in proportion to when they were added.  For example, if I suddenly start mining with 1PH/s, I would see a very rapid increase in the number of shares I have on the chain, and then when I stopped, they would drop off at the same rate.

My calculated expected payouts provided by the node have always been spot on (give or take a few satoshi).  My actual payouts reflect the node's expectations.

I wish I had some better news or a solution I could offer, but unfortunately I'm at a loss, too.

Just on the off chance, are you using the latest version of p2pool?

Saturation should never be a problem with p2pool - it uses minimal bandwidth, almost nothing. How many connections does your bitcoind have? I restrict mine to 14 to keep bandwidth down - I also use QOS for prioritizing traffic on ports 9332,9333,8332 & 8333.

OK, here's some more oddness. Note the difference before and after the restart





Note that the previous drop in payout I had, I had over-restricted my bandwidth with tc.sh (because my upsteam was saturated) so I am wondering if I somehow disconnected from a "false" chain or possibly some kind of DOS (note the high in/out) or... Who knows? It's beyond me.

One thought on the dropping shares. I know that p2pool uses sharechains. Is it possible somehow that there is a fork going on in the background and one of the forks eventually gets orphaned. That could kind-of explain how my expected payout dropped to what the payout was in the block *after* the block had been mined. If I was on the shorter fork...

I am now collecting data about expected payouts for everyone listed in my instance of p2pool and I'll see if this looks like it's affecting anybody else.

as i mentioned earlier, you'll need to be very patient with p2p. takes sometime to build up the payout. best is to run your own p2p next to your miners.

would love to see a boost in p2p

Nope. The block was mined at 08:59:53.

The graph shows 0.014 up until I had to kill the p2pool and bitcoind at 09:05 because it was interfering with my Cisco phone. (I blame the Cisco phone for this FWIW).

Payout was around 0.005 (Won't say the exact amount)

Then the graph shows a gap before I started bitcoind and p2pool again when my call was done.

Then the graph continues to show 0.014 for a few minutes then it drops to 0.005, apparently losing most of the shares I had taken the last 24 hours building up.

Someone suggested that maybe the payout address had changed for my earlier issue of losing shares. Besides the fact that I had been running p2pool without restarting from way before it happened so that couldn't have been the case, I also just changed my payout address (to one that I'm OK with sharing) and the payout dropped to 0 (as you would expect) whereas before when it happened, it didn't.

defo something is NOT right ... my pool estimated payout & http://minefast.coincadence.com/p2pool-stats.php reads out to be very close & i use it to cross reference it.

setup your own pool op or move to another pool.

thx to finder

BITCOIN BLOCK FOUND by 1NJJgrGhU7rTFCgD9ZbfktKoyj4vFHe4yB! @ 112801.99 GH/s

https://blockchain.info/block/0000000000000000040c77c6374e7d99fd286f6dff539fc7892dd4bced444ee7

would like to see more

Your calculation seems fairly accurate.

I get about 18.6 with PPS.

I might give it a shot. thanks man.

I'm not sure what front end your running, but the predicted payout reported by p2pool is exact if a block is found "now". Perhaps you had some shares drop off from when you saw it and when the block was mined?

OK, think I'm done with this pool. My payout on the last block according to the graph should have been 0.012 but was actually around 0.005. Then I had to restart the pool and bitcoind and my shares dropped again. Something screwy, chaps.

Writing the formula another way:
For 2.3PH/s it's 18.99852101BTC expected per day.

D = Difficulty
H = Mhash/s
C = Reward (currenctly 25 BTC, soon to be 12.5)

24 / (D * 2^32 / (H * 10^6) / 60 / 60) * C = BTC/day

Thx.

Hmmm....has anyone else had the latest bitcoind "lock up" on them? First time it's ever happened to me - I had to kill & restart it  

Edit:  And another BLOCK!