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

[newbuntu]

Does anyone know of any good bitcoin p2pool scanners besides these two:
http://p2pool-nodes.info
http://p2pool.hostv.pl

Thanks!

http://p2pools.org/btc

[1715072147]

1715072147

[1715072147]

1715072147

[1715072147]

1715072147

[IYFTech]

Well bugger me.  Just found my first ever block - only took me 18 months.........

That deserves a spliff.   Nice 

[windpath]

Well bugger me.  Just found my first ever block - only took me 18 months.........

That deserves a spliff.   Nice 

Cheers 

[-ck]

Is there anyone mining here with an SP30 that wants to report how well they perform on p2pool please? Thanks.

I got the answer I needed on the spondoolies thread, thanks. It works fine.

[bryonp]

Well bugger me.  Just found my first ever block - only took me 18 months.........

That deserves a spliff.   Nice 

Cool Dude!!!!!
I guess I will never get one, just hung up my operation.... 4T and the income verses electric is not good.....

Hope you find more!!!!

[ravin]

Well bugger me.  Just found my first ever block - only took me 18 months.........

That deserves a spliff.   Nice 

Sarcasm alert! :-)

[windpath]

Shellshock, Aftershock & P2Pool

If you have not heard, a new vulnerability called Shellshock — also called the "Bash Bug" — is affecting both Linux computers and Macs, and it has the potential to let attackers take control of your computer or server.

Many P2Pool nodes run on Linux and Mac, to test your node open up a shell and run:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"

If you see:

vulnerable
this is a test

You are vulnerable and should update bash immediately.

Linux users should run:

Code:

sudo apt-get update
sudo apt-get install bash

Apple has promised a security fix for Mac users soon.

[norgan]

Shellshock, Aftershock & P2Pool

If you have not heard, a new vulnerability called Shellshock — also called the "Bash Bug" — is affecting both Linux computers and Macs, and it has the potential to let attackers take control of your computer or server.

Many P2Pool nodes run on Linux and Mac, to test your node open up a shell and run:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"

If you see:

vulnerable
this is a test

You are vulnerable and should update bash immediately.

Linux users should run:

Code:

sudo apt-get update
sudo apt-get install bash

One advantage of running windows servers 😉

Apple has promised a security fix for Mac users soon.

[jonnybravo0311]

Shellshock, Aftershock & P2Pool

If you have not heard, a new vulnerability called Shellshock — also called the "Bash Bug" — is affecting both Linux computers and Macs, and it has the potential to let attackers take control of your computer or server.

Many P2Pool nodes run on Linux and Mac, to test your node open up a shell and run:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"

If you see:

vulnerable
this is a test

You are vulnerable and should update bash immediately.

Linux users should run:

Code:

sudo apt-get update
sudo apt-get install bash

Apple has promised a security fix for Mac users soon.

Thanks for the heads up windpath!  Once you've installed the patched shell this is what you'll see:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test

That's on Ubuntu 14.04LTS fully updated as of the time of writing this post.  OSX 10.9.5 Mavericks is still vulnerable:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
vulnerable
this is a test

[newbuntu]

How high can the efficiency go?
On my node I'm running around 107% right now with 20 peers (9 incoming) (plus my miners), but last night it hit 117.6% when I had 14 peers ( 6 incoming).
How is the efficiency deterermined / calculated? what are the criteria / factors?
Thanks.

[jonnybravo0311]

How high can the efficiency go?
On my node I'm running around 107% right now with 20 peers (9 incoming) (plus my miners), but last night it hit 117.6% when I had 14 peers ( 6 incoming).
How is the efficiency deterermined / calculated? what are the criteria / factors?
Thanks.

Efficiency is a measure of how your node is doing compared to the rest of the network.  It compares your orphans/deads to the network.  The lower your ratio of orphans/deads to the network's, the higher your efficiency.

If you want to see the code...

web.py:

Code:

global_stale_prop = p2pool_data.get_average_stale_prop(node.tracker, node.best_share_var.value, look behind)
...
efficiency=(1 - (stale_orphan_shares+stale_doa_shares)/shares)/(1 - global_stale_prop) if shares else None

data.py:

Code:

def get_average_stale_prop(tracker, share_hash, lookbehind):
    stales = sum(1 for share in tracker.get_chain(share_hash, lookbehind) if share.share_data['stale_info'] is not None)
    return stales/(lookbehind + stales)

[newbuntu]

How high can the efficiency go?
On my node I'm running around 107% right now with 20 peers (9 incoming) (plus my miners), but last night it hit 117.6% when I had 14 peers ( 6 incoming).
How is the efficiency deterermined / calculated? what are the criteria / factors?
Thanks.

Efficiency is a measure of how your node is doing compared to the rest of the network.  It compares your orphans/deads to the network.  The lower your ratio of orphans/deads to the network's, the higher your efficiency.

If you want to see the code...

web.py:

Code:

global_stale_prop = p2pool_data.get_average_stale_prop(node.tracker, node.best_share_var.value, look behind)
...
efficiency=(1 - (stale_orphan_shares+stale_doa_shares)/shares)/(1 - global_stale_prop) if shares else None

data.py:

Code:

def get_average_stale_prop(tracker, share_hash, lookbehind):
    stales = sum(1 for share in tracker.get_chain(share_hash, lookbehind) if share.share_data['stale_info'] is not None)
    return stales/(lookbehind + stales)

Thank you jonnybravo0311, that's exactly what I'm looking for.

[simdude]

I am having issues with my bitcoind not responding after a few hours running. I am trying to keep my p2pool node active. Just cant figure out what bitcoind is crashing.

[phillipsjk]

I am having issues with my bitcoind not responding after a few hours running. I am trying to keep my p2pool node active. Just cant figure out what bitcoind is crashing.

Do you have at least 2GB of RAM?

[Hunterbunter]

Shellshock, Aftershock & P2Pool

If you have not heard, a new vulnerability called Shellshock — also called the "Bash Bug" — is affecting both Linux computers and Macs, and it has the potential to let attackers take control of your computer or server.

Many P2Pool nodes run on Linux and Mac, to test your node open up a shell and run:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"

If you see:

vulnerable
this is a test

You are vulnerable and should update bash immediately.

Linux users should run:

Code:

sudo apt-get update
sudo apt-get install bash

Apple has promised a security fix for Mac users soon.

Thanks for the heads up windpath!  Once you've installed the patched shell this is what you'll see:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test

That's on Ubuntu 14.04LTS fully updated as of the time of writing this post.  OSX 10.9.5 Mavericks is still vulnerable:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
vulnerable
this is a test

I have 3 servers, 2 only says "This is a test" with no warnings...is that also normal?

The 3rd one says "vulnerable" and "this is a test". I've done an apt-get update/upgrade, and it claims its the newest version. Any idea why that wouldn't have worked on there? That one is Debian 6.0.10

[norgan]

I just hit my biggest share to date I think: 169,159,254 

[windpath]

Shellshock, Aftershock & P2Pool

If you have not heard, a new vulnerability called Shellshock — also called the "Bash Bug" — is affecting both Linux computers and Macs, and it has the potential to let attackers take control of your computer or server.

Many P2Pool nodes run on Linux and Mac, to test your node open up a shell and run:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"

If you see:

vulnerable
this is a test

You are vulnerable and should update bash immediately.

Linux users should run:

Code:

sudo apt-get update
sudo apt-get install bash

Apple has promised a security fix for Mac users soon.

Thanks for the heads up windpath!  Once you've installed the patched shell this is what you'll see:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test

That's on Ubuntu 14.04LTS fully updated as of the time of writing this post.  OSX 10.9.5 Mavericks is still vulnerable:

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
vulnerable
this is a test

I have 3 servers, 2 only says "This is a test" with no warnings...is that also normal?

The 3rd one says "vulnerable" and "this is a test". I've done an apt-get update/upgrade, and it claims its the newest version. Any idea why that wouldn't have worked on there? That one is Debian 6.0.10

Hunter, I'm not 100% on this, but you may have fixed Shellshock, but still be vulnerable to Aftershock...

(note the aftershock fix was integrated before I first posted this)

The bash fix for CVE-2014-6271 (Shellshock) was incomplete and command injection is possible even after the patch has been applied. The issue is being tracked as CVE-2014-7169 (Aftershock).

Ongoing discussion here: https://news.ycombinator.com/item?id=8361574

If fixed after running

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"

you should see

Code:

bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test

if still vulnerable you should see

Code:

vulnerable
this is a test

Aftershock has its own test:

Code:

env var='() {(a)=>\' bash -c "echo date"; cat echo; rm -f echo

If fixed you will see:

Code:

bash: var: line 1: syntax error near unexpected token `='
bash: var: line 1: `'
bash: error importing function definition for `var'
date
cat: echo: No such file or directory

If vulnerable you will see:

Code:

bash: var: line 1: syntax error near unexpected token `='
bash: var: line 1: `'
bash: error importing function definition for `var'
Fri Sep 26 09:20:00 UTC 2014

Hope this helps...

[Hunterbunter]

Hunter, I'm not 100% on this, but you may have fixed Shellshock, but still be vulnerable to Aftershock...

(note the aftershock fix was integrated before I first posted this)

The bash fix for CVE-2014-6271 (Shellshock) was incomplete and command injection is possible even after the patch has been applied. The issue is being tracked as CVE-2014-7169 (Aftershock).

Ongoing discussion here: https://news.ycombinator.com/item?id=8361574

If fixed after running

Code:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"

you should see

Code:

bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test

if still vulnerable you should see

Code:

vulnerable
this is a test

Aftershock has its own test:

Code:

env var='() {(a)=>\' bash -c "echo date"; cat echo; rm -f echo

If fixed you will see:

Code:

bash: var: line 1: syntax error near unexpected token `='
bash: var: line 1: `'
bash: error importing function definition for `var'
date
cat: echo: No such file or directory

If vulnerable you will see:

Code:

bash: var: line 1: syntax error near unexpected token `='
bash: var: line 1: `'
bash: error importing function definition for `var'
Fri Sep 26 09:20:00 UTC 2014

Hope this helps...

Thanks for the info. It looks like my first two servers are fixed with aftershock. The third one is still vulnerable. It's a VPS while the other two are full dedicated...I wonder if that has anything to do with it. Might have a bad source or something that hasn't updated yet. bleh!

[jonnybravo0311]

For anyone using some form of OSX, Apple just released the patch to the shell.  Here's the link for Mavericks: http://support.apple.com/kb/DL1769?viewlocale=en_US&locale=en_US

[windpath]

For anyone using some form of OSX, Apple just released the patch to the shell.  Here's the link for Mavericks: http://support.apple.com/kb/DL1769?viewlocale=en_US&locale=en_US

Thanks, confirmed working...