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

[lenny_]

and why are ip's like 54.250.3.112 and 24.214.18.71 having days off continuously requesting shares from my peer ? (u can guess where the latency goes , to the moon and back all day).

Just ban those IPs. Problem solved.

Can you guys explain (on Linux):
how to see what IPs are wasting most bandwidth and request shares where they shouldn't?
how to ban IP on linux temporarily /permanently from connecting to my node?

Thanks.

[1713911344]

1713911344

[1713911344]

1713911344

[1713911344]

1713911344

[1713911344]

1713911344

[rav3n_pl]

and why are ip's like 54.250.3.112 and 24.214.18.71 having days off continuously requesting shares from my peer ? (u can guess where the latency goes , to the moon and back all day).

Just ban those IPs. Problem solved.

Can you guys explain (on Linux):
how to see what IPs are wasting most bandwidth and request shares where they shouldn't?
how to ban IP on linux temporarily /permanently from connecting to my node?

Thanks.

Find where you are sending shares:
grep Sending p2pool/data/XXXcoin/log

then use scrypt drop.sh:
sudo iptables -A INPUT -s $1 -j DROP

It will block ip till next reboot.

[GrapeApe]

I was wondering if it is better to use multiple threads or one? Cgminer uses  two by default (at least for me).

[supwang]

Hi, all:
I'm using p2pool with cgminer. local hashrate is 1Gh/s show in p2pool windows, but p2pool.info only show 600Mh/s for my address!? Is this a network delay?
Thank you.

[zvs]

Hi, all:
I'm using p2pool with cgminer. local hashrate is 1Gh/s show in p2pool windows, but p2pool.info only show 600Mh/s for my address!? Is this a network delay?
Thank you.

it means you either haven't mined for a whole day, you've been unlucky, your efficiency is low

or some combo of those three

[supwang]

it means you either haven't mined for a whole day, you've been unlucky, your efficiency is low

or some combo of those three

I mining for 7*24. Everything is fine before 2 days. I don't know what causes the hash rate reduce, does anyone have the same experience?
Thank you.

[kjj]

it means you either haven't mined for a whole day, you've been unlucky, your efficiency is low

or some combo of those three

I mining for 7*24. Everything is fine before 2 days. I don't know what causes the hash rate reduce, does anyone have the same experience?
Thank you.

p2pool.info isn't measuring your hash rate, it is estimating it from a random process.  Variations in that process lead to variations in the estimated hashrate.  p2pool.info has to rely on actual shares, so the variance there will be much higher than your local estimates, which are estimated from pseudoshares.

[supwang]

p2pool.info isn't measuring your hash rate, it is estimating it from a random process.  Variations in that process lead to variations in the estimated hashrate.  p2pool.info has to rely on actual shares, so the variance there will be much higher than your local estimates, which are estimated from pseudoshares.

Thank you.
Does it mean if the accept rate do not reduce, the profit will not be changed?

[GrapeApe]

Can someone explain to me why the jalapeño or ASIC in general wont work on p2pool.

[gyverlb]

Can someone explain to me why the jalapeño or ASIC in general wont work on p2pool.

What makes you think they won't?
At least Avalon as been reported to work with their latest firmware (I'm not sure about the efficiency or the exact configuration though).

[spiccioli]

What makes you think they won't?
At least Avalon as been reported to work with their latest firmware (I'm not sure about the efficiency or the exact configuration though).

Sorry, I've made several tests with an Avalon (latest firmware), it barely works for a few minutes, then either p2pool (latest git code) or the Avalon break.

I see a couple of users of p2pool with hash rates that appear to be an Avalon, but I don't know how they're able to make it work, if they're using an Avalon.

spiccioli

[gyverlb]

What makes you think they won't?
At least Avalon as been reported to work with their latest firmware (I'm not sure about the efficiency or the exact configuration though).

Sorry, I've made several tests with an Avalon (latest firmware), it barely works for a few minutes, then either p2pool (latest git code) or the Avalon break.

I see a couple of users of p2pool with hash rates that appear to be an Avalon, but I don't know how they're able to make it work, if they're using an Avalon.

spiccioli

I'm in the dark too: there has been progress but no final report. Even if there isn't a 100% efficient configuration, I'd welcome reports on settings and codebases (cgminer and p2pool) used to reach a stable level whatever the efficiency (just for the sake of documenting it in my guide for an easy reference).

[PatMan]

Can someone explain to me why the jalapeño or ASIC in general wont work on p2pool.

If you scroll back through the thread you'll see that aseras also tried his avalon out to no avail, he describes the problems he had quite well....

It's a p2pool/stratum issue & needs to be addressed urgently......like, for the last 6 months or so.......

[Searinox]

My p2pool mining has been having latency issues the past few days despite the wireless and WAN showing excellent latencies. I then went and did something someone said earlier and set blockmaxsize to 5000 in Qt and my latency's dropped to the lowest I've ever had. What are the risks in the long run for doing this?

[forrestv]

What makes you think they won't?
At least Avalon as been reported to work with their latest firmware (I'm not sure about the efficiency or the exact configuration though).

Sorry, I've made several tests with an Avalon (latest firmware), it barely works for a few minutes, then either p2pool (latest git code) or the Avalon break.

I see a couple of users of p2pool with hash rates that appear to be an Avalon, but I don't know how they're able to make it work, if they're using an Avalon.

spiccioli

You have to use the "avalon" branch of P2Pool for Stratum to work.

My p2pool mining has been having latency issues the past few days despite the wireless and WAN showing excellent latencies. I then went and did something someone said earlier and set blockmaxsize to 5000 in Qt and my latency's dropped to the lowest I've ever had. What are the risks in the long run for doing this?

What kind of "latency issues" were you having? High "Bitcoin Getwork Latency" or low efficiency? The former doesn't matter too much.

The risk of doing that is that it isn't sustainable. Eventually, transaction fees will dominate the block reward, and you won't be taking them.

[spiccioli]

What makes you think they won't?
At least Avalon as been reported to work with their latest firmware (I'm not sure about the efficiency or the exact configuration though).

Sorry, I've made several tests with an Avalon (latest firmware), it barely works for a few minutes, then either p2pool (latest git code) or the Avalon break.

I see a couple of users of p2pool with hash rates that appear to be an Avalon, but I don't know how they're able to make it work, if they're using an Avalon.

spiccioli

You have to use the "avalon" branch of P2Pool for Stratum to work.

Hi forrestv,

I did use the avalon branch but it made no difference.

And I have to use --fix-protocol on cgminer (so I'm not using stratum) otherwise the Avalon does not submit shares and hangs up after half a minute/a couple of minutes of "work"

ckolivas believes that there is some issue on the stratum implementation of p2pool and/or there are problems due to the low memory available on the Avalons.

Aseras was able to mine on p2pool but it was not using latest Avalon firmware which I'm using.

spiccioli

[PatMan]

My p2pool mining has been having latency issues the past few days despite the wireless and WAN showing excellent latencies. I then went and did something someone said earlier and set blockmaxsize to 5000 in Qt and my latency's dropped to the lowest I've ever had. What are the risks in the long run for doing this?

I started getting latency issues after updating to 11.4 - I downgraded back to 11.3 and all was fine & dandy again. What version are you using?

[Searinox]

My p2pool mining has been having latency issues the past few days despite the wireless and WAN showing excellent latencies. I then went and did something someone said earlier and set blockmaxsize to 5000 in Qt and my latency's dropped to the lowest I've ever had. What are the risks in the long run for doing this?

I started getting latency issues after updating to 11.4 - I downgraded back to 11.3 and all was fine & dandy again. What version are you using?

I'm using 11.3 and I recommended that people use it just a few days ago in this thread. Nonetheless, I continued to have issues with latency even after that. I'm just concerned of it affecting my payout in other ways.

[PatMan]

What makes you think they won't?
At least Avalon as been reported to work with their latest firmware (I'm not sure about the efficiency or the exact configuration though).

Sorry, I've made several tests with an Avalon (latest firmware), it barely works for a few minutes, then either p2pool (latest git code) or the Avalon break.

I see a couple of users of p2pool with hash rates that appear to be an Avalon, but I don't know how they're able to make it work, if they're using an Avalon.

spiccioli

You have to use the "avalon" branch of P2Pool for Stratum to work.

Hi forrestv,

I did use the avalon branch but it made no difference.

And I have to use --fix-protocol on cgminer (so I'm not using stratum) otherwise the Avalon does not submit shares and hangs up after half a minute/a couple of minutes of "work"

ckolivas believes that there is some issue on the stratum implementation of p2pool and/or there are problems due to the low memory available on the Avalons.

Aseras was able to mine on p2pool but it was not using latest Avalon firmware which I'm using.

spiccioli

I believe ckolivas is correct. He pretty much knows his stuff.

[crunchy]

care to explain why skipping from block punishes anywhere from 1 to 20 times per skipped block ? wheres the logic in that.

It's not punishing you, it's punishing some other person who made a share when there was already a new Bitcoin block. The message being repeated doesn't really mean anything.

and how does this relate to the "current payout : x.xxxx LTC" going up (thats my share of TX fees i'm guessing) and when the punishes start => , all that my share had rissen just dissappears to the minimum possible. and the time to share follows likewise, starts to drop and then goes back up to were it was. just not letting me get ahead never, at 1 share or max 2 a day its not worth it

then it is my share that gets punished in effect no ? yes !

its what i am seeing in the console, things go well, the moment my share starts rising problems start , skipping from block, punishing and all that was gained is gone again. The way it looks is plain crap.
variable difficulty just means the pool is never running optimally, except for those at the handles. adjust settings to get more efficiency and the program WILL change things to make it less optimal.

thats what it looks like when running, not much logic to be found.


greetings