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

[K1773R]

just wanted to test LTC and p2pool with LTC, litecoind is missing the submitblock RCP call and therefore it dosnt work, anoyne encountered this before?
https://github.com/litecoin-project/litecoin/issues/20

EDIT: nvm, p2pool still was using bitcoin logic even with --net litecoin, after restarting several times it worked.

[1713527081]

1713527081

[1713527081]

1713527081

[1713527081]

1713527081

[1713527081]

1713527081

[1713527081]

1713527081

[K1773R]

My getwork latency is 0.211s mean. Had one spike up to 0.8s
I dont know if its good or bad. Whats your latency?
Also how can i optimize?

Use bitcoind from git.
Put bitcoind on SSD disk if you have.
Or use some RAID array.

On my RAID1 (mirror) with 2 disk 10k RPM i have under 0.1 latancy (now  is 0.0539s mean)

even better, use it over ext4 for extreme caching speed
also renicing it to -10 gives ALOT of latency reduce

[Red Emerald]

My getwork latency is 0.211s mean. Had one spike up to 0.8s
I dont know if its good or bad. Whats your latency?
Also how can i optimize?

Use bitcoind from git.
Put bitcoind on SSD disk if you have.
Or use some RAID array.

On my RAID1 (mirror) with 2 disk 10k RPM i have under 0.1 latancy (now  is 0.0539s mean)

even better, use it over ext4 for extreme caching speed
also renicing it to -10 gives ALOT of latency reduce

I hadn't thought about using nice or ext4. I'll have to try that.

I think ionice might help even more.

[K1773R]

My getwork latency is 0.211s mean. Had one spike up to 0.8s
I dont know if its good or bad. Whats your latency?
Also how can i optimize?

Use bitcoind from git.
Put bitcoind on SSD disk if you have.
Or use some RAID array.

On my RAID1 (mirror) with 2 disk 10k RPM i have under 0.1 latancy (now  is 0.0539s mean)

even better, use it over ext4 for extreme caching speed
also renicing it to -10 gives ALOT of latency reduce

I hadn't thought about using nice or ext4. I'll have to try that.

I think ionice might help even more.

ionice is unecessary with ext4.

[Red Emerald]

My getwork latency is 0.211s mean. Had one spike up to 0.8s
I dont know if its good or bad. Whats your latency?
Also how can i optimize?

Use bitcoind from git.
Put bitcoind on SSD disk if you have.
Or use some RAID array.

On my RAID1 (mirror) with 2 disk 10k RPM i have under 0.1 latancy (now  is 0.0539s mean)

even better, use it over ext4 for extreme caching speed
also renicing it to -10 gives ALOT of latency reduce

I hadn't thought about using nice or ext4. I'll have to try that.

I think ionice might help even more.

ionice is unecessary with ext4.

Really? Why is that? A quick google search didn't turn up anything.

I'm on ext3, so I'll play with ionice anyway

[K1773R]

My getwork latency is 0.211s mean. Had one spike up to 0.8s
I dont know if its good or bad. Whats your latency?
Also how can i optimize?

Use bitcoind from git.
Put bitcoind on SSD disk if you have.
Or use some RAID array.

On my RAID1 (mirror) with 2 disk 10k RPM i have under 0.1 latancy (now  is 0.0539s mean)

even better, use it over ext4 for extreme caching speed
also renicing it to -10 gives ALOT of latency reduce

I hadn't thought about using nice or ext4. I'll have to try that.

I think ionice might help even more.

ionice is unecessary with ext4.

Really? Why is that? A quick google search didn't turn up anything.

I'm on ext3, so I'll play with ionice anyway

ext3 has some seconds until a flush of queue is forced, ext4 up to 120 seconds, therefore u can read/write alot (my ext4 got 4GB buffer depends on system/kernel settings) and therefore u can easely write/read stuff without the need for flushing it instantly, therefore new miners will get the work and some seconds later it gets flushed to disk ionice is good if there is continues rw going on @ the HD, but if you do all these operations in cache anyway it dosnt matter. you should ionice it to -c 3 (idle) otherwise the whole system may hang while its being flushed (then even p2pool cant write to its sharechain). sry for all the typos, tired as hell, gtg sleep

[rav3n_pl]

Got cure for giant transfers in TRC nodes:
https://github.com/Rav3nPL/p2pool/commit/1685c53a5dc5f394ecc13345b7bbe61429e5792e
There is at least one badly updated/hacked TRC node that are messing in TRC chain.
Patch is affecting ONLY TRC nodes, can be applied safe in BTC/LTC ones. Maybe more users will run own TRC nodes

EDIT:
User of node 94.219.146.231 plz update your TRC stuff. Your node is asking for shares over and over...

[stevegee58]

I stopped mining p2pool a few weeks ago but I noticed that I'm still getting hits on port 9333 all the time.

Wouldn't p2pool forget my IP address after it's no longer active?

[rav3n_pl]

AFIK there is no way to "forget" node other than delete 'addrs' file from 'data' directory.
Those hits are harmless. Block port on router if it is brothering you much.

I stopped mining p2pool a few weeks ago but I noticed that I'm still getting hits on port 9333 all the time.

Wouldn't p2pool forget my IP address after it's no longer active?

[K1773R]

Got cure for giant transfers in TRC nodes:
https://github.com/Rav3nPL/p2pool/commit/1685c53a5dc5f394ecc13345b7bbe61429e5792e
There is at least one badly updated/hacked TRC node that are messing in TRC chain.
Patch is affecting ONLY TRC nodes, can be applied safe in BTC/LTC ones. Maybe more users will run own TRC nodes

EDIT:
User of node 94.219.146.231 plz update your TRC stuff. Your node is asking for shares over and over...

just block him and its fine?

[rav3n_pl]

Got cure for giant transfers in TRC nodes:
https://github.com/Rav3nPL/p2pool/commit/1685c53a5dc5f394ecc13345b7bbe61429e5792e
There is at least one badly updated/hacked TRC node that are messing in TRC chain.
Patch is affecting ONLY TRC nodes, can be applied safe in BTC/LTC ones. Maybe more users will run own TRC nodes

EDIT:
User of node 94.219.146.231 plz update your TRC stuff. Your node is asking for shares over and over...

just block him and its fine?

It is making ~20k/s form 0.5k/s traffic. I can block it, but he will bang to other nodes and make them suffer wasted traffic. I have unlimited bandwidth, but not ever1 have that luxury.

[tiberiandusk]

My internet is terrible. getblock latency is always around 1-1.5 seconds.

[rav3n_pl]

My internet is terrible. getblock latency is always around 1-1.5 seconds.

It is more like CPU/bitcoind troubles, not internet.

[zvs]

My getwork latency is 0.211s mean. Had one spike up to 0.8s
I dont know if its good or bad. Whats your latency?
Also how can i optimize?

Use bitcoind from git.
Put bitcoind on SSD disk if you have.
Or use some RAID array.

On my RAID1 (mirror) with 2 disk 10k RPM i have under 0.1 latancy (now  is 0.0539s mean)

i've only been running it for an hour, but my "Bitcoind GetBlockTemplate Latency" is 0.15-0.20s..... is this the same thing?       don't see how it could be much faster, as it runs off a ram drive already

maybe having 800 outgoing connections in bitcoind slows it down?

i've noticed that i'm showing around 25.75 block value (with fees) while everyone else is 25.2 or less.   i guess that would slow it down?  

scratch.

example:

http://nogleg.com:9332/static/share.html#00000000003cc762db443f6f0a2df00b83e33f14a7fe021c22c740b23f8cd051

vs

http://nogleg.com:9332/static/share.html#00000000004057867aca8a5eeee954d4a512f572e2df86ae981092caff8f4f1d
http://nogleg.com:9332/static/share.html#00000000001700565889f549a456173c2595dc84fd98db13d3c9a8de9f9882c9
http://nogleg.com:9332/static/share.html#00000000002ee676f00cc3be921bc9cdffdaaa10a3558843e329e2555e24401f

(the next 3)

[zvs]

also, can someone clarify what this means:

2012-12-22 14:34:37.330552 Skipping from block 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f to block 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434!
2012-12-22 14:34:38.159596 P2Pool: 17399 shares in chain (9699 verified/17403 total) Peers: 8 (2 incoming)
2012-12-22 14:34:38.159652  Local: 6892MH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-6%) Expected time to share: 6.8 minutes
2012-12-22 14:34:38.159672  Shares: 17 (0 orphan, 0 dead) Stale rate: ~0.0% (0-19%) Efficiency: ~117.5% (95-118%) Current payout: 0.0511 BTC
2012-12-22 14:34:38.159693  Pool: 323GH/s Stale rate: 14.9% Expected time to block: 12.4 hours
2012-12-22 14:34:38.692333 Punishing share for 'Block-stale detected! 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434 < 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f'! Jumping from b284721e to 18d04958!
2012-12-22 14:34:39.114153 GOT SHARE!  ab9d1818 prev 18d04958 age 8.55s
2012-12-22 14:34:39.124374 New work for worker! Difficulty: 1.286614 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:39.132938 New work for worker! Difficulty: 1.286614 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:39.373962 New work for worker! Difficulty: 1.259615 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:41.161616 P2Pool: 17400 shares in chain (9701 verified/17405 total) Peers: 8 (2 incoming)
2012-12-22 14:34:41.161679  Local: 6910MH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:41.161698  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:41.161719  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:44.164537 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:44.164590  Local: 6915MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:44.164608  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:44.164629  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:47.166613 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:47.166696  Local: 6922MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:47.166730  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:47.166757  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:50.169344 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:50.169401  Local: 6942MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:50.169420  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:50.169440  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:50.405453 New work for worker! Difficulty: 1.410955 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:52.592338 Skipping from block 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f to block 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434!
2012-12-22 14:34:53.172031 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:53.172114  Local: 6972MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:53.172139  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0543 BTC
2012-12-22 14:34:53.172165  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:53.965183 New work for worker! Difficulty: 1.572481 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:53.974331 New work for worker! Difficulty: 1.572481 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:54.237588 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:54.293442 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:54.497860 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:56.173854 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:56.173919  Local: 6969MH/s in last 10.0 minutes Local dead on arrival: ~4.2% (2-7%) Expected time to share: 6.7 minutes
2012-12-22 14:34:56.173947  Shares: 18 (1 orphan, 0 dead) Stale rate: ~5.6% (0-26%) Efficiency: ~110.7% (87-117%) Current payout: 0.0507 BTC
2012-12-22 14:34:56.173969  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours





it still seems to me that p2pool punishes good connections, by DOA'ing and orphaning valid shares, based on other ppls slow connections?    and why do i skip blocks like 4 or 5 times?

[K1773R]

also, can someone clarify what this means:

2012-12-22 14:34:37.330552 Skipping from block 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f to block 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434!
2012-12-22 14:34:38.159596 P2Pool: 17399 shares in chain (9699 verified/17403 total) Peers: 8 (2 incoming)
2012-12-22 14:34:38.159652  Local: 6892MH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-6%) Expected time to share: 6.8 minutes
2012-12-22 14:34:38.159672  Shares: 17 (0 orphan, 0 dead) Stale rate: ~0.0% (0-19%) Efficiency: ~117.5% (95-118%) Current payout: 0.0511 BTC
2012-12-22 14:34:38.159693  Pool: 323GH/s Stale rate: 14.9% Expected time to block: 12.4 hours
2012-12-22 14:34:38.692333 Punishing share for 'Block-stale detected! 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434 < 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f'! Jumping from b284721e to 18d04958!
2012-12-22 14:34:39.114153 GOT SHARE!  ab9d1818 prev 18d04958 age 8.55s
2012-12-22 14:34:39.124374 New work for worker! Difficulty: 1.286614 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:39.132938 New work for worker! Difficulty: 1.286614 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:39.373962 New work for worker! Difficulty: 1.259615 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:41.161616 P2Pool: 17400 shares in chain (9701 verified/17405 total) Peers: 8 (2 incoming)
2012-12-22 14:34:41.161679  Local: 6910MH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:41.161698  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:41.161719  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:44.164537 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:44.164590  Local: 6915MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:44.164608  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:44.164629  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:47.166613 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:47.166696  Local: 6922MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:47.166730  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:47.166757  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:50.169344 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:50.169401  Local: 6942MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:50.169420  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:50.169440  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:50.405453 New work for worker! Difficulty: 1.410955 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:52.592338 Skipping from block 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f to block 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434!
2012-12-22 14:34:53.172031 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:53.172114  Local: 6972MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:53.172139  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0543 BTC
2012-12-22 14:34:53.172165  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:53.965183 New work for worker! Difficulty: 1.572481 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:53.974331 New work for worker! Difficulty: 1.572481 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:54.237588 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:54.293442 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:54.497860 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:56.173854 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:56.173919  Local: 6969MH/s in last 10.0 minutes Local dead on arrival: ~4.2% (2-7%) Expected time to share: 6.7 minutes
2012-12-22 14:34:56.173947  Shares: 18 (1 orphan, 0 dead) Stale rate: ~5.6% (0-26%) Efficiency: ~110.7% (87-117%) Current payout: 0.0507 BTC
2012-12-22 14:34:56.173969  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours





it still seems to me that p2pool punishes good connections, by DOA'ing and orphaning valid shares, based on other ppls slow connections?    and why do i skip blocks like 4 or 5 times?

because the blocks in the p2pool sharechain or bitcoin sharechain became invalid/stale.

block value is always different due to the reason that all transaction fees are included in this number, the more transactions the higher a block value.

[zvs]

also, can someone clarify what this means:

2012-12-22 14:34:37.330552 Skipping from block 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f to block 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434!
2012-12-22 14:34:38.159596 P2Pool: 17399 shares in chain (9699 verified/17403 total) Peers: 8 (2 incoming)
2012-12-22 14:34:38.159652  Local: 6892MH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-6%) Expected time to share: 6.8 minutes
2012-12-22 14:34:38.159672  Shares: 17 (0 orphan, 0 dead) Stale rate: ~0.0% (0-19%) Efficiency: ~117.5% (95-118%) Current payout: 0.0511 BTC
2012-12-22 14:34:38.159693  Pool: 323GH/s Stale rate: 14.9% Expected time to block: 12.4 hours
2012-12-22 14:34:38.692333 Punishing share for 'Block-stale detected! 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434 < 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f'! Jumping from b284721e to 18d04958!
2012-12-22 14:34:39.114153 GOT SHARE!  ab9d1818 prev 18d04958 age 8.55s
2012-12-22 14:34:39.124374 New work for worker! Difficulty: 1.286614 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:39.132938 New work for worker! Difficulty: 1.286614 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:39.373962 New work for worker! Difficulty: 1.259615 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:41.161616 P2Pool: 17400 shares in chain (9701 verified/17405 total) Peers: 8 (2 incoming)
2012-12-22 14:34:41.161679  Local: 6910MH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:41.161698  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:41.161719  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:44.164537 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:44.164590  Local: 6915MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:44.164608  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:44.164629  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:47.166613 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:47.166696  Local: 6922MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:47.166730  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:47.166757  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:50.169344 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:50.169401  Local: 6942MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:50.169420  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:50.169440  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:50.405453 New work for worker! Difficulty: 1.410955 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:52.592338 Skipping from block 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f to block 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434!
2012-12-22 14:34:53.172031 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:53.172114  Local: 6972MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:53.172139  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0543 BTC
2012-12-22 14:34:53.172165  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:53.965183 New work for worker! Difficulty: 1.572481 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:53.974331 New work for worker! Difficulty: 1.572481 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:54.237588 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:54.293442 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:54.497860 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:56.173854 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:56.173919  Local: 6969MH/s in last 10.0 minutes Local dead on arrival: ~4.2% (2-7%) Expected time to share: 6.7 minutes
2012-12-22 14:34:56.173947  Shares: 18 (1 orphan, 0 dead) Stale rate: ~5.6% (0-26%) Efficiency: ~110.7% (87-117%) Current payout: 0.0507 BTC
2012-12-22 14:34:56.173969  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours





it still seems to me that p2pool punishes good connections, by DOA'ing and orphaning valid shares, based on other ppls slow connections?    and why do i skip blocks like 4 or 5 times?

because the blocks in the p2pool sharechain or bitcoin sharechain became invalid/stale.

block value is always different due to the reason that all transaction fees are included in this number, the more transactions the higher a block value.

right, i knew about that, re: transaction fees.  the larger block size could result a few more ms (given that all of p2pool and bitcoind reside on a ramdisk), but some other person was reporting less than .10 seconds on the 'Bitcoind GetBlockTemplate Latency' stat.. (correct me if I'm wrong)

would it be faster if it only had 8 outgoing connections?  but, then, would I not also be causing more orphans by receiving blocks from the network slower?  i don't know how else to explain the above orphan.  i 'skipped ahead' to the next block, found a share, and then i 'skipped ahead to the next block' (same one) again, and it was counted as an orphan.

'Punishing share for 'Block-stale detected! 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434 < 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f'! Jumping from b284721e to 18d04958!'

??

[K1773R]

also, can someone clarify what this means:

2012-12-22 14:34:37.330552 Skipping from block 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f to block 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434!
2012-12-22 14:34:38.159596 P2Pool: 17399 shares in chain (9699 verified/17403 total) Peers: 8 (2 incoming)
2012-12-22 14:34:38.159652  Local: 6892MH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-6%) Expected time to share: 6.8 minutes
2012-12-22 14:34:38.159672  Shares: 17 (0 orphan, 0 dead) Stale rate: ~0.0% (0-19%) Efficiency: ~117.5% (95-118%) Current payout: 0.0511 BTC
2012-12-22 14:34:38.159693  Pool: 323GH/s Stale rate: 14.9% Expected time to block: 12.4 hours
2012-12-22 14:34:38.692333 Punishing share for 'Block-stale detected! 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434 < 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f'! Jumping from b284721e to 18d04958!
2012-12-22 14:34:39.114153 GOT SHARE!  ab9d1818 prev 18d04958 age 8.55s
2012-12-22 14:34:39.124374 New work for worker! Difficulty: 1.286614 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:39.132938 New work for worker! Difficulty: 1.286614 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:39.373962 New work for worker! Difficulty: 1.259615 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:41.161616 P2Pool: 17400 shares in chain (9701 verified/17405 total) Peers: 8 (2 incoming)
2012-12-22 14:34:41.161679  Local: 6910MH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:41.161698  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:41.161719  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:44.164537 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:44.164590  Local: 6915MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:44.164608  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:44.164629  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:47.166613 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:47.166696  Local: 6922MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:47.166730  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:47.166757  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:50.169344 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:50.169401  Local: 6942MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:50.169420  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:50.169440  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:50.405453 New work for worker! Difficulty: 1.410955 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:52.592338 Skipping from block 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f to block 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434!
2012-12-22 14:34:53.172031 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:53.172114  Local: 6972MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:53.172139  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0543 BTC
2012-12-22 14:34:53.172165  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:53.965183 New work for worker! Difficulty: 1.572481 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:53.974331 New work for worker! Difficulty: 1.572481 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:54.237588 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:54.293442 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:54.497860 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:56.173854 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:56.173919  Local: 6969MH/s in last 10.0 minutes Local dead on arrival: ~4.2% (2-7%) Expected time to share: 6.7 minutes
2012-12-22 14:34:56.173947  Shares: 18 (1 orphan, 0 dead) Stale rate: ~5.6% (0-26%) Efficiency: ~110.7% (87-117%) Current payout: 0.0507 BTC
2012-12-22 14:34:56.173969  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours





it still seems to me that p2pool punishes good connections, by DOA'ing and orphaning valid shares, based on other ppls slow connections?    and why do i skip blocks like 4 or 5 times?

because the blocks in the p2pool sharechain or bitcoin sharechain became invalid/stale.

block value is always different due to the reason that all transaction fees are included in this number, the more transactions the higher a block value.

right, i knew about that, re: transaction fees.  the larger block size could result a few more ms (given that all of p2pool and bitcoind reside on a ramdisk), but some other person was reporting less than .10 seconds on the 'Bitcoind GetBlockTemplate Latency' stat.. (correct me if I'm wrong)

would it be faster if it only had 8 outgoing connections?  but, then, would I not also be causing more orphans by receiving blocks from the network slower?  i don't know how else to explain the above orphan.  i 'skipped ahead' to the next block, found a share, and then i 'skipped ahead to the next block' (same one) again, and it was counted as an orphan.

'Punishing share for 'Block-stale detected! 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434 < 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f'! Jumping from b284721e to 18d04958!'

??

it may be slower, u wont get orphans due to that since u sibmit ur shares to the p2pool sharechain. i usually got 0 orphans and some doas due to the reason i got 100 connections to other nodes.

[zvs]

it may be slower, u wont get orphans due to that since u sibmit ur shares to the p2pool sharechain. i usually got 0 orphans and some doas due to the reason i got 100 connections to other nodes.

hmm, do you (or anyone else) have a list of all the p2pool nodes that are connectable (i guess there's an -addnode equivalent?) that sustain 3+ ghash??


oh, everyone feel free to addnode 5.9.24.81 in p2pool list

[K1773R]

it may be slower, u wont get orphans due to that since u sibmit ur shares to the p2pool sharechain. i usually got 0 orphans and some doas due to the reason i got 100 connections to other nodes.

hmm, do you (or anyone else) have a list of all the p2pool nodes that are connectable (i guess there's an -addnode equivalent?) that sustain 3+ ghash??


oh, everyone feel free to addnode 5.9.24.81 in p2pool list

5.*.*.* is illegal.

if ur pool is accessable then just wait otherwise use --outgoing-conns
hashrate of the pool dosnt matter.