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

This error shows when P2pool cannot connect to bitcoind, i.e. you don't have bitcoin running, or your firewall / virus program refused to allow p2pool to talk to bitcoind...  or you forgot to set JSON name/pass, re-view p2pool setup instructions.

from looking at my logs on nogleg,

the p2pool block was received 4 seconds after the btc guild block (14:25:22)

it got orphaned

(ed: fixed repeating myself)

P2Pool release 11.3 hash: 896c9ed4357bd8b986457b1da42b8a7bc7e7617d

Windows binary: http://u.forre.st/u/drxlzowj/p2pool_win32_11.3.zip
Windows binary signature: http://u.forre.st/u/mghtodti/p2pool_win32_11.3.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/11.3
Source tarball: https://github.com/forrestv/p2pool/tarball/11.3

Changes:
* Fixed bugs with Litecoin Stratum support difficulty handling

Still giving block not found. Does that mean it is not going to pay out?

OK, I don't really know much about the behind-the-scenes for mining. Are we waiting for something to happen with this one?

http://blockexplorer.com/block/000000000000016e5c3b2f821f961f95fc2d08b75d5e681cd2282e85f748cf53

Also, it looks like my previous problems with p2pool synching may have been related to bitcoind eating up all my upstream bandwidth. Apparently it hadn't been an issue with any of my other stuff because I don't usually run bitcoind. I'll be re-enabling QOS and dropping 8333 in the "almost zero bandwidth" bucket.

Though I'm glad it got me to switch to CGMiner. I think it let me coax an extra 100MH/s out of my setup.

I did another git clone and got the latest version and it seems to work much better.  I'm getting about 50/min now

I was having problems where cgminer would be mining away happily except I wasn't earning any LTC any more (like today).  I'll find out in a few hours if this was fixed too.  Was there a LTC hard fork I didn't know about?

Ahhhh, so that's a change beyond 11.2?  I'll update my node when I get home and try that.

Pretty sure 2000 is the max in the source.  I generated some 30000 difficulty share or so by modifying source.  The limit should probably be increased

You have 120 shares/min because p2pool-11.2 is broken for LTC stratum.  Upgrade to p2pool git.

Wishlist:
Can merged mining daemons report their getwork latency to p2pool and we can have nice graphs, like for bitcoind getwork latency?

Ok... change the username being passed to p2pool.

adding "/1000" would change the minimum share difficulty you're trying to find, to diff 1000 shares. This option would be the one to slow down how fast you're finding shares. Since payouts take the target difficulty into account, finding fewer high-diff shares would pay out the same as many low-diff shares.

So, say with LTC right now, you're seeing "Share difficulty: 0.640942", and you add "/2.5" to the end of your username, you should start seeing the 'new work for worker!' lines listing your "Share difficulty: 2.500000"... if the pool diff goes higher than that, then you'll follow the pool diff, so it is whichever is higher.

adding "+0.01" would change the other difficulty. Your new work for worker is showing "Difficulty: 0.000009" for example. This is the level of work your miner is sending back to p2pool for speed calculations. If you add "+0.01" to your username, then p2pool will be asking for 0.01 diff shares back for speed stuff, instead of the dynamic one it sends.

Both of those can be used independently.

Also, there is a cap on the + that p2pool will use. I forget exactly how much, but if you set it too high, p2pool will ask for its own maximum from the miner, based on what the Share diff is at the time you start mining. This isn't much of an issue, you'd still be using a much higher miner diff than before.

Using + is _not_ a mathematical operation like the person a few posts above suggested. "+" is just a flag, same as "/", for p2pool to look for to parse out the number being passed to it, so don't use + or / in your username unless you are intending to use the options.

So...
 "/####" is target share difficulty
"+####" is target miner difficulty

Lemme know how they work out for you now.

-- Smoov

Too much like hard work. I think I'll just rework my widget I wrote for the HHTT pool. It may need to work a little differently since the pages aren't public (and I wouldn't recommend anyone port forwarding 9332. Though I don't know that would necessarily cause any problems directly).

Just look on your node /static/graphs.html?Day page

OK, liking p2pool so far. I miss being able to track my hashrate easily though. Who wants an Android app?

I've tried modifying the difficulty using this "username/xxxx+yyyy" syntax but it doesn't seem to have any effect.

All I wanted to do was reduce my share solution rate by about 1/40 of what it is right now.  I'm looking at the "u: xxx/m" field in cgminer to determine this.  It's currently showing about 120/m.

username+5 would adds to 'base difficulty' or w/e, so instead of it being 1, 2, (or rarely 3), it'll be 6, 7, 8.  that's what it uses to calculate your hashrate on the graphs  (so essentially, yes, in response to your question)

username/xxxx (assuming it's higher than the p2pool assigned difficulty) is what difficulty shares you're trying to produce

Hold on, can you please explain?
username/2000 - that's "big shares" difficulty, which p2pool counts as our income, correct?
username+2000 - what's exactly that, then? Difficulty given to stratum-cgminer?

It's the same. You add /x000 to your username to increase share value. And add +x to increase difficulty value.

so you could use aseras/2000

Or

Aseras+4

Or aseras/2000+8

Many combinations. You try to make it so that you find a few shares per hour.

I'm running a small GPU on p2pool (V 11.2) for mining LTC at around 145 kh/s with cgminer (V 2.11.4).  Everything seems to be working but I noticed that instead of the usual 3 shares/minute on BTC mining, I'm getting about 120 shares/minute with LTC.  Basically the shares are flying past.

Is there a way to increase the share difficulty my miner sees to slow this down?

remember there was a hardfork, dunno what happend but with my old version i couldnt get the full blockchain and therefore of course not get any valid shares