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

Andrew Vorobyov

hero member

Activity: 558

Merit: 500

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

Frizz23

hero member

Activity: 1162

Merit: 500

Quote from: spiccioli on February 10, 2012, 02:08:34 AM

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.

scintill

sr. member

Activity: 448

Merit: 254

Quote from: tripper22 on February 10, 2012, 03:33:25 AM

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.

Ente

legendary

Activity: 2126

Merit: 1001

Quote from: piuk on February 09, 2012, 07:31:31 PM

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

tripper22

full member

Activity: 188

Merit: 100

Quote from: scintill on February 10, 2012, 03:16:22 AM

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.

scintill

sr. member

Activity: 448

Merit: 254

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.

Rubberduckie

legendary

Activity: 1442

Merit: 1000

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

spiccioli

legendary

Activity: 1379

Merit: 1003

nec sine labore

Quote from: piuk on February 09, 2012, 07:31:31 PM

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

Frizz23

hero member

Activity: 1162

Merit: 500

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

ThiagoCMC

legendary

Activity: 1204

Merit: 1000

฿itcoin: Currency of Resistance!

Quote from: Tittiez on February 09, 2012, 10:36:51 PM

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

gnar1ta$

donator

Activity: 798

Merit: 500

Quote from: twmz on February 09, 2012, 10:11:33 PM

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 Wink

Tittiez

hero member

Activity: 686

Merit: 500

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!

twmz

hero member

Activity: 737

Merit: 500

Quote from: gnar1ta$ on February 09, 2012, 09:33:27 PM

Quote from: TurdHurdur on February 09, 2012, 09:23:36 PM

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.

twmz

hero member

Activity: 737

Merit: 500

Quote from: Proofer on February 09, 2012, 09:59:03 PM

Code:

... New work for worker! Difficulty: 2.785534 Share difficulty: 424.797691 ...

I think I know what "Share difficulty" is. What's "Difficulty"? Is that the miner's criterion for a "mini-share" to pass to p2pool?

That is the difficulty of the so-called pseudo share. P2Pool lies to your miner and tells it to solve an easy share so that your miner finds shares more often than once every 20 minutes (as would happen with the real share difficulty). P2Pool then effectively ignores (except to calculate stats) any submitted shares that are not good enough for the real share difficulty. It was done so that you can tell more quickly if your miners are misbehaving.

Proofer

member

Activity: 266

Merit: 36

Code:

... New work for worker! Difficulty: 2.785534 Share difficulty: 424.797691 ...

I think I know what "Share difficulty" is. What's "Difficulty"? Is that the miner's criterion for a "mini-share" to pass to p2pool?

Wandering Albatross

member

Activity: 70

Merit: 10

Quote from: TurdHurdur

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.

Thanks will look, I'm not very pythonesque.
Pythonista? Pythonovite? Pythonian? Pythoner?

gnar1ta$

donator

Activity: 798

Merit: 500

Quote from: TurdHurdur on February 09, 2012, 09:23:36 PM

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?

TurdHurdur

full member

Activity: 216

Merit: 100

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.

gnar1ta$

donator

Activity: 798

Merit: 500

Quote from: Wandering Albatross on February 09, 2012, 09:02:41 PM

That's not clear to me. It says to connect to an existing p2pool node. I'm running p2pool to listen for my miners not to connect to an existing node.

Code:

worker interface:
  -w PORT, --worker-port PORT
                        listen on PORT for RPC connections from miners
                        (default: bitcoin:9332, litecoin:9327)

No...

Wandering Albatross

member

Activity: 70

Merit: 10

Quote from: gnar1ta$

Code:

p2pool interface:
  --p2pool-port PORT    use port PORT to listen for connections (forward this
                        port from your router!) (default: bitcoin:9333,
                        litecoin:9338)
  -n ADDR[:PORT], --p2pool-node ADDR[:PORT]
                        connect to existing p2pool node at ADDR listening on
                        port PORT (defaults to default p2pool P2P port) in
                        addition to builtin addresses

worker interface:
  -w PORT, --worker-port PORT
                        listen on PORT for RPC connections from miners
                        (default: bitcoin:9332, litecoin:9327)

I am probably missing some detail. I've read the manual, etc.

"connect to existing p2pool node at ADDR listening on"

That's not clear to me. It says to connect to an existing p2pool node. I'm running p2pool to listen for my miners not to connect to an existing node.

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 789. (Read 2591916 times)