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

[IYFTech]

So nice it has been implemented already. But I will agree with comments made earlier on, it should be applied to miners with 500 GH/s (1.7% of total p2pool hashrate). Please reduce it to at least 2% from 5%. It's a simple fix, and it will help a lot to small miners.

From experience, having "only" 2% of the p2pool hashrate doesn't mean there's too much variance (the rewards oscillate +/-~10% around).

With 5%, ~20 large miners can take most of the pie, leaving crumbs to others. With 2%, this is raised to 50 large miners.

I'd be OK with a 1% limit, but 2% should limit complains of high variance from large miners (the reward may even move as much from the hashrate fluctuations of the whole pool as from the share frequency variance, people with 5% or more may be able to confirm this if they have variance around 10% in their rewards too).

BTW: I've not looked into the code, what would happen if there were only 10 miners on p2pool? Is the current algorithm able to converge on sane values or would the current 5% target raise the individual share difficulty without bonds.
From the one-liner extract above it seems there's a missing parameter to achieve this protection (the number of distinct addresses with valid shares in the recent sharechain).

I will decrease the percentage then. Maybe 1.67%? That's a share every half hour.

If there are very few miners, nothing insane happens. Each miner's share difficulty multiplier becomes the maximum, 30, and then the 30-second share period target decreases the minimum difficulty until there's a share every 30 seconds again.

Has this been implemented yet? I'm considering turning my node back on to see if it improves anything.....

[1714118627]

1714118627

[1714118627]

1714118627

[1714118627]

1714118627

[1714118627]

1714118627

[1714118627]

1714118627

[1714118627]

1714118627

[zvs]

Has this been implemented yet? I'm considering turning my node back on to see if it improves anything.....

nothing on git yet... there were two changes, but only affecting litecoins and some other bizarre coin  (terracoins?)

[Mogumodz]

@zvs

Ha....ha....ha

"Nigerian BTC P2Pool - "We mine our Bitcoin directly out of other people's wallets!"

[zvs]

@zvs

Ha....ha....ha

"Nigerian BTC P2Pool - "We mine our Bitcoin directly out of other people's wallets!"

i thought it was fitting 

[oldbushie]

I recently added 60 GH/s, so why would my reward suddenly go DOWN instead of up? Worst case, wouldn't it just stay level? o_O I did notice a bit of an increase in total p2pool hashrate, but I wouldn't expect such a big drop in my own payout based on how much it increased by. I did have a little downtime while I was setting up the new miner but said downtime was minimal. All my other stats read normally though. Efficiency is 101% and latency is < 0.1s. "Local rate" and "Local rate reflected in shares" match up with each other for the past 24 hours, as well as matching what I would expect for the combination of the miners I have.

[Jude Austin]

hetzner network was screwed for about 15m, if anyone reads this that was mining on my pool or some other one located on hetzner network

oh, and luck over the last 3 days has been good if you include 266856 and onwards  

5 blocks in 76 hours, estimated time is 14hr30m but that's with 32.9 thash, and the average over the last 76 hours is probably more like 29-30thash...  jaja

btw: whoever is using p2pool.org:9332 and paying 2% for 75% efficiency... stop!

Oh thanks.

I don't think your advice is working tho.

1.60TH/s (13% DOA) at this time.

When/if you ever get that hash rate you will see your efficiency drop also.

Does everyone on this forum always get jealous and have to attack everyone else?

It's ok man, some day you too will have miners, but attacking other people isn't going to work.

[Mogumodz]

I recently added 60 GH/s, so why would my reward suddenly go DOWN instead of up? Worst case, wouldn't it just stay level? o_O I did notice a bit of an increase in total p2pool hashrate, but I wouldn't expect such a big drop in my own payout based on how much it increased by. I did have a little downtime while I was setting up the new miner but said downtime was minimal. All my other stats read normally though. Efficiency is 101% and latency is < 0.1s. "Local rate" and "Local rate reflected in shares" match up with each other for the past 24 hours, as well as matching what I would expect for the combination of the miners I have.

It will pretty much always go up and down over time.

[Jude Austin]

hetzner network was screwed for about 15m, if anyone reads this that was mining on my pool or some other one located on hetzner network

oh, and luck over the last 3 days has been good if you include 266856 and onwards  

5 blocks in 76 hours, estimated time is 14hr30m but that's with 32.9 thash, and the average over the last 76 hours is probably more like 29-30thash...  jaja

btw: whoever is using p2pool.org:9332 and paying 2% for 75% efficiency... stop!

Oh thanks.

I don't think your advice is working tho.

1.60TH/s (13% DOA) at this time.

When/if you ever get that hash rate you will see your efficiency drop also.

Does everyone on this forum always get jealous and have to attack everyone else?

It's ok man, some day you too will have miners, but attacking other people isn't going to work.

And another thing, how is your expected BTC in 24 hours increasing when you charge no fee?

[wtogami]

Hi folks,

https://bitcointalk.org/index.php?topic=320695.0;all
p2pool users may be interested in Bitcoin OMG, the branch of Bitcoin that contains many of the well-tested features from Bitcoin 0.9 and Litecoin 0.8.  Two of those features, Disable Wallet mode and phantomcircuit's Faster Propagation may be of interest to p2pool miners in further optimizing their mining node by reducing RAM requirements and getting new blocks a split second faster.  Disable Wallet is only usable for headless bitcoind (not bitcoin-qt wallets).  Check out the thread for a list of other features.  Testing of that branch has already helped to improve Bitcoin 0.9.

[zvs]

hetzner network was screwed for about 15m, if anyone reads this that was mining on my pool or some other one located on hetzner network

oh, and luck over the last 3 days has been good if you include 266856 and onwards  

5 blocks in 76 hours, estimated time is 14hr30m but that's with 32.9 thash, and the average over the last 76 hours is probably more like 29-30thash...  jaja

btw: whoever is using p2pool.org:9332 and paying 2% for 75% efficiency... stop!

Oh thanks.

I don't think your advice is working tho.

1.60TH/s (13% DOA) at this time.

When/if you ever get that hash rate you will see your efficiency drop also.

Does everyone on this forum always get jealous and have to attack everyone else?

It's ok man, some day you too will have miners, but attacking other people isn't going to work.

And another thing, how is your expected BTC in 24 hours increasing when you charge no fee?

you truly have no clue.  it's quite sad.

my advice isn't working?  huh?

i have been at 1.5thash before, see http://nogleg.com:9332/static/graphs.html?Week

here:

http://nogleg.com:9332/fee
http://p2pool.org:9332/fee

get a grip.  good job grabbing p2pool.org and preying on the dim, btw.  i see that you're up to 0.03 btc from fees yourself.

by the way, I charge one millions % in fees

that's a lot of monies.

ps: the only p2pool I've ever attacked is yours, and that's because it took you two weeks to upgrade to a p2pool client that supported the NewShare...  wasting all those poor souls hashes that happen to be at your site.  then again, I suppose you *did* have about a 1/1000 chance per day to solve a block.  now it's merely on principle

[zvs]

BTW, feel free to PM me if you ever decide that you want to increase that 75% efficiency

for example, 84.201.254.19:9332, used to have a 15% orphan rate

[maqifrnswa]

I will decrease the percentage then. Maybe 1.67%? That's a share every half hour.

don't know this part of the code well enough, but is the calculation per miner or per node? It's possible a large node may get >1.67% of the shares but be comprised of many small miners. I don't think it's too big of a deal, it would just encourage smaller miners to diversify and not all go on a single node.

[gyverlb]

I will decrease the percentage then. Maybe 1.67%? That's a share every half hour.

don't know this part of the code well enough, but is the calculation per miner or per node? It's possible a large node may get >1.67% of the shares but be comprised of many small miners. I don't think it's too big of a deal, it would just encourage smaller miners to diversify and not all go on a single node.

If it's like the rest of the code I suppose it should be by payment address. So if your miners all share the same payment address they will share the 1.67%.

[matthewh3]

One of our Jupiters is hashing well currently on P2Pool using the latest firmware.  We're going to leave it on there for twenty-four hours and if all is well put both on there.  Which should add ~1.1TH/s to the pool.

[lenny_]

One of our Jupiters is hashing well currently on P2Pool using the latest firmware.  We're going to leave it on there for twenty-four hours and if all is well put both on there.  Which should add ~1.1TH/s to the pool.

Can you share your node address so we can see stats, and paste cgminer output from Jupiter? I am curious how you can say "it's hashing well" when AFAIK KNC firmware is still doing full stop for 2-3sec everytime when LP/work restart arrives, lol.

[zvs]

One of our Jupiters is hashing well currently on P2Pool using the latest firmware.  We're going to leave it on there for twenty-four hours and if all is well put both on there.  Which should add ~1.1TH/s to the pool.

Can you share your node address so we can see stats, and paste cgminer output from Jupiter? I am curious how you can say "it's hashing well" when AFAIK KNC firmware is still doing full stop for 2-3sec everytime when LP/work restart arrives, lol.

If it's 2s, that's less than 7% DOA, so still easy to have >100% efficiency

i'll add here that sometime tomorrow i'm going to increase the pool fee to 2%, as it makes no sense to run a public p2pool that i'm not even using at 0%.  then i suppose since nobody will use it at that point (it doesn't have the name p2pool.org, after all), I'll shut it & bitcoind down and save $80/mo on this buffalo server

[Mogumodz]

I've been grateful for two people testing two KNC Mercury devices on my private p2pool node and the total node DOA varies between 0.8%-1.4% for nearly 2 days now. Pay outs are looking good.

Server is in Amsterdam with one of the Mercury miners in USA and one in UK.

Efficiency is at 106.8% atm as has been at 98% when I put a Saturn on p2pool, forgetting it had FW 0.96 on it so it threw up a dead straight away.

FW 0.98 seems a lot better than 0.96 (never tested with 0.97).

When I tested a Jupiter for an hour on 0.98 which has some bad cores (not very long I know) it threw up two orphans one after another.

I still need to test a Saturn for a while but will need to flash FW 0.98 onto it first.

If things go well and get better, should be about 1TH pointed at p2pool.

[zvs]

shut off early at 8:25am utc!  c u nogleg

[NothinG]

I haven't used p2pool in a long time, are the shares suppose to increase or do I need to just wait longer?

Code:

Local: 13644MH/s in last 3.0 minutes Local dead on arrival: ~0.8% (0-3%) Expected time to share: 13.2 hours
Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
Pool: 39203GH/s Stale rate: 18.4% Expected time to block: 11.9 hours

[rav3n_pl]

It is all in log. Your share ETA is ~13 hrs - it means you should find one share every ~13hrs.
But it can be 4 or 34 hrs too