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

[twmz]

gnar1ta$, it helps if you know what you're talking about.

Wandering Albatross, line 764 of p2pool/main.py has a reactor.listenTCP where you can provide an interface argument, but doesn't. So, wait on forrestv to code the means of changing that via argument or take the initiative.

Hence the    What is it he is trying to do?

He's trying to get p2pool to bind to a specific network interface (not to a specific port as your suggested solution was talking about).  But p2pool doesn't have an option to bind to a specific interface (yet) and instead it binds to all available interfaces.

[Tittiez]

Code:

2012-02-09 22:35:15.574000  Pool: 215GH/s Stale rate: 11.0% Average time between
 blocks: 0.32 days

215GH/s, Woohoo!

Oh and look at litecoins!

Code:

2012-02-09 22:43:39.875000  Pool: 1006kH/s Stale rate: 12.5% Average time between blocks: 0.07 days

Just Marvelous!

[gnar1ta$]

He's trying to get p2pool to bind to a specific network interface (not to a specific port as your suggested solution was talking about).  But p2pool doesn't have an option to bind to a specific interface (yet) and instead it binds to all available interfaces.

Thanks twmz, that was helpful, as your 1Twmz will show 

[ThiagoCMC]

Code:

2012-02-09 22:35:15.574000  Pool: 215GH/s Stale rate: 11.0% Average time between
 blocks: 0.32 days

215GH/s, Woohoo!

Oh and look at litecoins!

Code:

2012-02-09 22:43:39.875000  Pool: 1006kH/s Stale rate: 12.5% Average time between blocks: 0.07 days

Just Marvelous!

+++100000

[Frizz23]

Can I use p2pool to mine Bitcoins and with the --merged flag also mine Litecoins at the same time?

[spiccioli]

Just a quick note. You can now find a list recent of P2Pool blocks here:

http://blockchain.info/blocks/P2Pool

piuk,

either that list is not correct or I did not receive payment for all of p2pool mined shares

Code:

yes 166064 	17:27:21 	00000000000006bdb99d5aab93a5cc5b36c427eb07657011f7354e92d81b47b1
no  166062 	17:03:42 	0000000000000a173b45d573d6c500f81120a06fb00b2c90c68ed8d8312bc4b3
yes 166044 	14:08:30 	00000000000002ea00fb76322d57f63819cd9ed5b18c70f084e3cf4b5a03e7ea
yes 166031 	12:00:57 	0000000000000a445a69dd4c3a3d036804df25331cb015f3170b775320d205f4
yes 165994 	06:05:40 	000000000000039ccdd2529b5af67320a57a8c5a68116e14f1fe1dddc9f459b6
yes 165984 	03:20:48 	0000000000000b12309dd48cc86f50788d7670d9745c7f25e53ddd61de7e76bb

In particular block 166062 seems not to be a p2pool block

http://blockexplorer.com/block/0000000000000a173b45d573d6c500f81120a06fb00b2c90c68ed8d8312bc4b3

This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool.

spiccioli

[Rubberduckie]

Please could someone write a guide on how to set up p2pool in windows to mine Litecoins!

[scintill]

Is anyone else seeing this for the pool's hash rate for the day?



I also had some errors in the console p2pool was running on -- I didn't copy them, but it looked like it was on the line calculating my efficiency, something about NaN.  I restarted p2pool and I'm getting messages about the watchdog timer for bitcoind, shares don't seem to be processing (I see "Processing X shares..." a lot, where X is sometimes a drastically different number), and connections to p2pool peers are flaking out.  Just a second ago I "got a block from a peer and passed to bitcoind" and then p2pool lost contact with bitcoind.  I'm running p2pool and bitcoind on AWS, so I would assume the connection is pretty good.

Should I pull the latest p2pool from github?  Any ideas what's going on?

Thanks.

EDIT: Well, after thrashing through a bunch of errors for a few minutes, it looks like the output is back to normal (hmm, except for "Own efficiency: 111±86%").  I should add that bitcoind was running and appeared normal, although I restarted it at the same time I restarted p2pool.  The pool's rate graph for today looks like the same.  I'm still curious what happened.

[tripper22]

Is anyone else seeing this for the pool's hash rate for the day?



I also had some errors in the console p2pool was running on -- I didn't copy them, but it looked like it was on the line calculating my efficiency, something about NaN.  I restarted p2pool and I'm getting messages about the watchdog timer for bitcoind, shares don't seem to be processing (I see "Processing X shares..." a lot, where X is sometimes a drastically different number), and connections to p2pool peers are flaking out.  Just a second ago I "got a block from a peer and passed to bitcoind" and then p2pool lost contact with bitcoind.  I'm running p2pool and bitcoind on AWS, so I would assume the connection is pretty good.

Should I pull the latest p2pool from github?  Any ideas what's going on?

Thanks.

EDIT: Well, after thrashing through a bunch of errors for a few minutes, it looks like the output is back to normal (hmm, except for "Own efficiency: 111±86%").  I should add that bitcoind was running and appeared normal, although I restarted it at the same time I restarted p2pool.  The pool's rate graph for today looks like the same.  I'm still curious what happened.

Get the latest version of p2pool to solve your issues.

[Ente]

Just a quick note. You can now find a list recent of P2Pool blocks here:

http://blockchain.info/blocks/P2Pool

Very nice, thank you for that!
Could you add the date to each block too?

Additionally, I would like a graph with "blocks per day" or similar, to have a quick overview of our "luck".
I know http://u.forre.st/p2pool/luck.png already, which is nice, but takes a three day average. I would prefer a more finely grained graph, updating whenever a block is found.

These are all just details, I am very happy with p2pool!

Ente

[scintill]

Get the latest version of p2pool to solve your issues.

OK, I just did, and it seems to be running OK.  For future reference, how often is an update needed?  My copy was only 2 weeks old.  I'm a little frustrated to see that the pool found 10 blocks since my last payout, so I assume I haven't earned anything in that time and have possibly been passing bad data to other nodes.  Did I miss any announcement of backward-incompatible changes?

EDIT: Nevermind, I haven't missed any blocks.

[Frizz23]

This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool.

+1

p2pool claims to be totally transparent. Users having full control (as in opposite to big mining pools).

Yet we don't even know for sure when / what was found.

[Andrew Vorobyov]

I just finished my rig set up. Can somebody look at this output and confirm I'm doing this right...

Code:

2012-02-10 04:29:16.181656 New work for worker! Difficulty: 2.994499 Share difficulty: 462.391754 Total block value: 50.034500 BTC including 110 transactions
2012-02-10 04:29:17.304420 P2Pool: 17493 shares in chain (10253 verified/18398 total) Peers: 10 (0 incoming)
2012-02-10 04:29:17.304594  Local: 1854MH/s in last 10.0 minutes Local dead on arrival: ~1.7% (0-6%) Expected time to share: 17.7 minutes
2012-02-10 04:29:17.304716  Shares: 9 (0 orphan, 0 dead) Stale rate: ~0.0% (0-26%) Efficiency: ~111.4% (82-112%) Current payout: 0.0520 BTC
2012-02-10 04:29:17.304826  Pool: 210GH/s Stale rate: 10.2% Expected time to block: 7.8 hours

[thirdlight]

Yet we don't even know for sure when / what was found.

Your p2pool log shows everything!
Something like

Code:

cat path-to-p2pool/data/bitcoin/log | grep BLOCK

will show you all the blocks found by you (GOT BLOCK FROM MINER) and found by others (GOT BLOCK FROM PEER).
Example:
2012-02-09 17:16:28.953245 GOT BLOCK FROM PEER! Passing to bitcoind! fd031bab bitcoin: 6bdb99d5aab93a5cc5b36c427eb07657011f7354e92d81b47b1
You can search block explorer for the block hash (eg 6bdb99d5aab93a5cc5b36c427eb07657011f7354e92d81b47b1) to find details of the block. This one was 166064, the most recent one found by p2pool.

[kano]

Hmm but the share-chain history is gone after 2 days ...
Yeah I know there are people who never write buggy code ... but the rest of us ... if you find a problem the history is all but gone.

[Ente]

Well, do a daily cronjob then,

Code:

cat path-to-p2pool/data/bitcoin/log | grep BLOCK >> ~/blocklist

and remove the duplicates with

Code:

sort ~/blocklist | uniq > ~/blocklist

True, this could be integrated into p2pool as well.. p2pool is in constant development.
For me, a look at my blockexplorer-address is enough, anyway.

Ente

edit:
Not talking to you personally, kano, I guess you know your linux stuff by now ;-)

[Gabi]

This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool.

+1

p2pool claims to be totally transparent. Users having full control (as in opposite to big mining pools).

Yet we don't even know for sure when / what was found.

Please stop spreading idiocies.

The fact that YOU don't know, doesn't mean that others don't.

P2pool is totally opensource and there are logs of everything happened.

Go back to paying 10% to deepbit now.

[Frizz23]

Me?

spiccioli posted this:"This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool."

Here: https://bitcointalk.org/index.php?topic=18313.msg741069#msg741069

[spiccioli]

Me?

spiccioli posted this:"This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool."

Here: https://bitcointalk.org/index.php?topic=18313.msg741069#msg741069

If you come from a pool (I'm mining since may last year), you're used to a pool page where you find mined blocks, your payout and so on.

Here you need to grep logs and I was grepping them when I found that old blocks get re-logged as new, and as such my payouts were "wrong".

This has been fixed yesterday.

I'm not stating that p2pool is not correct, but that it is just "difficult" to prove it is

And I'm here because I like p2pool and I've never mined on deepbit.

spiccioli.

[DiabloD3]

Me?

spiccioli posted this:"This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool."

Here: https://bitcointalk.org/index.php?topic=18313.msg741069#msg741069

If you come from a pool (I'm mining since may last year), you're used to a pool page where you find mined blocks, your payout and so on.

Here you need to grep logs and I was grepping them when I found that old blocks get re-logged as new, and as such my payouts were "wrong".

This has been fixed yesterday.

I'm not stating that p2pool is not correct, but that it is just "difficult" to prove it is

And I'm here because I like p2pool and I've never mined on deepbit.

spiccioli.

Troll less kthx.