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

[lenny_]

lenny.dnsd.me:9332 updated

It's interesting how AM blades wil perform after the switch. According to my calculations, they must still have about 18% DOA  

That's sad. Wonder to know, if I will manage to get 100% efficiency

BTW I have newest p2pool from git master branch. How to fix these errors (BE Blade mining)?

Code:

2013-07-07 19:48:23.922620 P2Pool: 17462 shares in chain (17466 verified/17466 total) Peers: 6 (0 incoming)
2013-07-07 19:48:23.922785  Local: 13672MH/s in last 5.6 minutes Local dead on arrival: ~59.6% (54-65%) Expected time to share: 9.0 minutes
2013-07-07 19:48:23.922883  Shares: 2 (0 orphan, 2 dead) Stale rate: ~100.0% (34-100%) Efficiency: ~0.0% (0-86%) Current payout: 0.0000 BTC
2013-07-07 19:48:23.922992  Pool: 1097GH/s Stale rate: 22.7% Expected time to block: 23.2 hours
2013-07-07 19:48:23.928893 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:23.929048     Hash:   a05aa5b108837b213bff4705f6909066d4c01edd2cfbfdd75c0b919d
2013-07-07 19:48:23.929188     Target: 485f60345db91c000000000000000000000000000000000000000000
2013-07-07 19:48:23.937017 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:23.937258     Hash:   df476abf298776044878cc3f070f8e6b4312ee14b06fb31a8683f066
2013-07-07 19:48:23.937387     Target: 485f60345db91c000000000000000000000000000000000000000000
2013-07-07 19:48:24.259964 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:24.260147     Hash:   d6a0358698bf77396d47fc27a261327a89b533b0e053dfe68699cc05
2013-07-07 19:48:24.260246     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:24.747383 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:24.747589     Hash:   7b459de0e13f928c2595d145a95c669166a54c4a5e7976952774e4d0
2013-07-07 19:48:24.747691     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:24.877765 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:24.877950     Hash:   93192b3f1b9863eed64a7f099bd594893c9cfcdde6d88061b0e5fb2e
2013-07-07 19:48:24.878049     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:25.413071 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:25.413297     Hash:   791be9497d311418544d32d10f3307d241828e9a27c1a7a2ba5eb5b6
2013-07-07 19:48:25.413400     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:25.420694 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:25.420837     Hash:   be1d5918ddd8894c94197245e88d6adb3384f40fa719e59e4428c2b2
2013-07-07 19:48:25.420874     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:26.347089 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:26.347286     Hash:   7fdefddad6b86859392ace66bbc3960c4d58a0f5c7ee93ada08ed93c
2013-07-07 19:48:26.347412     Target: 485f60345db91c000000000000000000000000000000000000000000
2013-07-07 19:48:26.528118 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:26.528331     Hash:   9ea676585fcdb2729a3a7175e2ffc5421fcc269eafe8feedaade83d8
2013-07-07 19:48:26.528452     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:26.534254 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:26.534432     Hash:   803a15090454a4e2880229dffc923d4d59c807d8c3c558f593730f5b
2013-07-07 19:48:26.534530     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000

[1713887506]

1713887506

[1713887506]

1713887506

[1713887506]

1713887506

[1713887506]

1713887506

[1713887506]

1713887506

[1713887506]

1713887506

[baloo_kiev]

1

lenny.dnsd.me:9332 updated

It's interesting how AM blades wil perform after the switch. According to my calculations, they must still have about 18% DOA  

That's sad. Wonder to know, if I will manage to get 100% efficiency

BTW I have newest p2pool from git master branch. How to fix these errors (BE Blade mining)?

Code:

2013-07-07 19:48:23.922620 P2Pool: 17462 shares in chain (17466 verified/17466 total) Peers: 6 (0 incoming)
2013-07-07 19:48:23.922785  Local: 13672MH/s in last 5.6 minutes Local dead on arrival: ~59.6% (54-65%) Expected time to share: 9.0 minutes
2013-07-07 19:48:23.922883  Shares: 2 (0 orphan, 2 dead) Stale rate: ~100.0% (34-100%) Efficiency: ~0.0% (0-86%) Current payout: 0.0000 BTC
2013-07-07 19:48:23.922992  Pool: 1097GH/s Stale rate: 22.7% Expected time to block: 23.2 hours
2013-07-07 19:48:23.928893 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:23.929048     Hash:   a05aa5b108837b213bff4705f6909066d4c01edd2cfbfdd75c0b919d
2013-07-07 19:48:23.929188     Target: 485f60345db91c000000000000000000000000000000000000000000
2013-07-07 19:48:23.937017 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:23.937258     Hash:   df476abf298776044878cc3f070f8e6b4312ee14b06fb31a8683f066
2013-07-07 19:48:23.937387     Target: 485f60345db91c000000000000000000000000000000000000000000
2013-07-07 19:48:24.259964 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:24.260147     Hash:   d6a0358698bf77396d47fc27a261327a89b533b0e053dfe68699cc05
2013-07-07 19:48:24.260246     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:24.747383 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:24.747589     Hash:   7b459de0e13f928c2595d145a95c669166a54c4a5e7976952774e4d0
2013-07-07 19:48:24.747691     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:24.877765 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:24.877950     Hash:   93192b3f1b9863eed64a7f099bd594893c9cfcdde6d88061b0e5fb2e
2013-07-07 19:48:24.878049     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:25.413071 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:25.413297     Hash:   791be9497d311418544d32d10f3307d241828e9a27c1a7a2ba5eb5b6
2013-07-07 19:48:25.413400     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:25.420694 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:25.420837     Hash:   be1d5918ddd8894c94197245e88d6adb3384f40fa719e59e4428c2b2
2013-07-07 19:48:25.420874     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:26.347089 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:26.347286     Hash:   7fdefddad6b86859392ace66bbc3960c4d58a0f5c7ee93ada08ed93c
2013-07-07 19:48:26.347412     Target: 485f60345db91c000000000000000000000000000000000000000000
2013-07-07 19:48:26.528118 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:26.528331     Hash:   9ea676585fcdb2729a3a7175e2ffc5421fcc269eafe8feedaade83d8
2013-07-07 19:48:26.528452     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000
2013-07-07 19:48:26.534254 Worker pioruns10_beblade submitted share with hash > target:
2013-07-07 19:48:26.534432     Hash:   803a15090454a4e2880229dffc923d4d59c807d8c3c558f593730f5b
2013-07-07 19:48:26.534530     Target: 3ccf1029e7d6b8000000000000000000000000000000000000000000

Try to set your pseudoshare difficulty to 1 (username+1)

[fsb4000]

http://fsb4000.no-ip.biz:9332/ updated. Thank you!

[Anonymailer]

http://pool.fabulouspanda.co.uk:9332 updated, already got a BFL Single SC over there so I can't wait for the fork! Thank you!

[svirus]

http://pool.hostv.pl:9332/ Updated
After 12 hours Shares: 9 total (0 orphaned, 1 dead) Efficiency: 110.6%
But my Bitcoind GetBlockTemplate Latency little grow.

[yxxyun]

my node updated, looks fine.

[lenny_]

node: lenny.dnsd.me:9332
I setup BE Blade to use +1 pseudoshare (+1 to username). However, I am still getting these errors, but not so often as before.
Log below:
There's also someone mining on my node right now on BE Blade (12.6GH/s hashrate, 7.6GH/s of it - DOA). Looks like he setup +1 to username as well.

Code:

2013-07-08 03:17:38.412260  Pool: 1065GH/s Stale rate: 18.6% Expected time to block: 23.9 hours
2013-07-08 03:17:40.030014
2013-07-08 03:17:40.045617 New work for worker! Difficulty: 1.000000 Share difficulty: 1801.662333 Total block value: 25.115112 BTC including 145 transactions
2013-07-08 03:17:40.521536
2013-07-08 03:17:40.536623 New work for worker! Difficulty: 1.000000 Share difficulty: 1801.341940 Total block value: 25.115112 BTC including 145 transactions
2013-07-08 03:17:41.034625
2013-07-08 03:17:41.052869 New work for worker! Difficulty: 1.000000 Share difficulty: 1801.341940 Total block value: 25.115112 BTC including 145 transactions
2013-07-08 03:17:41.436942 P2Pool: 17339 shares in chain (17344 verified/17344 total) Peers: 8 (2 incoming)
2013-07-08 03:17:41.437117  Local: 23250MH/s in last 10.0 minutes Local dead on arrival: ~53.6% (51-56%) Expected time to share: 5.7 minutes
2013-07-08 03:17:41.437285  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~23.1% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:17:41.437388  Pool: 1066GH/s Stale rate: 18.7% Expected time to block: 23.9 hours
2013-07-08 03:17:43.143928 Worker pioruns10_beblade submitted share with hash > target:
2013-07-08 03:17:43.144111     Hash:   ab1e35e2c85950554feb622410bad972d7cf01d624fc79ff3bbc22e04e9e0dcf
2013-07-08 03:17:43.144236     Target: ffff0000000000000000000000000000000000000000000000000000
2013-07-08 03:17:43.251147 Worker pioruns10_beblade submitted share with hash > target:
2013-07-08 03:17:43.251345     Hash:   bbf74c834082ced72418d509b5ab171c28c711c34f32d94475665137f1959427
2013-07-08 03:17:43.251483     Target: ffff0000000000000000000000000000000000000000000000000000
2013-07-08 03:17:44.457688 P2Pool: 17339 shares in chain (17344 verified/17344 total) Peers: 8 (2 incoming)
2013-07-08 03:17:44.457788  Local: 23279MH/s in last 10.0 minutes Local dead on arrival: ~53.7% (51-56%) Expected time to share: 5.7 minutes
2013-07-08 03:17:44.457825  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~23.1% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:17:44.457875  Pool: 1066GH/s Stale rate: 18.7% Expected time to block: 23.9 hours
2013-07-08 03:17:44.717372 Worker pioruns10_beblade submitted share with hash > target:
2013-07-08 03:17:44.717589     Hash:   8fc435bbf58845206c5ac5593d4525e9adc3fc637b3232c937a5f45959a5503f
2013-07-08 03:17:44.717731     Target: ffff0000000000000000000000000000000000000000000000000000
2013-07-08 03:17:46.351951
2013-07-08 03:17:46.367896 New work for worker! Difficulty: 1.000000 Share difficulty: 1801.924625 Total block value: 25.115112 BTC including 145 transactions
2013-07-08 03:17:47.479683 P2Pool: 17340 shares in chain (17345 verified/17345 total) Peers: 8 (2 incoming)
2013-07-08 03:17:47.479800  Local: 23350MH/s in last 10.0 minutes Local dead on arrival: ~53.6% (51-56%) Expected time to share: 5.7 minutes
2013-07-08 03:17:47.479843  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~23.1% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:17:47.479887  Pool: 1065GH/s Stale rate: 18.9% Expected time to block: 23.9 hours
2013-07-08 03:17:48.822015
2013-07-08 03:17:48.840233 New work for worker! Difficulty: 1.000000 Share difficulty: 1805.169148 Total block value: 25.115112 BTC including 145 transactions
2013-07-08 03:17:50.498192 P2Pool: 17341 shares in chain (17346 verified/17346 total) Peers: 8 (2 incoming)
2013-07-08 03:17:50.498297  Local: 23500MH/s in last 10.0 minutes Local dead on arrival: ~53.9% (52-56%) Expected time to share: 5.6 minutes
2013-07-08 03:17:50.498328  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~23.1% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:17:50.498361  Pool: 1065GH/s Stale rate: 18.9% Expected time to block: 23.9 hours
2013-07-08 03:17:50.753548
2013-07-08 03:17:50.766176 New work for worker! Difficulty: 1.000000 Share difficulty: 1805.169148 Total block value: 25.115112 BTC including 145 transactions
2013-07-08 03:17:51.558101
2013-07-08 03:17:51.573094 New work for worker! Difficulty: 1.000000 Share difficulty: 1804.925631 Total block value: 25.115112 BTC including 145 transactions
2013-07-08 03:17:51.628923
2013-07-08 03:17:51.641700 New work for worker! Difficulty: 1.000000 Share difficulty: 1804.925631 Total block value: 25.115112 BTC including 145 transactions
2013-07-08 03:17:53.522207 P2Pool: 17342 shares in chain (17347 verified/17347 total) Peers: 8 (2 incoming)
2013-07-08 03:17:53.522317  Local: 23594MH/s in last 10.0 minutes Local dead on arrival: ~54.1% (52-56%) Expected time to share: 5.6 minutes
2013-07-08 03:17:53.522371  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~23.1% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:17:53.522413  Pool: 1063GH/s Stale rate: 18.7% Expected time to block: 23.9 hours
2013-07-08 03:17:53.744346 Worker 1BJAQkRVjafu46ojQjx377xCuPaReoXMyd submitted share with hash > target:
2013-07-08 03:17:53.744450     Hash:   950bef909a97369ced2a86153218ceea8dc5fbd42a88829db81e3b0a280e5cbf
2013-07-08 03:17:53.744496     Target: ffff0000000000000000000000000000000000000000000000000000
2013-07-08 03:17:54.534952 Worker 1BJAQkRVjafu46ojQjx377xCuPaReoXMyd submitted share with hash > target:
2013-07-08 03:17:54.535180     Hash:   12777044b6e599f54ec59f7e048011691ead3ebf11082283c8af501ec5e30ede
2013-07-08 03:17:54.535311     Target: ffff0000000000000000000000000000000000000000000000000000
2013-07-08 03:17:55.028949 Worker 1BJAQkRVjafu46ojQjx377xCuPaReoXMyd submitted share with hash > target:
2013-07-08 03:17:55.029130     Hash:   da5161cf4d3a499c2700b39218e7545451e743304b660cbcd790bd400884ad26
2013-07-08 03:17:55.029277     Target: ffff0000000000000000000000000000000000000000000000000000
2013-07-08 03:17:56.548131 P2Pool: 17342 shares in chain (17347 verified/17347 total) Peers: 8 (2 incoming)
2013-07-08 03:17:56.548238  Local: 23672MH/s in last 10.0 minutes Local dead on arrival: ~54.0% (52-56%) Expected time to share: 5.6 minutes
2013-07-08 03:17:56.548292  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~23.1% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:17:56.548326  Pool: 1063GH/s Stale rate: 18.7% Expected time to block: 23.9 hours
2013-07-08 03:17:58.761723 Worker 1BJAQkRVjafu46ojQjx377xCuPaReoXMyd submitted share with hash > target:
2013-07-08 03:17:58.761902     Hash:   1c32c48c7192dce301b03bb480169d47b1ad0dff2b926922822c4a9459932672
2013-07-08 03:17:58.762004     Target: ffff0000000000000000000000000000000000000000000000000000
2013-07-08 03:17:59.569535 P2Pool: 17342 shares in chain (17347 verified/17347 total) Peers: 8 (2 incoming)
2013-07-08 03:17:59.569638  Local: 23651MH/s in last 10.0 minutes Local dead on arrival: ~54.0% (52-56%) Expected time to share: 5.6 minutes
2013-07-08 03:17:59.569675  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~23.1% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:17:59.569717  Pool: 1063GH/s Stale rate: 18.7% Expected time to block: 23.9 hours

Code:

2013-07-08 03:23:44.258258  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.8% (10-43%) Current payout: 0.0000 BTC
2013-07-08 03:23:44.258295  Pool: 1082GH/s Stale rate: 17.8% Expected time to block: 23.5 hours
2013-07-08 03:23:47.284092 P2Pool: 17380 shares in chain (17385 verified/17385 total) Peers: 8 (2 incoming)
2013-07-08 03:23:47.284197  Local: 24660MH/s in last 10.0 minutes Local dead on arrival: ~60.6% (58-63%) Expected time to share: 5.2 minutes
2013-07-08 03:23:47.284301  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.8% (10-43%) Current payout: 0.0000 BTC
2013-07-08 03:23:47.284397  Pool: 1082GH/s Stale rate: 17.8% Expected time to block: 23.5 hours
2013-07-08 03:23:49.483952 Worker pioruns10_beblade submitted share with hash > target:
2013-07-08 03:23:49.484147     Hash:   75cd87706d8160a381011cfdc2153a1277018eee9b1ed5b59567c6d960840169
2013-07-08 03:23:49.484315     Target: ffff0000000000000000000000000000000000000000000000000000
2013-07-08 03:23:49.547793
2013-07-08 03:23:49.564042 New work for worker! Difficulty: 1.000000 Share difficulty: 1822.309035 Total block value: 25.131132 BTC including 202 transactions
2013-07-08 03:23:50.307803 P2Pool: 17381 shares in chain (17386 verified/17386 total) Peers: 8 (2 incoming)
2013-07-08 03:23:50.307917  Local: 24624MH/s in last 10.0 minutes Local dead on arrival: ~60.8% (59-63%) Expected time to share: 5.2 minutes
2013-07-08 03:23:50.307962  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.8% (10-43%) Current payout: 0.0000 BTC
2013-07-08 03:23:50.308005  Pool: 1082GH/s Stale rate: 17.8% Expected time to block: 23.5 hours
2013-07-08 03:23:50.448943 Worker pioruns10_beblade submitted share with hash > target:
2013-07-08 03:23:50.449175     Hash:   4cda5f12fb5bd08af13ff4b9a670e96ddbf28ee56d5fff6510a130131754d026
2013-07-08 03:23:50.449314     Target: ffff0000000000000000000000000000000000000000000000000000
2013-07-08 03:23:53.336000 P2Pool: 17381 shares in chain (17386 verified/17386 total) Peers: 8 (2 incoming)
2013-07-08 03:23:53.336097  Local: 24646MH/s in last 10.0 minutes Local dead on arrival: ~61.4% (59-64%) Expected time to share: 5.2 minutes
2013-07-08 03:23:53.336129  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.8% (10-43%) Current payout: 0.0000 BTC
2013-07-08 03:23:53.336165  Pool: 1082GH/s Stale rate: 17.8% Expected time to block: 23.5 hours
2013-07-08 03:23:55.029341
2013-07-08 03:23:55.041915 New work for worker! Difficulty: 1.000000 Share difficulty: 1822.309035 Total block value: 25.131132 BTC including 202 transactions
2013-07-08 03:23:56.358754 P2Pool: 17381 shares in chain (17386 verified/17386 total) Peers: 8 (2 incoming)
2013-07-08 03:23:56.358857  Local: 24739MH/s in last 10.0 minutes Local dead on arrival: ~61.9% (60-64%) Expected time to share: 5.2 minutes
2013-07-08 03:23:56.358888  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.8% (10-43%) Current payout: 0.0000 BTC
2013-07-08 03:23:56.358923  Pool: 1082GH/s Stale rate: 17.8% Expected time to block: 23.5 hours
2013-07-08 03:23:59.378478 P2Pool: 17381 shares in chain (17386 verified/17386 total) Peers: 8 (2 incoming)
2013-07-08 03:23:59.378588  Local: 24703MH/s in last 10.0 minutes Local dead on arrival: ~62.2% (60-64%) Expected time to share: 5.2 minutes
2013-07-08 03:23:59.378634  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.8% (10-43%) Current payout: 0.0000 BTC
2013-07-08 03:23:59.378680  Pool: 1082GH/s Stale rate: 17.8% Expected time to block: 23.5 hours
2013-07-08 03:24:02.404006 P2Pool: 17381 shares in chain (17386 verified/17386 total) Peers: 8 (2 incoming)
2013-07-08 03:24:02.404106  Local: 24746MH/s in last 10.0 minutes Local dead on arrival: ~62.3% (60-64%) Expected time to share: 5.2 minutes
2013-07-08 03:24:02.404136  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.8% (10-43%) Current payout: 0.0000 BTC
2013-07-08 03:24:02.404172  Pool: 1082GH/s Stale rate: 17.8% Expected time to block: 23.5 hours
2013-07-08 03:24:02.566501
2013-07-08 03:24:02.583036 New work for worker! Difficulty: 1.000000 Share difficulty: 1822.099522 Total block value: 25.131832 BTC including 205 transactions
2013-07-08 03:24:03.503839
2013-07-08 03:24:03.516460 New work for worker! Difficulty: 1.000000 Share difficulty: 1822.099522 Total block value: 25.131832 BTC including 205 transactions
2013-07-08 03:24:05.430216 P2Pool: 17382 shares in chain (17387 verified/17387 total) Peers: 8 (2 incoming)
2013-07-08 03:24:05.430315  Local: 24789MH/s in last 10.0 minutes Local dead on arrival: ~62.8% (61-65%) Expected time to share: 5.2 minutes
2013-07-08 03:24:05.430346  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.9% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:24:05.430382  Pool: 1082GH/s Stale rate: 18.0% Expected time to block: 23.5 hours
2013-07-08 03:24:08.454549 P2Pool: 17382 shares in chain (17387 verified/17387 total) Peers: 8 (2 incoming)
2013-07-08 03:24:08.454667  Local: 24839MH/s in last 10.0 minutes Local dead on arrival: ~63.2% (61-65%) Expected time to share: 5.2 minutes
2013-07-08 03:24:08.454700  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.9% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:24:08.454735  Pool: 1082GH/s Stale rate: 18.0% Expected time to block: 23.5 hours
2013-07-08 03:24:11.477941 P2Pool: 17382 shares in chain (17387 verified/17387 total) Peers: 8 (2 incoming)
2013-07-08 03:24:11.478042  Local: 24875MH/s in last 10.0 minutes Local dead on arrival: ~63.2% (61-65%) Expected time to share: 5.2 minutes
2013-07-08 03:24:11.478074  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.9% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:24:11.478108  Pool: 1082GH/s Stale rate: 18.0% Expected time to block: 23.5 hours
2013-07-08 03:24:12.233209 Worker pioruns10_beblade submitted share with hash > target:
2013-07-08 03:24:12.233382     Hash:   f79cfa608f20a6de27ccbe1f220f574a5eda08435058e0d4031550c30c45468e
2013-07-08 03:24:12.233516     Target: ffff0000000000000000000000000000000000000000000000000000
2013-07-08 03:24:14.497799 P2Pool: 17382 shares in chain (17387 verified/17387 total) Peers: 8 (2 incoming)
2013-07-08 03:24:14.497899  Local: 24839MH/s in last 10.0 minutes Local dead on arrival: ~63.5% (61-66%) Expected time to share: 5.2 minutes
2013-07-08 03:24:14.497957  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.9% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:24:14.498007  Pool: 1082GH/s Stale rate: 18.0% Expected time to block: 23.5 hours
2013-07-08 03:24:17.526430 P2Pool: 17382 shares in chain (17387 verified/17387 total) Peers: 8 (2 incoming)
2013-07-08 03:24:17.526532  Local: 24846MH/s in last 10.0 minutes Local dead on arrival: ~63.2% (61-65%) Expected time to share: 5.2 minutes
2013-07-08 03:24:17.526588  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.9% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:24:17.526638  Pool: 1082GH/s Stale rate: 18.0% Expected time to block: 23.5 hours
2013-07-08 03:24:20.548909 P2Pool: 17382 shares in chain (17387 verified/17387 total) Peers: 8 (2 incoming)
2013-07-08 03:24:20.549029  Local: 24904MH/s in last 10.0 minutes Local dead on arrival: ~62.8% (61-65%) Expected time to share: 5.2 minutes
2013-07-08 03:24:20.550870  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.9% (10-44%) Current payout: 0.0000 BTC
2013-07-08 03:24:20.551029  Pool: 1082GH/s Stale rate: 18.0% Expected time to block: 23.5 hours
2013-07-08 03:24:23.583923 P2Pool: 17382 shares in chain (17387 verified/17387 total) Peers: 8 (2 incoming)
2013-07-08 03:24:23.584022  Local: 24889MH/s in last 10.0 minutes Local dead on arrival: ~62.5% (60-65%) Expected time to share: 5.2 minutes
2013-07-08 03:24:23.584054  Shares: 32 (1 orphan, 25 dead) Stale rate: ~81.2% (64-92%) Efficiency: ~22.9% (10-44%) Current payout: 0.0000 BTC

I cannot prevent other users to connect to my node and start mining with BE Blades. If they will not setup +1 to username, my p2pool log will be spammed with thousands of error messages. How to fix it in p2pool code?

[freshzive]

so before we can expect to see any better behavior with ASICS we need to wait until 95% of the pool has upgraded, correct?

[bitpop]

Yes we haven't forked yet

[kano]

so before we can expect to see any better behavior with ASICS we need to wait until 95% of the pool has upgraded, correct?

However, the BFL 1.2.5 firmware makes the Jalapeno worse and all the rest of BFLSC the same.
If the chips are doing 4GH/s it takes ~0.93s to do a nonce range (and they are not divided up across the chips)
So expect around 3.1% work loss (when p2pool goes to 30s) just due to the way the BFLSC firmware works.
As I've stated long ago on the BFL forum, the fix for p2pool is quite straight forward, but still no response about it being done.
https://forums.butterflylabs.com/announcements/913-bitforce-sc-communication-protocol-draft-revision-2-a-8.html#post31853

[General-Beck]

http://general-beck.ru:9327 update, worked fine.

[maqifrnswa]

so before we can expect to see any better behavior with ASICS we need to wait until 95% of the pool has upgraded, correct?

However, the BFL 1.2.5 firmware makes the Jalapeno worse and all the rest of BFLSC the same.
If the chips are doing 4GH/s it takes ~0.93s to do a nonce range (and they are not divided up across the chips)
So expect around 3.1% work loss (when p2pool goes to 30s) just due to the way the BFLSC firmware works.
As I've stated long ago on the BFL forum, the fix for p2pool is quite straight forward, but still no response about it being done.
https://forums.butterflylabs.com/announcements/913-bitforce-sc-communication-protocol-draft-revision-2-a-8.html#post31853

If we hack
https://github.com/luke-jr/BitForce_SC/blob/e9e6a41fd76050a3aea2ab973c808f4cede174eb/BitForce_SC/ASIC_Engine.c
in function
ASIC_calculate_engines_nonce_range()

and divide line 1761 by some factor
https://github.com/luke-jr/BitForce_SC/blob/e9e6a41fd76050a3aea2ab973c808f4cede174eb/BitForce_SC/ASIC_Engine.c#L1761

we should reduce the nonce range by that factor.

This is a myopic hack, but would it work? you know the code intimately, i'm just pulling at straws here.

[furball]

Harvestcoin server at http://mining.harvestcoin.com:9327 has been updated...thanks very much for the hard work!

[kano]

so before we can expect to see any better behavior with ASICS we need to wait until 95% of the pool has upgraded, correct?

However, the BFL 1.2.5 firmware makes the Jalapeno worse and all the rest of BFLSC the same.
If the chips are doing 4GH/s it takes ~0.93s to do a nonce range (and they are not divided up across the chips)
So expect around 3.1% work loss (when p2pool goes to 30s) just due to the way the BFLSC firmware works.
As I've stated long ago on the BFL forum, the fix for p2pool is quite straight forward, but still no response about it being done.
https://forums.butterflylabs.com/announcements/913-bitforce-sc-communication-protocol-draft-revision-2-a-8.html#post31853

If we hack
https://github.com/luke-jr/BitForce_SC/blob/e9e6a41fd76050a3aea2ab973c808f4cede174eb/BitForce_SC/ASIC_Engine.c
in function
ASIC_calculate_engines_nonce_range()

and divide line 1761 by some factor
https://github.com/luke-jr/BitForce_SC/blob/e9e6a41fd76050a3aea2ab973c808f4cede174eb/BitForce_SC/ASIC_Engine.c#L1761

we should reduce the nonce range by that factor.

This is a myopic hack, but would it work? you know the code intimately, i'm just pulling at straws here.

I just look at the original of 1.2.5 from Nasser, but yeah with a few minor changes in there you could make it hash a fraction of a nonce range every time instead of the full range.

The only (minor) catch is that of course you are sending n times the amount of work and generating n times the amount of work in cgminer.
It becomes a major catch if you are dividing it too much.
You'd also have to change my FULLNONCE definition in driver-bflsc.c (around line 77)

[baloo_kiev]

node: lenny.dnsd.me:9332
I setup BE Blade to use +1 pseudoshare (+1 to username). However, I am still getting these errors, but not so often as before.
Log below:
There's also someone mining on my node right now on BE Blade (12.6GH/s hashrate, 7.6GH/s of it - DOA). Looks like he setup +1 to username as well.

I cannot prevent other users to connect to my node and start mining with BE Blades. If they will not setup +1 to username, my p2pool log will be spammed with thousands of error messages. How to fix it in p2pool code?

50% DOA is just what is expected and it will probably drop to about 18% after share period switch.

Blades send diff1 shares regardles of what the node tells, so if the difficulty is set higher, a part of pseudoshares will be reported 'hash > target'. Those rare cases reported when you set diff to 1 are just hardware errors which are not filtered by the blade's software (my AM USB's chip produces about 1% or less HW errors depending on temperature).

Any code tweaks most likely won't decrease your node load. If you want to get rid of these messages in your log, just comment out lines 413 to 415 in p2pool/work.py.

[maqifrnswa]

I just look at the original of 1.2.5 from Nasser, but yeah with a few minor changes in there you could make it hash a fraction of a nonce range every time instead of the full range.

The only (minor) catch is that of course you are sending n times the amount of work and generating n times the amount of work in cgminer.
It becomes a major catch if you are dividing it too much.
You'd also have to change my FULLNONCE definition in driver-bflsc.c (around line 77)

great summary by Kano on BFL forums, https://forums.butterflylabs.com/announcements/3282-bitforce-sc-firmware-version-1-2-5-a-5.html#post46125

I job per chip is worse, not better (for p2pool) However if it runs 50% faster, well I guess that doesn't matter

Anyway,
the biggest issue with the MCU design in the FPGA was that it doesn't give you an answer until it completes the work.
The SC does the same thing.

So e.g. with 10 chips doing 4GH/s each, instead of getting 1 answer in 0.093 seconds, you get 10 answers in 0.93 seconds.
Thus latency is worse with the 1 job per chip firmware.

As I have said elsewhere (since 20-Jun), the simple fix is grade school maths level:
Divide the job up based on the speed of each chip, not give each chip it's own job, faster chips get a larger nonce range, slower chips get a smaller range.
Basically, set it so that all chips complete about the same time based on their performance.
The total number range is 4,294,967,296 so it's not hard to divide it up and get a very close finishing time for each chip
(and you can determine the ranges once and use them until it readjusts the chip performance)

With 1.2.5 on 10s p2pool, you'll still get roughly 9.3% stale on all BFLSCs - each chip will be doing work when an LP hits and the MCU will wait for each chip to complete it's job before it starts a new one and have a stale result from each - being 9.3% of the 10s share LP time (or 3.1% of the soon to be increased 30s LP)

[Anonymailer]

Considering BFL have been too lazy to make P2Pool a consideration, they really should throw some of that BTC1000 donation fund they setup towards forrestv, cg and bfgminer teams for doing this work for them.

[baloo_kiev]

Considering BFL have been too lazy to make P2Pool a consideration, they really should throw some of that BTC1000 donation fund they setup towards forrestv, cg and bfgminer teams for doing this work for them.

They just don't care. Josh doesn't even know what is p2pool. This perfectly fits his "money printing" conception. They should start shipping standalone miners with pre-set standard config: main pool Guild, backup pool 50BTC, option to set your MtGox and bank account, so after quick configuration you just power it up and receive USD straight to your account, and forget about bitcoins

[Searinox]

The new P2Pool is frequently freezing up and using 50% CPU for a minute at a time.

Update: Restarting them along with the node after the initial share download fixes it. I've repro'd this issue on 2 machines.

[forrestv]

P2Pool release 13.1  - commit hash: 94b87f6c9c04c292bca9565961f83198438f0f76

Windows binary: http://u.forre.st/u/xmqipwes/p2pool_win32_13.1.zip
Windows binary signature: http://u.forre.st/u/apxlhewu/p2pool_win32_13.1.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/13.1
Source tarball: https://github.com/forrestv/p2pool/tarball/13.1

Changes:
The hardfork hasn't happened yet, and this release fixes a potential problem that could cause people mining with non-standard transaction inclusion options to have their shares orphaned more often.