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

[Icoin]

Hi
Is it possible to add the http://p2pool.info/favicon.ico from p2pool.info to the actual p2pool gitgub fork? Allso i like the way the actual hashrate can be reviewed for any timeperiod there, would be great to have that for a p2pool node aswell..

Thanks in advance

[1714294440]

1714294440

[1714294440]

1714294440

[bitpop]

Pull: https://github.com/forrestv/p2pool/pull/24
Test: http://bitpoppool.geekgalaxy.com:9332/static/

Hi
Is it possible to add the http://p2pool.info/favicon.ico from p2pool.info to the actual p2pool gitgub fork? Allso i like the way the actual hashrate can be reviewed for any timeperiod there, would be great to have that for a p2pool node aswell..

Thanks in advance

[gmaxwell]

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

I hope everyone has upgraded to 0.6.2.  If not, do so right away!

And thanks for Forrest for finding and reporting this issue!

[coretechs]

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

I hope everyone has upgraded to 0.6.2.  If not, do so right away!

And thanks for Forrest for finding and reporting this issue!

+1 thanks Forrest!

[Aseras]

Wonder if he "discovered" it by having p2ppol do something that essentially dos'ed itself and causes some of those long block problems?

[ChanceCoats123]

Updated!

[mdude77]

Wonder if he "discovered" it by having p2ppol do something that essentially dos'ed itself and causes some of those long block problems?

You mean the 33 hour one?  <facepalm>

Horrible luck for 300+ g/h.

[forrestv]

The bug I discovered in Bitcoin has no affect on or relationship to P2Pool. (:

[coretechs]

Uh, what? p2pool is more susceptible to DoS than other pools...

Would you mind explaining how/why?  I usually think of a typical DDoS attack against a public mining pool address, perhaps you are referring to a different DoS method that I'm not considering.

[Luke-Jr]

Uh, what? p2pool is more susceptible to DoS than other pools...

Would you mind explaining how/why?  I usually think of a typical DDoS attack against a public mining pool address, perhaps you are referring to a different DoS method that I'm not considering.

It's trivial to get the IPs of every p2pool miner, and spread the DDoS across them. Many (most?) mining pools can withstand far more bandwidth being thrown at them, than the equivalent in miners' connections, so the DDoS will require less bandwidth to pull off. Furthermore, since such a DDoS takes out the miners' connection, it effectively prevents any failover including solo mining.

To contrast, not only do other pools have higher DDoS resistance in terms of bandwidth, but they generally keep their miners' IPs private, so when/if the pool goes down, the miners are free to failover to another pool.

[kano]

Though ... the IP address of a non-p2pool pool is even less than trivial and doesn't require running p2pool and waiting and hoping to get everyone on p2pool to connect to you.
You get the IP address pretty much immediately when you want to start your DDoS attack and thus leave no pre DDoS trail ...

[forrestv]

It's trivial to get the IPs of every p2pool miner, and spread the DDoS across them. Many (most?) mining pools can withstand far more bandwidth being thrown at them, than the equivalent in miners' connections, so the DDoS will require less bandwidth to pull off. Furthermore, since such a DDoS takes out the miners' connection, it effectively prevents any failover including solo mining.

To contrast, not only do other pools have higher DDoS resistance in terms of bandwidth, but they generally keep their miners' IPs private, so when/if the pool goes down, the miners are free to failover to another pool.

There are hundreds of P2Pool nodes (my node has heard of 292 active in the past day). Does any pool have a network link that can sustain multiple gigabits per second?

[Luke-Jr]

There are hundreds of P2Pool nodes (my node has heard of 292 active in the past day). Does any pool have a network link that can sustain multiple gigabits per second?

Eligius's last DDoS was over 30 gbit/sec. It didn't stop until we overcame it.

[Gomeler]

Is there any way by crawling the p2pool logs to see when a block is found by p2pool and the reward distributed to my wallet? I'm not seeing any notifications in the p2pool logs. Trying to automate a report email so I can start gathering some mining stats with p2pool.

[Aseras]

Go to http://p2pool.info/ and go through each block and look for your payout address, or go to blockchain.info and put your payout address in the search box.

Here's the last block and the payouts.

http://blockchain.info/block-index/000000000000009743ecaf0e954afc3d1ee59cebbeb47e22d32bb4f6db52cc17

[Gomeler]

Go to http://p2pool.info/ and go through each block and look for your payout address, or go to blockchain.info and put your payout address in the search box.

Here's the last block and the payouts.

http://blockchain.info/block-index/000000000000009743ecaf0e954afc3d1ee59cebbeb47e22d32bb4f6db52cc17

I guess I'll have to dig through p2pool to see if there is a way to dump the individual user generated BTC to the logs. I'd hate to have to curl and scrape that page.

The following output gives an URL
GOT BLOCK FROM PEER! Passing to bitcoind! 74b22adc bitcoin: http://blockexplorer.com/block/00000000000000b8fea2523bd5ba56ab32e6cd6e0a1068d6f983e92074b22adc

that could then be scraped with grep, awk and sed

curl http://blockexplorer.com/block/000000000000009743ecaf0e954afc3d1ee59cebbeb47e22d32bb4f6db52cc17 | grep ${btcaddress} | awk '{print $3}' | sed 's|</li>||'

I guess that is a temporary solution. The GOT BLOCK FROM PEER! message should have a way to output this like..

GOT BLOCK FROM PEER! Passing to bitcoind! derpderpderp bitcoin: http://blockexplorer.com/block/00000000000000b8fea2523bd5ba56ab32e6cd6e0a1068d6f983e92074b22adc. Shares: x (y orphan, z dead) Stale rate: xx% Efficiency: yy% Block payout: x.y BTC

[Tittiez]

Mined 3 LTC blocks with P2Pool already in two days with only 21kH/s, good luck for the pool, bad luck for me. 

[JayCoin]

Uh, what? p2pool is more susceptible to DoS than other pools...

Would you mind explaining how/why?  I usually think of a typical DDoS attack against a public mining pool address, perhaps you are referring to a different DoS method that I'm not considering.

It's trivial to get the IPs of every p2pool miner, and spread the DDoS across them. Many (most?) mining pools can withstand far more bandwidth being thrown at them, than the equivalent in miners' connections, so the DDoS will require less bandwidth to pull off. Furthermore, since such a DDoS takes out the miners' connection, it effectively prevents any failover including solo mining.

To contrast, not only do other pools have higher DDoS resistance in terms of bandwidth, but they generally keep their miners' IPs private, so when/if the pool goes down, the miners are free to failover to another pool.

That's why you should use p2pmining.com to mine p2pool 

[Aseras]

Go to http://p2pool.info/ and go through each block and look for your payout address, or go to blockchain.info and put your payout address in the search box.

Here's the last block and the payouts.

http://blockchain.info/block-index/000000000000009743ecaf0e954afc3d1ee59cebbeb47e22d32bb4f6db52cc17

I guess I'll have to dig through p2pool to see if there is a way to dump the individual user generated BTC to the logs. I'd hate to have to curl and scrape that page.

The following output gives an URL
GOT BLOCK FROM PEER! Passing to bitcoind! 74b22adc bitcoin: http://blockexplorer.com/block/00000000000000b8fea2523bd5ba56ab32e6cd6e0a1068d6f983e92074b22adc

that could then be scraped with grep, awk and sed

curl http://blockexplorer.com/block/000000000000009743ecaf0e954afc3d1ee59cebbeb47e22d32bb4f6db52cc17 | grep ${btcaddress} | awk '{print $3}' | sed 's|</li>||'

I guess that is a temporary solution. The GOT BLOCK FROM PEER! message should have a way to output this like..

GOT BLOCK FROM PEER! Passing to bitcoind! derpderpderp bitcoin: http://blockexplorer.com/block/00000000000000b8fea2523bd5ba56ab32e6cd6e0a1068d6f983e92074b22adc. Shares: x (y orphan, z dead) Stale rate: xx% Efficiency: yy% Block payout: x.y BTC

why not just call bitcoind listtransactions  it'll show all the mined blocks individually to your address.

[Gomeler]

Go to http://p2pool.info/ and go through each block and look for your payout address, or go to blockchain.info and put your payout address in the search box.

Here's the last block and the payouts.

http://blockchain.info/block-index/000000000000009743ecaf0e954afc3d1ee59cebbeb47e22d32bb4f6db52cc17

I guess I'll have to dig through p2pool to see if there is a way to dump the individual user generated BTC to the logs. I'd hate to have to curl and scrape that page.

The following output gives an URL
GOT BLOCK FROM PEER! Passing to bitcoind! 74b22adc bitcoin: http://blockexplorer.com/block/00000000000000b8fea2523bd5ba56ab32e6cd6e0a1068d6f983e92074b22adc

that could then be scraped with grep, awk and sed

curl http://blockexplorer.com/block/000000000000009743ecaf0e954afc3d1ee59cebbeb47e22d32bb4f6db52cc17 | grep ${btcaddress} | awk '{print $3}' | sed 's|</li>||'

I guess that is a temporary solution. The GOT BLOCK FROM PEER! message should have a way to output this like..

GOT BLOCK FROM PEER! Passing to bitcoind! derpderpderp bitcoin: http://blockexplorer.com/block/00000000000000b8fea2523bd5ba56ab32e6cd6e0a1068d6f983e92074b22adc. Shares: x (y orphan, z dead) Stale rate: xx% Efficiency: yy% Block payout: x.y BTC

why not just call bitcoind listtransactions  it'll show all the mined blocks individually to your address.

I have an unusual case where I cannot SSH in to my boxes but instead have them dumping logs to me via email. I simply want to monitor the hashing rate and btc production remotely and if a box goes down I stop by the upcoming weekend. I have the rigs setup with conservative clocks and usually visit once every other week to install another machine and such.