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

[Carlton Banks]

I started getting the issue around 24 hours ago. Glad I can rule out some issue with my rig, anyways (set this afternoon aside to investigate, only just looked up to check in with the forum).

Godspeed, Forrest

[1713968977]

1713968977

[1713968977]

1713968977

[1713968977]

1713968977

[forrestv]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

[smoothrunnings]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Sorry when you say "try the most recent commit" what exactly do you mean by that?

Update the software or something else?

[bitpop]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Sorry when you say "try the most recent commit" what exactly do you mean by that?

Update the software or something else?

Something else on github

[smoothrunnings]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

So should I block port 9333 for now until the issue is fixed?

[clown]

I just remembered the name.  Was p2pmining. 

https://bitcointalk.org/index.php?topic=66202.0

There wasn't any risk to the pool operator, to my knowledge.  The basic principle was the subpool had it's own share chain (or equiv - could manage with a properly designed database) to track the p2pmining users.  Each share was also submitted to the real chain under the p2pmining address.  When a payout occurred, it was divided among the users in the subpool based on their piece of the subchain.  This also allowed merged mining to occur at a sub pool level, instead of basically solo, which is what p2pool is now.

The downside, of course, was it was a mini centralized pool, subject to possible pool operator abuse and hacking.  Hacking is what brought it down..

He's serving diff 1 shares though. No vardiff, how does his server not get spammed to death?

[mdude77]

I just remembered the name.  Was p2pmining. 

https://bitcointalk.org/index.php?topic=66202.0

There wasn't any risk to the pool operator, to my knowledge.  The basic principle was the subpool had it's own share chain (or equiv - could manage with a properly designed database) to track the p2pmining users.  Each share was also submitted to the real chain under the p2pmining address.  When a payout occurred, it was divided among the users in the subpool based on their piece of the subchain.  This also allowed merged mining to occur at a sub pool level, instead of basically solo, which is what p2pool is now.

The downside, of course, was it was a mini centralized pool, subject to possible pool operator abuse and hacking.  Hacking is what brought it down..

He's serving diff 1 shares though. No vardiff, how does his server not get spammed to death?

Back then large miners were < 100 GH/s.

M

[oldbushie]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Thanks, giving it a try now.

[smoothrunnings]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Sorry when you say "try the most recent commit" what exactly do you mean by that?

Update the software or something else?

Something else on github

Can you be any more vague than that?

[bitpop]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Sorry when you say "try the most recent commit" what exactly do you mean by that?

Update the software or something else?

Something else on github

Can you be any more vague than that?

You need to compile it from the latest commit

[smoothrunnings]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Sorry when you say "try the most recent commit" what exactly do you mean by that?

Update the software or something else?

Something else on github

Can you be any more vague than that?

You need to compile it from the latest commit

Where do I find the info on doing this?

[ikolubr]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

[bkminer]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart

[smoothrunnings]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart

Finally someone with a brain who spelled it out, what to do! LOL

Thanks for your help!

[bitpop]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart

Finally someone with a brain who spelled it out, what to do! LOL

Thanks for your help!

Wait so you know how to do that but my mention of running last commit didn't trigger this?

[bkminer]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Latest commit did not seem to help... happened again right after first incoming peer connected.

-Rick

[bitpop]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Latest commit did not seem to help... happened again right after first incoming peer connected.

-Rick

Give it time to block them

[smoothrunnings]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart

Finally someone with a brain who spelled it out, what to do! LOL

Thanks for your help!

Wait so you know how to do that but my mention of running last commit didn't trigger this?

Obviously you haven't been paying attention in the other thread on setting up P2Pool? I have only had my pool setup for uhm, close to 24 hours now. With the questions I was asking its obvious I didn't know much about linux otherwise I would have been done ages ago. Thanks to the guys over at the openSUSE forum who did a great job at translating the ubuntu mumbo jumbo stuff into openSUSE.

It would have been more simpler if you had said.. run git pull on p2pool instead of saying it the other way. LOL

There is no need to complicate your life and the life of others.

Thanks,

[smoothrunnings]

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Latest commit did not seem to help... happened again right after first incoming peer connected.

-Rick

It's working for me so far Rick, knock on wood.

You could always block or turn off port 9333 as a temporary measure and enable it later.

[bkminer]

It's working for me so far Rick, knock on wood.

You could always block or turn off port 9333 as a temporary measure and enable it later.

I should look at the code but I thought it would block the peer that sends bad shares before it went into it's loop that kills everything.  I have a monit script setup to restart it when it starts to act up. Unfortunately Apple AirPorts cut the connection for a minute or so when changing that level of settings.  I could just add an iptables rule..