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

[rav3n_pl]

Also I still thinks, that txes should be sent on demand, not to all connected nodes. "Peer sent entire transaction..." is seen too many times in log...

on demand -> ask if he knows the TX, if he says no send the TX to him.

I think about:
- received new share -> check txes it contains
- have all tx -> noop
- not have some txes -> ask for them node that send share
- node not send back tx in 2-5 sec -> check local bitcoin again -> ask another node/s if need

[lenny_]

Lenny, simply upgrading to the most recent commit in git will help. I think that 11.1-6-g19bf4ea solves the leak.

Indeed, it holds for 382 MB for whole day and even decreasing over time. Thank you forrestv!

[neosniperkiller]

I just setup my own multi merged p2pool (LINUX VERSION) (BTCwith all the alt coins) on my local network and it's running nicely.
All the chains are fully updated and the p2pool keeps receiving information.
Trying to mine on it works, shares get accepted, but the overview keeps on displaying the following line:

"Shares: 0 (0 orphan, 0 dead) Stale rate:  Efficiency:  Current payout: 0.0000 BTC"

== phoenix

Now I tried to mine on it using phoenix and it can connect to the p2pool.
But somehow when phoenix says "result accepted", nothing is displayed in the p2pool concerning that result.

== bfgminer

Second try was with bfgminer, see stats below, but still nothing changed at the p2pool overview.

 [2013-01-30 20:41:44] Started at [2013-01-30 20:29:46]
 [2013-01-30 20:41:44] Pool: http://192.168.1.4:9332
 [2013-01-30 20:41:44] Runtime: 0 hrs : 11 mins : 55 secs
 [2013-01-30 20:41:44] Average hashrate: 21.4 Megahash/s
 [2013-01-30 20:41:44] Solved blocks: 0
 [2013-01-30 20:41:44] Best share difficulty: 1
 [2013-01-30 20:41:44] Queued work requests: 82
 [2013-01-30 20:41:44] Share submissions: 5
 [2013-01-30 20:41:44] Accepted shares: 5
 [2013-01-30 20:41:44] Rejected shares: 0
 [2013-01-30 20:41:44] Accepted difficulty shares: 5
 [2013-01-30 20:41:44] Rejected difficulty shares: 0
 [2013-01-30 20:41:44] Reject ratio: 0.0%
 [2013-01-30 20:41:44] Hardware errors: 0
 [2013-01-30 20:41:44] Efficiency (accepted shares * difficulty / 2 KB): 0.01
 [2013-01-30 20:41:44] Utility (accepted shares / min): 0.42/min

 [2013-01-30 20:41:44] Discarded work due to new blocks: 197
 [2013-01-30 20:41:44] Stale submissions discarded due to new blocks: 0
 [2013-01-30 20:41:44] Unable to get work from server occasions: 0
 [2013-01-30 20:41:44] Work items generated locally: 431
 [2013-01-30 20:41:44] Submitting work remotely delay occasions: 0
 [2013-01-30 20:41:44] New blocks detected on network: 1


Anybody knows what I'm doing wrong??
Is this normal behavior of p2pool? When does the p2pool actually increases the "shares"?
Also, how does the p2pool add the alt coin deposits? I cannot see any other accounts made than " " on the alt coin daemons.

[mdude77]

At 21.4mh, it's going to take a LONG time to find a share.  If you check the p2pool output, it'll tell you the average time it'll take.  Wildly guessing, maybe 1/2 a day.

M

I just setup my own multi merged p2pool (LINUX VERSION) (BTCwith all the alt coins) on my local network and it's running nicely.
All the chains are fully updated and the p2pool keeps receiving information.
Trying to mine on it works, shares get accepted, but the overview keeps on displaying the following line:

"Shares: 0 (0 orphan, 0 dead) Stale rate:  Efficiency:  Current payout: 0.0000 BTC"

== phoenix

Now I tried to mine on it using phoenix and it can connect to the p2pool.
But somehow when phoenix says "result accepted", nothing is displayed in the p2pool concerning that result.

== bfgminer

Second try was with bfgminer, see stats below, but still nothing changed at the p2pool overview.

 [2013-01-30 20:41:44] Started at [2013-01-30 20:29:46]
 [2013-01-30 20:41:44] Pool: http://192.168.1.4:9332
 [2013-01-30 20:41:44] Runtime: 0 hrs : 11 mins : 55 secs
 [2013-01-30 20:41:44] Average hashrate: 21.4 Megahash/s
 [2013-01-30 20:41:44] Solved blocks: 0
 [2013-01-30 20:41:44] Best share difficulty: 1
 [2013-01-30 20:41:44] Queued work requests: 82
 [2013-01-30 20:41:44] Share submissions: 5
 [2013-01-30 20:41:44] Accepted shares: 5
 [2013-01-30 20:41:44] Rejected shares: 0
 [2013-01-30 20:41:44] Accepted difficulty shares: 5
 [2013-01-30 20:41:44] Rejected difficulty shares: 0
 [2013-01-30 20:41:44] Reject ratio: 0.0%
 [2013-01-30 20:41:44] Hardware errors: 0
 [2013-01-30 20:41:44] Efficiency (accepted shares * difficulty / 2 KB): 0.01
 [2013-01-30 20:41:44] Utility (accepted shares / min): 0.42/min

 [2013-01-30 20:41:44] Discarded work due to new blocks: 197
 [2013-01-30 20:41:44] Stale submissions discarded due to new blocks: 0
 [2013-01-30 20:41:44] Unable to get work from server occasions: 0
 [2013-01-30 20:41:44] Work items generated locally: 431
 [2013-01-30 20:41:44] Submitting work remotely delay occasions: 0
 [2013-01-30 20:41:44] New blocks detected on network: 1


Anybody knows what I'm doing wrong??
Is this normal behavior of p2pool? When does the p2pool actually increases the "shares"?
Also, how does the p2pool add the alt coin deposits? I cannot see any other accounts made than " " on the alt coin daemons.

[twmz]

I just setup my own multi merged p2pool (LINUX VERSION) (BTCwith all the alt coins) on my local network and it's running nicely.
All the chains are fully updated and the p2pool keeps receiving information.
Trying to mine on it works, shares get accepted, but the overview keeps on displaying the following line:

"Shares: 0 (0 orphan, 0 dead) Stale rate:  Efficiency:  Current payout: 0.0000 BTC"

...

Anybody knows what I'm doing wrong??
Is this normal behavior of p2pool? When does the p2pool actually increases the "shares"?

There are two different kinds of shares.  Your miner reports finding pseudo shares that are typically difficulty 1.  P2Pool's console output is reporting real shares that are difficulty in the hundreds.  Most pseudo shares are not real shares.  As someone else mentioned, the p2pool console output also includes a line that estimates how long (on average) it will take to find a real share based on your recent hashrate.  For the record, you are wasting time mining with only 21.4 MH/s or at least wasting electricity and money even if you are doing this just for fun.  It will take you an insane amount of time to find a share and your earnings will not outweigh the costs of your mining.

Also, how does the p2pool add the alt coin deposits? I cannot see any other accounts made than " " on the alt coin daemons.

Alt-coin merged mining is not pooled.  When you find an entire block based on your own mining effort, that payment will appear in your alt coin client just as if you were solo mining that alt-coin.

[neosniperkiller]

At 21.4mh, it's going to take a LONG time to find a share.  If you check the p2pool output, it'll tell you the average time it'll take.  Wildly guessing, maybe 1/2 a day.

M

Thanks for the info, I just saw the mentioning of TIME TO SHARE in the same block of text that keeps on reappearing in the terminal.
Indeed it takes some time +- 10.5 hours... nvidia laptop gpu...

There are two different kinds of shares.  Your miner reports finding pseudo shares that are typically difficulty 1.  P2Pool's console output is reporting real shares that are difficulty in the hundreds.  Most pseudo shares are not real shares.  As someone else mentioned, the p2pool console output also includes a line that estimates how long (on average) it will take to find a real share based on your recent hashrate.  For the record, you are wasting time mining with only 21.4 MH/s or at least wasting electricity and money even if you are doing this just for fun.  It will take you an insane amount of time to find a share and your earnings will not outweigh the costs of your mining.

Alt-coin merged mining is not pooled.  When you find an entire block based on your own mining effort, that payment will appear in your alt coin client just as if you were solo mining that alt-coin.

Thanks for the more detailed information!
I know about the loss of costs, but I did this to test the p2pool to see if it actually runs on my local network.

[forrestv]

P2Pool release 11.2 hash: 6ff320bf4ddfc735ea34ad30e0eab954f9bbaa69

Windows binary: http://u.forre.st/u/rliakpxs/p2pool_win32_11.2.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/11.2
Source tarball: https://github.com/forrestv/p2pool/tarball/11.2

Changes:
* Fixed a major memory leak of peer objects, as far as I know the cause of all P2Pool memory issues recently. Found by Prattler, whose donation address is 18uyCqDvP6VQUeyTuA5s6x1Ft8x8om767J:

<Prattler> [19:39:11] Memory leak solved!
<Prattler> [19:39:12] https://github.com/forrestv/p2pool/pull/81
<Prattler> [19:41:44] donations accepted at 18uyCqDvP6VQUeyTuA5s6x1Ft8x8om767J - I spent many hours tracking it down

* Fixed a minor memory leak of peer objects

[lenny_]

Can somebody give me node addresses, which are stable 24/7 on good internet and fast server? I would like to give it a try with Stratum miner.
http://nodes.p2pmine.com/ doesn't seem to be working.

[Subo1977]

Can somebody give me node addresses, which are stable 24/7 on good internet and fast server? I would like to give it a try with Stratum miner.
http://nodes.p2pmine.com/ doesn't seem to be working.

http://p2pool-cologne.dyndns.org:9332

[lenny_]

Thanks. I tried it, working very well - but ONLY with getwork.
When this bug with Stratum will be finally fixed? I cannot connect my Stratum Mining Proxy to any p2pool.
AFAIR Slush said that's bug in p2pool, not in his proxy.

Ztex BTCMiner reporting when connected to Stratum Mining Proxy:

Code:

ztex_ufm1_15y1-04A3461AD9-4: Using LongPolling URL http://localhost:4617/lp
ztex_ufm1_15y1-04A3461AD9-4: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s
ztex_ufm1_15y1-04A3461AD9-3: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s
ztex_ufm1_15y1-04A3461AD9-2: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s
ztex_ufm1_15y1-04A3461AD9-1: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s

Stratum Mining Proxy reporting when connected to p2pool-cologne.dyndns.org:9332:

Code:

$ python ~/stratum-mining-proxy/mining_proxy.py -gp 4617 -sp 4618 -rt -oh localhost -o p2pool-cologne.dyndns.org -p 9332
2013-02-10 08:09:05,284 INFO proxy jobs.<module> # Using C extension for midstate speedup. Good!
2013-02-10 08:09:05,939 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed
Traceback (most recent call last):
  File "/home/pioruns/stratum-mining-proxy/mining_proxy.py", line 154, in main
    new_host = (yield utils.detect_stratum(args.host, args.port))
  File "/usr/local/lib/python2.6/dist-packages/Twisted-12.2.0-py2.6-linux-x86_64.egg/twisted/internet/defer.py", line 1045, in _inlineCallbacks
    result = g.send(result)
  File "/home/pioruns/stratum-mining-proxy/mining_libs/utils.py", line 69, in detect_stratum
    header = f.response_headers.get('x-stratum', None)[0]
TypeError: 'NoneType' object is unsubscriptable
2013-02-10 08:09:05,943 WARNING proxy mining_proxy.main # Stratum proxy version: 1.3.0
2013-02-10 08:09:05,944 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at p2pool-cologne.dyndns.org:9332
2013-02-10 08:09:06,056 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-02-10 08:09:06,057 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at p2pool-cologne.dyndns.org:9332
2013-02-10 08:09:06,058 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-02-10 08:09:06,141 WARNING proxy mining_proxy.main # -----------------------------------------------------------------------
2013-02-10 08:09:06,142 WARNING proxy mining_proxy.main # LISTENING FOR MINERS ON http://localhost:4617 (getwork) and stratum+tcp://0.0.0.0:4618 (stratum)
2013-02-10 08:09:06,143 WARNING proxy mining_proxy.main # -----------------------------------------------------------------------
2013-02-10 08:09:06,146 INFO proxy client_service.handle_event # Setting new difficulty: 1.25145617624
2013-02-10 08:09:06,213 INFO proxy client_service.handle_event # New job 325955743810929301480796180155202751669 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:09:26,362 INFO proxy client_service.handle_event # Setting new difficulty: 1.18215669878
2013-02-10 08:09:26,799 INFO proxy client_service.handle_event # New job 269997156551243822103854752532703491497 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:09:34,703 INFO proxy client_service.handle_event # Setting new difficulty: 1.09734043353
2013-02-10 08:09:34,968 INFO proxy client_service.handle_event # New job 73858452078503214942533707870333976939 for prevhash d9371e22, clean_jobs=True
^[OH^[OH2013-02-10 08:09:54,593 INFO proxy client_service.handle_event # Setting new difficulty: 1.09616051031
2013-02-10 08:09:54,670 INFO proxy client_service.handle_event # New job 321835293524890064476778311031875755101 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:09:56,307 INFO proxy client_service.handle_event # Setting new difficulty: 1.03434332373
2013-02-10 08:09:56,416 INFO proxy client_service.handle_event # New job 273423769805879948480669006224757885078 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:00,896 INFO proxy client_service.handle_event # Setting new difficulty: 1.06754432673
2013-02-10 08:10:01,047 INFO proxy client_service.handle_event # New job 81720095736822856709879056879847550243 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:05,357 INFO proxy client_service.handle_event # Setting new difficulty: 1.07267594408
2013-02-10 08:10:05,627 INFO proxy client_service.handle_event # New job 236633676678111076937776131695314696685 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:11,155 INFO proxy client_service.handle_event # Setting new difficulty: 1.10580012625
2013-02-10 08:10:11,309 INFO proxy client_service.handle_event # New job 126088639858383928803852013588898765095 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,094 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,171 INFO proxy client_service.handle_event # New job 338531295106564500565665242810625478384 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,218 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,285 INFO proxy client_service.handle_event # New job 98321113877270917104872120611515544998 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,332 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,366 INFO proxy client_service.handle_event # New job 240149389807169797691884903318242084252 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,429 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,479 INFO proxy client_service.handle_event # New job 119193302466034592597267511360171587748 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:17,982 WARNING proxy getwork_listener.render_POST # Worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo' subscribed for LP
2013-02-10 08:10:24,659 INFO proxy client_service.handle_event # Setting new difficulty: 1.00851885059
2013-02-10 08:10:24,728 INFO proxy client_service.handle_event # New job 172222459887028084567777385883242931397 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:24,729 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo'
2013-02-10 08:10:24,730 INFO proxy jobs.extranonce2_padding # Extranonce size mismatch. Please report this error to pool operator!
2013-02-10 08:10:24,768 WARNING proxy getwork_listener.render_POST # Worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo' subscribed for LP
2013-02-10 08:10:33,666 INFO proxy client_service.handle_event # Setting new difficulty: 0.999984741211
2013-02-10 08:10:34,198 INFO proxy client_service.handle_event # New job 83422292320684236540679450563292946587 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:34,199 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo'
2013-02-10 08:10:34,200 INFO proxy jobs.extranonce2_padding # Extranonce size mismatch. Please report this error to pool operator!

Result - cannot mine on stratum protocol at all. I reported this problem here #4319.

[Ed]

P2Pool release 11.2 ....

thank you

can someone explain, why 7 days luck chart trend was broken?
last time it happened when block value is halved

[PatMan]

Thanks. I tried it, working very well - but ONLY with getwork.
When this bug with Stratum will be finally fixed? I cannot connect my Stratum Mining Proxy to any p2pool.
AFAIR Slush said that's bug in p2pool, not in his proxy.

Ztex BTCMiner reporting when connected to Stratum Mining Proxy:

Code:

ztex_ufm1_15y1-04A3461AD9-4: Using LongPolling URL http://localhost:4617/lp
ztex_ufm1_15y1-04A3461AD9-4: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s
ztex_ufm1_15y1-04A3461AD9-3: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s
ztex_ufm1_15y1-04A3461AD9-2: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s
ztex_ufm1_15y1-04A3461AD9-1: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s

Stratum Mining Proxy reporting when connected to p2pool-cologne.dyndns.org:9332:

Code:

$ python ~/stratum-mining-proxy/mining_proxy.py -gp 4617 -sp 4618 -rt -oh localhost -o p2pool-cologne.dyndns.org -p 9332
2013-02-10 08:09:05,284 INFO proxy jobs.<module> # Using C extension for midstate speedup. Good!
2013-02-10 08:09:05,939 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed
Traceback (most recent call last):
  File "/home/pioruns/stratum-mining-proxy/mining_proxy.py", line 154, in main
    new_host = (yield utils.detect_stratum(args.host, args.port))
  File "/usr/local/lib/python2.6/dist-packages/Twisted-12.2.0-py2.6-linux-x86_64.egg/twisted/internet/defer.py", line 1045, in _inlineCallbacks
    result = g.send(result)
  File "/home/pioruns/stratum-mining-proxy/mining_libs/utils.py", line 69, in detect_stratum
    header = f.response_headers.get('x-stratum', None)[0]
TypeError: 'NoneType' object is unsubscriptable
2013-02-10 08:09:05,943 WARNING proxy mining_proxy.main # Stratum proxy version: 1.3.0
2013-02-10 08:09:05,944 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at p2pool-cologne.dyndns.org:9332
2013-02-10 08:09:06,056 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-02-10 08:09:06,057 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at p2pool-cologne.dyndns.org:9332
2013-02-10 08:09:06,058 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-02-10 08:09:06,141 WARNING proxy mining_proxy.main # -----------------------------------------------------------------------
2013-02-10 08:09:06,142 WARNING proxy mining_proxy.main # LISTENING FOR MINERS ON http://localhost:4617 (getwork) and stratum+tcp://0.0.0.0:4618 (stratum)
2013-02-10 08:09:06,143 WARNING proxy mining_proxy.main # -----------------------------------------------------------------------
2013-02-10 08:09:06,146 INFO proxy client_service.handle_event # Setting new difficulty: 1.25145617624
2013-02-10 08:09:06,213 INFO proxy client_service.handle_event # New job 325955743810929301480796180155202751669 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:09:26,362 INFO proxy client_service.handle_event # Setting new difficulty: 1.18215669878
2013-02-10 08:09:26,799 INFO proxy client_service.handle_event # New job 269997156551243822103854752532703491497 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:09:34,703 INFO proxy client_service.handle_event # Setting new difficulty: 1.09734043353
2013-02-10 08:09:34,968 INFO proxy client_service.handle_event # New job 73858452078503214942533707870333976939 for prevhash d9371e22, clean_jobs=True
^[OH^[OH2013-02-10 08:09:54,593 INFO proxy client_service.handle_event # Setting new difficulty: 1.09616051031
2013-02-10 08:09:54,670 INFO proxy client_service.handle_event # New job 321835293524890064476778311031875755101 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:09:56,307 INFO proxy client_service.handle_event # Setting new difficulty: 1.03434332373
2013-02-10 08:09:56,416 INFO proxy client_service.handle_event # New job 273423769805879948480669006224757885078 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:00,896 INFO proxy client_service.handle_event # Setting new difficulty: 1.06754432673
2013-02-10 08:10:01,047 INFO proxy client_service.handle_event # New job 81720095736822856709879056879847550243 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:05,357 INFO proxy client_service.handle_event # Setting new difficulty: 1.07267594408
2013-02-10 08:10:05,627 INFO proxy client_service.handle_event # New job 236633676678111076937776131695314696685 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:11,155 INFO proxy client_service.handle_event # Setting new difficulty: 1.10580012625
2013-02-10 08:10:11,309 INFO proxy client_service.handle_event # New job 126088639858383928803852013588898765095 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,094 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,171 INFO proxy client_service.handle_event # New job 338531295106564500565665242810625478384 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,218 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,285 INFO proxy client_service.handle_event # New job 98321113877270917104872120611515544998 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,332 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,366 INFO proxy client_service.handle_event # New job 240149389807169797691884903318242084252 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,429 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,479 INFO proxy client_service.handle_event # New job 119193302466034592597267511360171587748 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:17,982 WARNING proxy getwork_listener.render_POST # Worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo' subscribed for LP
2013-02-10 08:10:24,659 INFO proxy client_service.handle_event # Setting new difficulty: 1.00851885059
2013-02-10 08:10:24,728 INFO proxy client_service.handle_event # New job 172222459887028084567777385883242931397 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:24,729 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo'
2013-02-10 08:10:24,730 INFO proxy jobs.extranonce2_padding # Extranonce size mismatch. Please report this error to pool operator!
2013-02-10 08:10:24,768 WARNING proxy getwork_listener.render_POST # Worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo' subscribed for LP
2013-02-10 08:10:33,666 INFO proxy client_service.handle_event # Setting new difficulty: 0.999984741211
2013-02-10 08:10:34,198 INFO proxy client_service.handle_event # New job 83422292320684236540679450563292946587 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:34,199 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo'
2013-02-10 08:10:34,200 INFO proxy jobs.extranonce2_padding # Extranonce size mismatch. Please report this error to pool operator!

Result - cannot mine on stratum protocol at all. I reported this problem here #4319.

I also suggested that there was a problem with the stratum code quite some time ago elsewhere on this thread, but was not taken seriously unfortunately, so I left it. I've been watching this pool since leaving, and when I saw that the memleak had been fixed I decided to try it out again in the hope that things had improved, but after over 30 hours of mining thin air I pulled my rigs off again.

On other pools I can mine with stratum @ 1100% + efficiency, but stratum here is @ 350% on a good day, with constant stratum disconnects/restarts. It is no coincidence that since stratum was enabled on p2pool that the "luck" has been abysmal, and is still in a constant and steady decline. I'm sure there are people who will disagree with me, but until this issue is addressed I fear there will be no change.

I hope something is done soon, cos I like the idea & ethos of p2pool & want to mine here again, but it simply is not worth it at the moment.

Peace.

[-ck]

On other pools I can mine with stratum @ 1100% + efficiency, but stratum here is @ 350% on a good day, with constant stratum disconnects/restarts.

Please do not place any value whatsoever on the efficiency figure as it's virtually meaningless with stratum, and expected to be lower with frequent block updates of p2pool - and does NOT correlate with luck, performance, payment, value, btc, or anything.

If you do get disconnects and restarts, though, that is a totally different issue.

[PatMan]

On other pools I can mine with stratum @ 1100% + efficiency, but stratum here is @ 350% on a good day, with constant stratum disconnects/restarts.

Please do not place any value whatsoever on the efficiency figure as it's virtually meaningless with stratum, and expected to be lower with frequent block updates of p2pool - and does NOT correlate with luck, performance, payment, value, btc, or anything.

If you do get disconnects and restarts, though, that is a totally different issue.

Hi ckolivas,

What do you think is causing the constant disconnects & restarts? I've tried every possible setting imaginable with cgminer, many hours, and I only get this problem with p2pool & stratum since 60 days or so. Thanks.

[twmz]

can someone explain, why 7 days luck chart trend was broken?
last time it happened when block value is halved

Because...  it's luck?  You're looking for an explanation of why a random series of events occurred a certain way?

[Smoovious]

can someone explain, why 7 days luck chart trend was broken?
last time it happened when block value is halved

Because...  it's luck?  You're looking for an explanation of why a random series of events occurred a certain way?

Careful... might end up starting a religion down that path...

-- Smoov

[stevegee58]

Because...  it's luck?  You're looking for an explanation of why a random series of events occurred a certain way?

Aaaaaaaaaaaaaaaaaaaaaaaaah! He said the L word!

[-ck]

Hi ckolivas,

What do you think is causing the constant disconnects & restarts? I've tried every possible setting imaginable with cgminer, many hours, and I only get this problem with p2pool & stratum since 60 days or so. Thanks.

I really have no idea. The GF count at the top tells you how many real disconnects you get. On a local machine it should pretty much never drop out, and on a local network it should only exceedingly rarely do so. On a remote pool with my fairly reliable connection (even through wifi!) I only get disconnects when the pool restarts their server or my  ISP has an outage, and that's something like 1 dropout a month.

[Oktoberfest]

I can't even get this working on Windows.

• Installed Python 2.7 (x64)
• Installed Twisted
• Installed Zope.Interface
• Unzipped the files into C:\Python27\Lib\site-packages
• Created bitcoin.conf in: C:\Users\Me\AppData\Roaming\Bitcoin
• Typed:

rpcuser=<username>
rpcpassword=<password>
server=1
NOTE: I used a real u/n and p/w.

• Made a "run_p2pool.exe" shortcut adding the following in the Target line: C:\Users\Me\Downloads\p2pool_win32_11.2\run_p2pool.exe <username> <password>

NOTE: <username> and <password> are the ones I used in the bitcoin.conf file.

• Extracted cgminer to the Downloads folder as well.
• Created a shortcut of cgminer.exe and edited the Target line as such:

C:\Users\Me\Downloads\cgminer-2.10.5-win32\cgminer.exe -o http://127.0.0.1:9332 -u <username> -p <password>
NOTE: I used the the u/n and p/w from the bitcoin.conf file.[/list]

I run run_p2pool.exe shortcut, then I run cgminer.exe shortcut, NO DICE!

What I see:
run_p2pool
https://i.imgur.com/Jlrm05E.png

cgminer:
https://i.imgur.com/NZEjNdH.png

Just wanted to make a d'oh note. I rebooted my computer and it works now.
I suppose it's because Twisted makes a registry edit and you need a reboot for that to take effect.

In other news, the above instructions will get you mining on P2Pool on Windows. (I'm using Win 8 x64)

[rav3n_pl]

I can't even get this working on Windows.

• Installed Python 2.7 (x64)
• Installed Twisted
• Installed Zope.Interface
• Unzipped the files into C:\Python27\Lib\site-packages
• Created bitcoin.conf in: C:\Users\Me\AppData\Roaming\Bitcoin
• Typed:

rpcuser=<username>
rpcpassword=<password>
server=1
NOTE: I used a real u/n and p/w.

• Made a "run_p2pool.exe" shortcut adding the following in the Target line: C:\Users\Me\Downloads\p2pool_win32_11.2\run_p2pool.exe <username> <password>

NOTE: <username> and <password> are the ones I used in the bitcoin.conf file.

No need.p2pool is reading it form config file.

• Extracted cgminer to the Downloads folder as well.
• Created a shortcut of cgminer.exe and edited the Target line as such:

C:\Users\Me\Downloads\cgminer-2.10.5-win32\cgminer.exe -o http://127.0.0.1:9332 -u <username> -p <password>
NOTE: I used the the u/n and p/w from the bitcoin.conf file.[/list]

Wrong. user and pass can be anything, if you want mine to specyfic bitcoin address use it as username.

I run run_p2pool.exe shortcut, then I run cgminer.exe shortcut, NO DICE!

What I see:
....
Just wanted to make a d'oh note. I rebooted my computer and it works now.
I suppose it's because Twisted makes a registry edit and you need a reboot for that to take effect.

You need restart bitcoin after you edited bitcoin.conf file

In other news, the above instructions will get you mining on P2Pool on Windows. (I'm using Win 8 x64)