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

[Ente]

Dear DeathAndTaxes if you aren't happy with reality send your whine to god 

Uh, its not DnT whining here? He is setting the statistics facts straight? If anyone, Panda Mouse is whining, i.e. leaving p2pool because of scam or variance, depending on who you ask.

Ente

[1714134640]

1714134640

[1714134640]

1714134640

[Gabi]

Right but it's the internet where you always lose, so by posting, deathandtaxes automatically lost even if he is right.



Dear Panda Mouse if you aren't happy with reality send your whine to god. Meanwhile stop spreading FUD.

[ChanceCoats123]

Right but it's the internet where you always lose, so by posting, deathandtaxes automatically lost even if he is right.



Dear Panda Mouse if you aren't happy with reality send your whine to god. Meanwhile stop spreading FUD.

Hao? Last I checked, if you were right then... well... you're right.

[Smoovious]

Right but it's the internet where you always lose, so by posting, deathandtaxes automatically lost even if he is right.



Dear Panda Mouse if you aren't happy with reality send your whine to god. Meanwhile stop spreading FUD.

Hao? Last I checked, if you were right then... well... you're right.

Ahhhhh, to be young and naive again... .. .

-- Smoov

[Red Emerald]

Right but it's the internet where you always lose, so by posting, deathandtaxes automatically lost even if he is right.

So then you lose... why did you bother posting?

[JL421]

Correct me if I'm wrong, but could the variance between what the pool should have produced, and what was actually produced be a result of lag between the blockchain and the sharechain? Or even lag between local P2Pool clients and bitcoind?

I haven't looked into the history too much, but does P2Pool have an abnormally high amount of orphaned blocks?

[kano]

I'd guess that the expected delay getting from miner to network is the (hash rate) weighted average of that for all pool miners.

Some would of course have sizeable delays from miner to bitcoind and most would probably have few connections to the network.

If that adds up to enough to increase the number of orphans? No idea.

[jiyu_shi]

I've updated v0.10.3,run it and shows errors:
p2pool.util.jsonrpc.error:-12 error:keypool ran out,please call keypoolrefill first
error getting payout address from bitcoind:
traceback (most recent call last):

My bitcoin-qt is v0.6.0.6 and os is win7 x64
What is the matter?

[ChanceCoats123]

I've updated v0.10.3,run it and shows errors:
p2pool.util.jsonrpc.error:-12 error:keypool ran out,please call keypoolrefill first
error getting payout address from bitcoind:
traceback (most recent call last):

My bitcoin-qt is v0.6.0.6 and os is win7 x64
What is the matter?

Did you restart your computer when you updated? You might just have to wait long enough for bitcoin to synchronize the block chain.

[freshzive]

how do you update your p2pool folder using git? I thought you could use the "pull" command but that gives an error...

[Red Emerald]

how do you update your p2pool folder using git? I thought you could use the "pull" command but that gives an error...

What error?

[forrestv]

I've updated v0.10.3,run it and shows errors:
p2pool.util.jsonrpc.error:-12 error:keypool ran out,please call keypoolrefill first
error getting payout address from bitcoind:
traceback (most recent call last):

My bitcoin-qt is v0.6.0.6 and os is win7 x64
What is the matter?

The problem is due to you using an encrypted wallet, which is locked. The easiest solution would be to run p2pool with the -a option, with a payment address.

[DeathAndTaxes]

Possible bug report.

The hashrate found at /local_stats seems to be incorrect when using a custom target.

My guess is that the hashrates are looking at the # of shares and assuming a default target thus under-report actual hashrate when using higher target (i.e. username/target option)

[jiyu_shi]

I've updated v0.10.3,run it and shows errors:
p2pool.util.jsonrpc.error:-12 error:keypool ran out,please call keypoolrefill first
error getting payout address from bitcoind:
traceback (most recent call last):

My bitcoin-qt is v0.6.0.6 and os is win7 x64
What is the matter?

The problem is due to you using an encrypted wallet, which is locked. The easiest solution would be to run p2pool with the -a option, with a payment address.

Excuse me,but how to "run p2pool with the -a option, with a payment address"?

[Isokivi]

Excuse me,but how to "run p2pool with the -a option, with a payment address"?

run_p2pool - a 1QCnJU2qK1ufNouQoEqRhuRkbWU1Qpo2uw http://USER:PASS@127.0.0.1:8336/

[jiyu_shi]

Excuse me,but how to "run p2pool with the -a option, with a payment address"?

run_p2pool - a 1QCnJU2qK1ufNouQoEqRhuRkbWU1Qpo2uw http://USER:PASS@127.0.0.1:8336/

Thanks a lot!
It runs successfully!

[DeathAndTaxes]

Excuse me,but how to "run p2pool with the -a option, with a payment address"?

run_p2pool - a 1QCnJU2qK1ufNouQoEqRhuRkbWU1Qpo2uw http://USER:PASS@127.0.0.1:8336/

No need for user/pass.  If bitcoind is on the same machine as p2pool, p2pool will read pass from config file. 

[jiyu_shi]

My stale is 7.2%,it seems too high,why?
Does p2pool support longpoll?

[DeathAndTaxes]

My stale is 7.2%,it seems too high,why?
Does p2pool support longpool?

p2pool does support longpolls.

orphans in p2pool aren't the same as other pools.  They aren't lost work they are simply a limit of the sharechain only being able to make 1 share become the next share.  

The key thing to remember is that shares are worthless.  They have absolutely no real value.  Shares are just used as a work tracking mechanism that can't be cheated.  

p2pool has a high orphan rate because the network finds one share every 10 seconds (vs 600 sec for Bitcoin).    When two nodes submit a share at roughly the same time only 1 can become the next share in the chain and the other is orphaned.   Blocks are subject to p2pool internal orphans because they don't go into the sharechain, the node finding it broadcasts it directly to Bitcoin network (and relays it to all p2pool nodes).

That isn't to say orphans don't matter at all.  For p2pool oprhan rate what matters is your stale vs network stale.  If they are similar then you will earn at same rate .

An example may help.
Say you generate 10 shares per hour and the network generates 1000.  Both you and the network average have an orphan rate of 10%.

Work completed:  
You 10, network: 1000, 10 / 1000 = you contributed 1% of work

Shares orphaned:
You 1, network 100,  1/100 = your orphans are 1% of all shares orphaned

Work recorded in sharechain:
You 9, network 900,  9/900 = your share of reward is 1%

You provided 1% of the total work and got 1% of the reward.


dead on arrival is more comparable to a conventional pool's "stale rate".  It is work that your p2pool node determined was invalid by the time it was received.  In a similar fashion a conventional pool marks shares as stale if they are invalid by the time received by the pool.  

You should strive to keep that number as low as possible to increase your profits and to make p2pool more efficient.

To lower your DOA in cgminer you may want to try the following settings:
threads per GPU: 1
queue: 1
intensity: 1 lower than w/ conventional pools (i.e. for 5970 I use I:9 on normal pools and I:8 on p2pool)

TL/DR version:
1) p2pool stales aren't comparable to other pools because they include internal share orphans.
2) As long as your stale rate is comparable to the p2pool avg you will earn the same amount
3) DOA are more comparable to stale rate in other pools.
4) To lower DOA rate use "faster" cgminer settings (less threads, smaller queue, lower intensity)

[Gabi]

+1 to what he said, p2pool stales are not like other pools stales.