Re: [185 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

Quote from: irrational on April 16, 2014, 01:14:19 AM

Quote from: irrational on April 15, 2014, 04:11:15 AM

In the p2pool log, I'm seeing a ton of these:

Quote

2014-04-14 21:10:16.531268 Worker 12uCQa1rEBxQutWUkXE2AA6LnhfrAPJpgF submitted share with hash > target:
2014-04-14 21:10:16.531393 Hash: 93b4405c1ef4a1104a9a26bf30cbce5034847d7a6d5cb6babc8792326ef6b0ce
2014-04-14 21:10:16.531472 Target: ffffffffffffffffffffffffffffffffffffffffffffffffffffffff

I've tried reading through p2pool's source, but Python isn't my thing and the code doesn't appear well structured IMHO. So, it was hard for me to tell if "target" referred to:

a) A Bitcoin block target - unlikely
b) A p2pool share - my first thought
or
c) A difficulty 1 (or x) share - my fear

Surely somebody knows which it's referring to?

A difficulty 1 share.

That target is 2^(256-32)-1, the maximum possible target for most hardware (H=0).

That message is printed when a miner returns work that doesn't match the target it was sent, meaning that there's a bug or other problem.

EDIT: That returned work has a hash that isn't low at all. What mining hardware are you using?