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

[roy7]

If my understanding is correct, the only time the p2pool node would payout to it's default address is if I'm collecting fees.  If I want to see payouts on the "Payout if a block were found now", I would have to set my miners to pay to the node's payout address as well.

Yes the pool's address (you can specify it with -a) is only for fees or if a miner connects with an invalid payment address.

I wouldn't worry about the "payout if a block were found now" overly much and instead recommend you install the p2pool-node-status interface, or one of the other ones that are nice.

If I go with option 3, does the p2pool node software dole out appropriate difficulty to each miner?  Here, the 2 S1s at 200GH/s each should get higher difficulty than the 5 U2 sticks with a total of 8GH/s, right?  I realize that it really doesn't make much difference in the long run since the difficulty is purely for "lying" to the miner and getting better approximations of hash rate by allowing the miner to solve less difficult shares, right?

By default the vardiff for share difficulty and pseudoshare difficulty per miner will be set based on the total local node speed. If you want to be sure you get plenty of pseudo shares from each of your devices with varying speeds for graphing purposes, you probably need to add the auto-worker-diff patch so you can have the vardiff provide pseudo share difficulties by miner connection or by payment address. There's also a patch I made called vardiffbyaddress which sets actual share difficulty targets per payment address, but that's only useful to a public node with numerous people mining. For your own node, the auto-worker-diff is all you'd need to better control the pseudo share targets to each of your devices.

If all you cared about was total pool hash rate graphs, by default the node will aim for about 1 pseudo share per second. But your S1s will do so many that your USB miners get pushed down to doing far less than that, making their graphs very spotty (if you are graphing each miner separately).

[1714260217]

1714260217

[1714260217]

1714260217

[1714260217]

1714260217

[1714260217]

1714260217

[roy7]

Great point.  That would be option 4 - one I didn't think of  Just start the miners up with usernames like "S1_1", "S1_2", "rPi" and they will default payout to the node's wallet.  I'll restart them that way so I can track each miner's performance, but get the benefits of combined payouts (and like you stated, smaller fees because the payouts would be larger).

Thanks for the tip!

Yeah that's probably the best way to go. This way all pay is on same address (less dust issues) but you can still graph your miners separately. However you do have the issue that the miners will have a single pseudo share target of 1/sec. You can upgrade the vardiff algorithm with the auto-worker-diff patch, or set the pseudo target you want each miner to have manually using +DIFF after their name.

[smooth]

If the hash rate is such, or the difficulty is such, or whatever, where the expected time to block becomes 4 days, 5 days, longer... doesn't that equate to "wasted" work mining because there are days gone by without being counted?

No. Think of mining like flipping 40 coins and trying to get all heads. Getting a share when the pool doesn't get a block is like flipping 40 coins and getting say 38 or 39 heads. Close but no cigar. This is not wasted work, just a near miss. It feels like it because your brain plays tricks on you and you feel that because you almost accomplished the required task, you "should" be rewarded. But no, it doesn't work that way.

[irrational]

In the p2pool log, I'm seeing a ton of these:

2014-04-14 21:10:16.531268 Worker 12uCQa1rEBxQutWUkXE2AA6LnhfrAPJpgF submitted share with hash > target:
2014-04-14 21:10:16.531393     Hash:   93b4405c1ef4a1104a9a26bf30cbce5034847d7a6d5cb6babc8792326ef6b0ce
2014-04-14 21:10:16.531472     Target: ffffffffffffffffffffffffffffffffffffffffffffffffffffffff

I've tried reading through p2pool's source, but Python isn't my thing and the code doesn't appear well structured IMHO. So, it was hard for me to tell if "target" referred to:

a) A Bitcoin block target - unlikely
b) A p2pool share - my first thought
or
c) A difficulty 1 (or x) share - my fear

Surely somebody knows which it's referring to?

[forrestv]

In the p2pool log, I'm seeing a ton of these:

2014-04-14 21:10:16.531268 Worker 12uCQa1rEBxQutWUkXE2AA6LnhfrAPJpgF submitted share with hash > target:
2014-04-14 21:10:16.531393     Hash:   93b4405c1ef4a1104a9a26bf30cbce5034847d7a6d5cb6babc8792326ef6b0ce
2014-04-14 21:10:16.531472     Target: ffffffffffffffffffffffffffffffffffffffffffffffffffffffff

I've tried reading through p2pool's source, but Python isn't my thing and the code doesn't appear well structured IMHO. So, it was hard for me to tell if "target" referred to:

a) A Bitcoin block target - unlikely
b) A p2pool share - my first thought
or
c) A difficulty 1 (or x) share - my fear

Surely somebody knows which it's referring to?

A difficulty 1 share.

That target is 2^(256-32)-1, the maximum possible target for most hardware (H=0).

That message is printed when a miner returns work that doesn't match the target it was sent, meaning that there's a bug or other problem.

EDIT: That returned work has a hash that isn't low at all. What mining hardware are you using?

[irrational]

A difficulty 1 share.

That target is 2^(256-32)-1, the maximum possible target for most hardware (H=0).

That message is printed when a miner returns work that doesn't match the target it was sent, meaning that there's a bug or other problem.

EDIT: That returned work has a hash that isn't low at all. What mining hardware are you using?

Thank you very much for that info. That was my fear.

As for hardware, I'm using Antminer U2s. But, I don't think the hardware is sat fault. If I point my Ants (via Bfgminer) directly at p2pool, it works. I don't get those messages, and the p2pool stats page displays a local hash rate.

This problem arises when I first point my miners to a proxy I'm writing, and then the proxy talks to p2pool. The stratum communication looks identical to me:

Message to p2pool:

{"params":["12uCQa1rEBxQutWUkXE2AA6LnhfrAPJpgF","226858380923200241282647501746235717849","08000000","534ddc22","b9609317"],"id":800,"method":"mining.submit"}

Response from p2pool:

{"id":800,"error":null,"result":true}

And then in p2pool's console output I see these:

2014-04-15 20:26:07.905276 Worker 12uCQa1rEBxQutWUkXE2AA6LnhfrAPJpgF submitted share with hash > target:
2014-04-15 20:26:07.905412     Hash:   ef95748110ef4e9612d216da2cb08d1de41e28b872d7761aaff7db538d1f084b
2014-04-15 20:26:07.905520     Target: ffffffffffffffffffffffffffffffffffffffffffffffffffffffff

I'm still trying to debug what I've done wrong, but I figured stopping in here and double checking my understanding of p2pool's message was a good start.

Still confused as to why I'm getting a "result: true", despite p2pool claiming the hash doesn't meet difficulty 1 though.

[forrestv]

Still confused as to why I'm getting a "result: true", despite p2pool claiming the hash doesn't meet difficulty 1 though.

P2Pool only returns "result: false" for stale work, not invalid work, the idea being that rejected/accepted shares represent some useful quantity and that P2Pool will complain loudly if something is actually wrong.

[novanoob]

anyone found solution for incompatibility mining_proxy with p2pool?

Code:

C:\>mining_proxy -o 127.0.0.1 -p 9332 -gp 8330
2014-04-16 11:30:30,444 INFO proxy jobs.<module> # C extension for midstate not available. Using default implementation instead.
2014-04-16 11:30:30,444 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed
Traceback (most recent call last):
  File "mining_proxy.py", line 182, in main
AttributeError: 'module' object has no attribute '_parse'
2014-04-16 11:30:30,444 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.5
2014-04-16 11:30:30,460 WARNING proxy mining_proxy.test_update # Checking for updates...
2014-04-16 11:30:31,022 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at 127.0.0.1:9332
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
Failure: stratum.custom_exceptions.TransportException: SocketTransportClientFactory connection timed out
2014-04-16 11:31:09,132 INFO proxy mining_proxy.on_shutdown # Shutting down proxy...

[mdude77]

anyone found solution for incompatibility mining_proxy with p2pool?

Code:

C:\>mining_proxy -o 127.0.0.1 -p 9332 -gp 8330
2014-04-16 11:30:30,444 INFO proxy jobs.<module> # C extension for midstate not available. Using default implementation instead.
2014-04-16 11:30:30,444 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed
Traceback (most recent call last):
  File "mining_proxy.py", line 182, in main
AttributeError: 'module' object has no attribute '_parse'
2014-04-16 11:30:30,444 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.5
2014-04-16 11:30:30,460 WARNING proxy mining_proxy.test_update # Checking for updates...
2014-04-16 11:30:31,022 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at 127.0.0.1:9332
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
Failure: stratum.custom_exceptions.TransportException: SocketTransportClientFactory connection timed out
2014-04-16 11:31:09,132 INFO proxy mining_proxy.on_shutdown # Shutting down proxy...

Don't use the mining proxy? iirc p2pool works fine with getwork.

M

[novanoob]

Don't use the mining proxy? iirc p2pool works fine with getwork.

ASICMiner Block Erupter Cube directed to p2pool has only about 60% efficiency
and p2pool not show hashrate fo it insted console msg:

Code:

2014-04-16 12:28:24.499000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:24.795000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:24.795000     Hash:   b06b586f4dac49697137d0d941e4bb5460f6b340cd1b2bc02236bf79cdcf8ad
2014-04-16 12:28:24.795000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:24.811000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:24.811000     Hash:   fbc6c59bd5586e439ea88260933111aefff5a2d5c8916302453781ce60c494ed
2014-04-16 12:28:24.811000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:24.826000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:24.826000     Hash:   4d1503faebd95b9e174da6e32146fbc131767282eb88d4b2c8edf6e6fd17ed47
2014-04-16 12:28:24.826000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.060000 P2Pool: 17688 shares in chain (14732 verified/17692 total) Peers: 6 (0 incoming)
2014-04-16 12:28:25.060000  Local: 0H/s in last 10.0 minutes Local dead on arrival: ??? Expected time to share: ???
2014-04-16 12:28:25.060000  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2014-04-16 12:28:25.060000  Pool: 165TH/s Stale rate: 13.0% Expected time to block: 1.8 days
2014-04-16 12:28:25.232000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.232000     Hash:   63311e01ab25caf7eb4760d5557ec77eaf7cfe037568d7f6abd23359d31f9a03
2014-04-16 12:28:25.232000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.248000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.248000     Hash:   e403b813ac18c496bdb9e7c98141944ddf0454abd39c1a38189823b3e8fcdcfb
2014-04-16 12:28:25.248000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.263000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.263000     Hash:   3987e9f12da6fbf7dd74b871f6e3994317da901e4de3366cd673915f981043a6
2014-04-16 12:28:25.263000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.279000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.279000     Hash:   e004ab6b08d567116c9334d6c1cbafb92c00fccbab6f0407f705efd2765c99a7
2014-04-16 12:28:25.279000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.638000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.638000     Hash:   e89f94af0e8430c4ab61b98a03b4e95d09888a14389b1691ea8c8486b446d783
2014-04-16 12:28:25.638000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.669000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.669000     Hash:   78bb795c7ebdf9d232f8e7227c5a3f1b4db6a2f10e967baf51e6a1ff2412a202
2014-04-16 12:28:25.669000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.684000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.684000     Hash:   49ae678a407d942dfaa7247a88e4b602d6c61ba4a6d26ef82751073de15c67ad
2014-04-16 12:28:25.684000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.716000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.716000     Hash:   ad28087bd567f5c6616ce674d80d0f9fa2d71f472538eefc7a13105cdc85e9e6
2014-04-16 12:28:25.716000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:26.028000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:26.043000     Hash:   9af797c5688dfa2ff9e6739b4b57d457349eb21e02e2b54ae7f160ff766052d6
2014-04-16 12:28:26.043000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:26.059000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:26.059000     Hash:   cfa674770ea156cb8aa45f188d07a623fc2d57a94ccedbb7007086f7544055d9
2014-04-16 12:28:26.059000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:26.106000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:26.106000     Hash:   5647fe3176bbe09fb5adc9bad7a502f92806708cfd3b47475210cd6698051ec8
2014-04-16 12:28:26.106000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:26.308000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:26.308000     Hash:   7147c9870bcb9967e40e588e86e2471035bd78dc89c3998a3b146d2adb24f6e8
2014-04-16 12:28:26.308000     Target: db24b5c57d9bb0000000000000000000000000000000000000000000

[mdude77]

Don't use the mining proxy? iirc p2pool works fine with getwork.

ASICMiner Block Erupter Cube directed to p2pool has only about 60% efficiency
and p2pool not show hashrate fo it insted console msg:

I believe others have said cubes don't work well with p2pool.  But hey, 60% is better than 0% with the proxy.

Seriously, I suggest another pool with a cube.

M

[novanoob]

Don't use the mining proxy? iirc p2pool works fine with getwork.

ASICMiner Block Erupter Cube directed to p2pool has only about 60% efficiency
and p2pool not show hashrate fo it insted console msg:

I believe others have said cubes don't work well with p2pool.  But hey, 60% is better than 0% with the proxy.

Seriously, I suggest another pool with a cube.

cubes work well with proxy - 97-98% efficiency...
will be fine that proxy work with p2pool...

[kano]

I have no care/consideration for what Bitcoin represents?  HUH??

You are a cgminer developer?   Please explain your ethical position to me.  I do not understand why you think I am abusing the Bitcoin network by simply mining on it.     

Well, oddly enough, if you ignore part of what I said, you will indeed not understand what I said ...

[CaptEmulation]

I use bfgminer -http-port 8330 to proxy for an ASICMiner BE Cube and it works very well with p2pool.

[novanoob]

I use bfgminer -http-port 8330 to proxy for an ASICMiner BE Cube and it works very well with p2pool.

this is Long Poll: inactive sheme, could you please check your Efficieny: ?%

[oldbushie]

How do I manually update bitcoind on Ubuntu? apt-get is still out of date.

[Krak]

I use bfgminer -http-port 8330 to proxy for an ASICMiner BE Cube and it works very well with p2pool.

this is Long Poll: inactive sheme, could you please check your Efficieny: ?%

Yeah, that's kinda the idea. BE Cubes wouldn't need a proxy if they supported stratum.

[rav3n_pl]

How do I manually update bitcoind on Ubuntu? apt-get is still out of date.

You need build it from sources. Clone git and make/qmake ;]

[lenny_]

How do I manually update bitcoind on Ubuntu? apt-get is still out of date.

You need build it from sources. Clone git and make/qmake ;]

No, he don't. Linux binary is here:
https://bitcoin.org/bin/0.9.1/bitcoin-0.9.1-linux.tar.gz

[roy7]

No, he don't. Linux binary is here:
https://bitcoin.org/bin/0.9.1/bitcoin-0.9.1-linux.tar.gz

I run the binary myself, works great. Compiling on my little amazon EC2 machines takes forever.