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

[coinnewb]

Thanks for sharing the details, tucenaber!

I also changed mine to 100 but still see the warning message from time to time.  Any idea on how to proceed?

[1714009411]

1714009411

[1714009411]

1714009411

[-ck]

I don't understand. If p2pool can roll the time locally fast enough, there should be no need to tell the mining software to roll the time at all. Alternatively, if you let the mining software roll the time, why should p2pool roll time at all? There's some kind of catch 22 thing going on here, and yet it should be very low overhead to roll the time. Something is missing in this equation. The mining software should report if it supports nrolltime in X-Mining-Extensions: "longpoll midstate rollntime submitold". If it supports rollntime then p2pool should not be rolling the time itself and allow the miner to do it by advertising X-Roll-Ntime (potentially with some expire= but just "Y" should suffice here). If it does not support rollntime, then p2pool should roll the time itself and not advertise X-Roll-Ntime.

[rav3n_pl]

I don't understand. If p2pool can roll the time locally fast enough, there should be no need to tell the mining software to roll the time at all. Alternatively, if you let the mining software roll the time, why should p2pool roll time at all? There's some kind of catch 22 thing going on here, and yet it should be very low overhead to roll the time. Something is missing in this equation. The mining software should report if it supports nrolltime in X-Mining-Extensions: "longpoll midstate rollntime submitold". If it supports rollntime then p2pool should not be rolling the time itself and allow the miner to do it by advertising X-Roll-Ntime (potentially with some expire= but just "Y" should suffice here). If it does not support rollntime, then p2pool should roll the time itself and not advertise X-Roll-Ntime.

Looks like killing rolltime line is best option if using cgminer then

[Schleicher]

Looks like these are the options we have:
1. recalculate the merkle root each time p2pool is going to send work to the miner

• this will increase CPU load
  
• the miner can roll the time
  

2. p2pool rolls the time, don't let the mining client do it

• this will result in more getwork requests
  

[tucenaber]

Looks like these are the options we have:
1. recalculate the merkle root each time p2pool is going to send work to the miner

• this will increase CPU load
  
• the miner can roll the time
  

This is incorrect. We don't have to recalculate merkle-roots at every request. We only have to calculate once for each miner each time we get new work, compared to once for all miners as it is now.

For those that have only one miner connected there will be no difference.

[mdude77]

I don't understand. If p2pool can roll the time locally fast enough, there should be no need to tell the mining software to roll the time at all. Alternatively, if you let the mining software roll the time, why should p2pool roll time at all? There's some kind of catch 22 thing going on here, and yet it should be very low overhead to roll the time. Something is missing in this equation. The mining software should report if it supports nrolltime in X-Mining-Extensions: "longpoll midstate rollntime submitold". If it supports rollntime then p2pool should not be rolling the time itself and allow the miner to do it by advertising X-Roll-Ntime (potentially with some expire= but just "Y" should suffice here). If it does not support rollntime, then p2pool should roll the time itself and not advertise X-Roll-Ntime.

Looks like killing rolltime line is best option if using cgminer then

I did that and it drove cgminer nuts.  It complained non stop about the p2pool not supplying work fast enough and directed all the work to my backup pools.

Anyhow, I fixed mine.  I directed all my workers to ozcoin again.  Experiment is over (a week), things haven't changed, I still do better on 5% PPS on ozcoin than I do on p2pool.

M

[rav3n_pl]

P2pool software is updated, xrolll changed to 120 seconds and some other stuff. It should prevent all this dupe madness (unless you have over 35GH on one miner....).

[-ck]

We're still disagreeing about what the "expire=" means. cgminer can roll up to 7000 seconds into the future, but will only work on rolled work for $expire seconds before discarding it.

[RandomQ]

so I was looking at /pings I think this is ping time to other p2pool servers
IE "108.175.12.32:9333": 271.435022354126,

and /user_stales i think is a percent of stales?
IE "1GREEN1Q1iGnonZ5yBdFbxifYdwhbzNU1m": 0.056818181818181816

Any Ideas?

Using  3.1-29-gfc4ae93

[rav3n_pl]

UR correct.
Looks like I`m connected to very few European nodes, only 2-3 addresses under 100ms, on both LTC and BTC pool.

[kano]

... and if you look at the cgminer API 'stats' command it will tell you the network performance figures for each pool so you can compare them that way for active pools.
However, the actual non 'Pool' stats in there are really all that matter since as long as cgminer is getting work before it is needed that's all that matters.

[RandomQ]

p2pool official birthday?

June 17, 2011?

 mid-July, 2011?

July 26, 2011?

[mdude77]

P2pool software is updated, xrolll changed to 120 seconds and some other stuff. It should prevent all this dupe madness (unless you have over 35GH on one miner....).

I put one miner back on p2pool.  I double checked my math and p2pool is pretty close to ozcoin.

I also changed my xroll to 120, and I'm still getting a lot of dupes.

when you say "p2pool software is updated", what do you mean?  I still show the official version as 3.1

M

[sharky112065]

P2pool software is updated, xrolll changed to 120 seconds and some other stuff. It should prevent all this dupe madness (unless you have over 35GH on one miner....).

I put one miner back on p2pool.  I double checked my math and p2pool is pretty close to ozcoin.

I also changed my xroll to 120, and I'm still getting a lot of dupes.

when you say "p2pool software is updated", what do you mean?  I still show the official version as 3.1

M

If your version does not show "3.1-33-g246efaa-dirty" you are probably not using the latest version available (git; https://github.com/forrestv/p2pool/commits/master").

[rav3n_pl]

3.1 form 1st post is constantly updated.
If ur on windows try latest source from git and run it from source on python.
Just copy data directory to keep history and payout address.

[mdude77]

3.1 form 1st post is constantly updated.
If ur on windows try latest source from git and run it from source on python.
Just copy data directory to keep history and payout address.

I pulled in the latest version and I'm no longer getting dupe share messages!!  Not sure what else you changed... as I changed my local source timeout to 120 and it didn't fix it.

M

[RandomQ]

I know we have the sendmany command to send donations to all p2pool miners.

Is there a command to sendlocal where any miners on your sub pool would be sent a donation?

I really want to sent BTC generated from alt coins to the Miners that help generate them.

I guess I could grep "GOT SHARE" to have a list of the recent shares and figure how to dividend up the payments but a command would be so nice

[Subo1977]

Hi.

I got 2 payouts from p2pool in the Last 24 h.
In the Staats Page are 0 Blocks found in the Last 24 hours.
This Happens a few in the Last days

Is this a Bug?

[racerguy]

is there a way to make bitcoin p2pool serve out variable diff shares in the same way as litecoin p2pool does?

[rav3n_pl]

Hi.

I got 2 payouts from p2pool in the Last 24 h.
In the Staats Page are 0 Blocks found in the Last 24 hours.
This Happens a few in the Last days

Is this a Bug?

Code:

Blocks found in last day:

Note that blocks may have been orphaned from the P2Pool chain and so not be here.

See http://p2pool.info/ for real block found count