Uh, you've got it as the exact opposite of what the reality is
Slow nodes aren't being punished... furthermore, if they found a block while generating these useless shares, then it'd be an orphaned block
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 507. (Read 2591928 times)
Now consider the rule defined by those 3 lines I was talking about. It states "If a share (S) is based on stale block, mine on its parent (P)." (That's what "Punishing for block-stale / Jumping to ..." log message is about.) If a miner (either intentionally or because of slow bitcoind) disrespects this rule, not only he loses nothing, but may also eventually profit from it! Really, his share A (a child of block-stale share S, which is punished by the rest of the network) is 1 share ahead of "proper" miner's share B, which is P's child. As a result, A will have priority over B even if B is found earlier!
Should I report a bug on GitHub?
You should. But read below why I think it's not high priority.
2 cases in your example:
- local bitcoind lagging: miner is punished most of the time so it is prevented to benefit from worthless work as intended and is motivated to upgrade his/her configuration
- node trying to make his share more resilient by avoiding to build on the parent share
In the "more resilient attack" the node can only attack after one out of 20 shares (30s share interval with 10mn block interval) if and only if it is from a slow node producing a stale share (assuming we don't have nodes more than 30-60s behind the Bitcoin network able to make 2 successive stale shares).
- if another node finds a share before him he will automatically switch to it as building on either fork doesn't give him any benefit anymore
- if he finds a share before the rest of the network, he won't have gained anything (he has as much chances of that happening when mining on the parent share)
- the only gain is when he finds a share that collides with another : there he will be sure to win instead of having ~50% chances
So someone trying this attack will get benefit for less than 5% (1 in 20 at most, probably far less) of his expected DOA+Orphan rate (which seems to be ~10% since we switched to a 30s share interval) and this benefit will be ~50%.
So in the most pathological case where 100% of the network produces stale shares (built with the previous block), the expected benefit is only 50% of 10% of 5% : 0.25%.
Most nodes probably don't produce stale shares, so this is more likely a ~0.1% advantage.
Now what is the attacker losing? If you don't punish slow nodes you are hurting yourself as much as the rest of the network by validating wasted work. The exception is the slow node which is grateful to be paid for worthless work.
For every gained share you are validating one worthless share. If everyone did this, everyone would lose money to worthless shares producers instead of gaining 0.1%. Now it's too late for me to try to estimate how much is lost but disabling the protection might not be a good idea, especially if many are doing it. It probably would end in a "tragedy of the commons": you can gain a bit by doing it, but when everyone does it, everyone loses.
Allowing worthless work allows it to rise without limits: if there are very slow bitcoinds with very high hashrate they could make 2 or more consecutive stale shares a frequent occasion and rise the worthless hashrate to 10 or more percent of the whole pool.
One solution might be to ignore stale shares when comparing the different sharechain forks. People disabling the protection would get no benefit at all.
In the meanwhile, advocating to remove the protection is an attack on P2Pool, please stop doing it unless you want to participate in your own reduced income.[/list]
i have it running now if someone wanted to test before setting up local node or something
Exactly
Quote
Now consider the rule defined by those 3 lines I was talking about. It states "If a share (S) is based on stale block, mine on its parent (P)." (That's what "Punishing for block-stale / Jumping to ..." log message is about.) If a miner (either intentionally or because of slow bitcoind) disrespects this rule, not only he loses nothing, but may also eventually profit from it! Really, his share A (a child of block-stale share S, which is punished by the rest of the network) is 1 share ahead of "proper" miner's share B, which is P's child. As a result, A will have priority over B even if B is found earlier!
Exactly
P2Pool release 13.2 - commit hash: a7e081924e8bd1f3a7b57dc34499475b8cd458a5
Windows binary: http://u.forre.st/u/xypigdde/p2pool_win32_13.2.zip
Windows binary signature: http://u.forre.st/u/vuopsaei/p2pool_win32_13.2.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/13.2
Source tarball: https://github.com/forrestv/p2pool/tarball/13.2
Changes:
* Out-of-the-box Avalon device support - simply point Avalon devices to http://P2POOL_HOST:9332/
Windows binary: http://u.forre.st/u/xypigdde/p2pool_win32_13.2.zip
Windows binary signature: http://u.forre.st/u/vuopsaei/p2pool_win32_13.2.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/13.2
Source tarball: https://github.com/forrestv/p2pool/tarball/13.2
Changes:
* Out-of-the-box Avalon device support - simply point Avalon devices to http://P2POOL_HOST:9332/
Well done!
P2Pool release 13.2 - commit hash: a7e081924e8bd1f3a7b57dc34499475b8cd458a5
Windows binary: http://u.forre.st/u/xypigdde/p2pool_win32_13.2.zip
Windows binary signature: http://u.forre.st/u/vuopsaei/p2pool_win32_13.2.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/13.2
Source tarball: https://github.com/forrestv/p2pool/tarball/13.2
Changes:
* Out-of-the-box Avalon device support - simply point Avalon devices to http://P2POOL_HOST:9332/
Windows binary: http://u.forre.st/u/xypigdde/p2pool_win32_13.2.zip
Windows binary signature: http://u.forre.st/u/vuopsaei/p2pool_win32_13.2.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/13.2
Source tarball: https://github.com/forrestv/p2pool/tarball/13.2
Changes:
* Out-of-the-box Avalon device support - simply point Avalon devices to http://P2POOL_HOST:9332/
Sorry for misunderstanding here. When saying "broken", I mean not broken code but wrong algorithm/strategy.
One of principal rules of mining, as I understand it, is "A miner who breaks a rule must be punished." For example, if you mine not on the latest block but its parent, or mine invalid blocks, your work will be orphaned by the rest of network.
Now consider the rule defined by those 3 lines I was talking about. It states "If a share (S) is based on stale block, mine on its parent (P)." (That's what "Punishing for block-stale / Jumping to ..." log message is about.) If a miner (either intentionally or because of slow bitcoind) disrespects this rule, not only he loses nothing, but may also eventually profit from it! Really, his share A (a child of block-stale share S, which is punished by the rest of the network) is 1 share ahead of "proper" miner's share B, which is P's child. As a result, A will have priority over B even if B is found earlier!
Should I report a bug on GitHub?
One of principal rules of mining, as I understand it, is "A miner who breaks a rule must be punished." For example, if you mine not on the latest block but its parent, or mine invalid blocks, your work will be orphaned by the rest of network.
Now consider the rule defined by those 3 lines I was talking about. It states "If a share (S) is based on stale block, mine on its parent (P)." (That's what "Punishing for block-stale / Jumping to ..." log message is about.) If a miner (either intentionally or because of slow bitcoind) disrespects this rule, not only he loses nothing, but may also eventually profit from it! Really, his share A (a child of block-stale share S, which is punished by the rest of the network) is 1 share ahead of "proper" miner's share B, which is P's child. As a result, A will have priority over B even if B is found earlier!
Should I report a bug on GitHub?
I think it should be reported, at least to start the discussion
This has been already discussed here. Current share "punishing" mechanism is broken. I hope forrestv will eventually notice and fix it. Until then, I just comment out those three lines which "jump" to previous share and I don't really care if anyone suffers from it.
Broken how? There's not even a bug on the bugtracker related to share punishing.
Devs don't dig in forum posts for bug descriptions unless they happen to be involved in it...
Last time I found a bug with zvs, I created an entry in the bugtracker with detailed explanations and forrestv designed a solution in a couple of weeks (which is now in place).
Sorry for misunderstanding here. When saying "broken", I mean not broken code but wrong algorithm/strategy.
One of principal rules of mining, as I understand it, is "A miner who breaks a rule must be punished." For example, if you mine not on the latest block but its parent, or mine invalid blocks, your work will be orphaned by the rest of network.
Now consider the rule defined by those 3 lines I was talking about. It states "If a share (S) is based on stale block, mine on its parent (P)." (That's what "Punishing for block-stale / Jumping to ..." log message is about.) If a miner (either intentionally or because of slow bitcoind) disrespects this rule, not only he loses nothing, but may also eventually profit from it! Really, his share A (a child of block-stale share S, which is punished by the rest of the network) is 1 share ahead of "proper" miner's share B, which is P's child. As a result, A will have priority over B even if B is found earlier!
Should I report a bug on GitHub?
This has been already discussed here. Current share "punishing" mechanism is broken. I hope forrestv will eventually notice and fix it. Until then, I just comment out those three lines which "jump" to previous share and I don't really care if anyone suffers from it.
Broken how? There's not even a bug on the bugtracker related to share punishing.
Devs don't dig in forum posts for bug descriptions unless they happen to be involved in it...
Last time I found a bug with zvs, I created an entry in the bugtracker with detailed explanations and forrestv designed a solution in a couple of weeks (which is now in place).
So, being that for the next 2 weeks I have a really bad internet connection; I should set my pseudo difficulty share to a higher amount so that it's not killing my internet speeds?
Also, thank you for answering my first question!
A higher share difficulty won't hurt anything; it'll just make your graphs go all over the place. I personally use difficulty 8 on my Jalapeno just to save some bandwidth. If you're mining on a node on your local network, however, the only thing you're really saving is maybe a tiny amount of CPU power.Also, thank you for answering my first question!
I'm mining on someone else's p2pool node, which is relatively close, 1 state away. But I have a pathetic 2Mbps and 1Mbps up until next week or two tops when I get the 75Mbps and 20Mbps up.
At that point, my RAID-1 2x2TB HDD, PCI-e 16x dual network card, 32GB of DDR3 memory and my 3.66GHz AMD Hex Core will be hosting it's own P2Pool node. CAN'T WAIT!
I might charge a small fee, but then if funds allow I'll be placing it within a data center in the Midwest as it doesn't seem to have a lot of nodes in this general region with a good, quality connection.
So, being that for the next 2 weeks I have a really bad internet connection; I should set my pseudo difficulty share to a higher amount so that it's not killing my internet speeds?
Also, thank you for answering my first question!
A higher share difficulty won't hurt anything; it'll just make your graphs go all over the place. I personally use difficulty 8 on my Jalapeno just to save some bandwidth. If you're mining on a node on your local network, however, the only thing you're really saving is maybe a tiny amount of CPU power. Also, thank you for answering my first question!
I have a question in regards to the pseudo difficulty set by the client.
Being that the share difficulty is 3x higher than it was before and I'm mining between 5,500 MH/s and 6,000 MH/s with my Jalapeno and having a poor connection at the current moment; would increasing the difficulty factor to say 4-8:
A.) Find shares more quickly?
B.) Raise my income vs running it at the default '1' difficulty
Thanks!
Being that the share difficulty is 3x higher than it was before and I'm mining between 5,500 MH/s and 6,000 MH/s with my Jalapeno and having a poor connection at the current moment; would increasing the difficulty factor to say 4-8:
A.) Find shares more quickly?
B.) Raise my income vs running it at the default '1' difficulty
Thanks!
Anyone happen to know? /bump
So, being that for the next 2 weeks I have a really bad internet connection; I should set my pseudo difficulty share to a higher amount so that it's not killing my internet speeds?
Also, thank you for answering my first question!
I have a question in regards to the pseudo difficulty set by the client.
Being that the share difficulty is 3x higher than it was before and I'm mining between 5,500 MH/s and 6,000 MH/s with my Jalapeno and having a poor connection at the current moment; would increasing the difficulty factor to say 4-8:
A.) Find shares more quickly?
B.) Raise my income vs running it at the default '1' difficulty
Thanks!
Being that the share difficulty is 3x higher than it was before and I'm mining between 5,500 MH/s and 6,000 MH/s with my Jalapeno and having a poor connection at the current moment; would increasing the difficulty factor to say 4-8:
A.) Find shares more quickly?
B.) Raise my income vs running it at the default '1' difficulty
Thanks!
Anyone happen to know? /bump
I have a question in regards to the pseudo difficulty set by the client.
Being that the share difficulty is 3x higher than it was before and I'm mining between 5,500 MH/s and 6,000 MH/s with my Jalapeno and having a poor connection at the current moment; would increasing the difficulty factor to say 4-8:
A.) Find shares more quickly?
B.) Raise my income vs running it at the default '1' difficulty
Thanks!
Being that the share difficulty is 3x higher than it was before and I'm mining between 5,500 MH/s and 6,000 MH/s with my Jalapeno and having a poor connection at the current moment; would increasing the difficulty factor to say 4-8:
A.) Find shares more quickly?
B.) Raise my income vs running it at the default '1' difficulty
Thanks!
Anyone happen to know? /bump
This has been already discussed here. Current share "punishing" mechanism is broken. I hope forrestv will eventually notice and fix it. Until then, I just comment out those three lines which "jump" to previous share and I don't really care if anyone suffers from it.
zvs, you are complaining about a « problem » on an old version of p2pool running on a fork with an efficiency that would make even me jealous (my efficiency on the new code is between 102 and 107%).
AFAIK your efficiency was always stellar in your reports, even if what you describe happened in the most recent p2pool version what would be the problem and why should someone spend some time on this?
AFAIK your efficiency was always stellar in your reports, even if what you describe happened in the most recent p2pool version what would be the problem and why should someone spend some time on this?
I've actually watched it as it occurred a couple of times now.
It places these late shares into my 'headers' section. If I get a share during this time, then it builds off the share before all these 'punished' ones started appearing in my headers section.... the problem is, by the time I build off share x, punished share y already has one or two other shares below it.... but as it is never put in my share chain, I don't build off of it
re just happened like 3 minutes ago:
2013-07-19 09:03:51.919905 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:03:51.924370 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:03:56.605840 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:03:56.901231 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:03:56.906108 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:04:00.185645 Peer sent entire transaction 2a4f06e011b54f5b6486c0c2da291715f7ef7230ce135af7a4181f0f9c560fc6 that was already received
2013-07-19 09:04:01.902012 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:04:01.906526 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:04:03.161645 GOT SHARE! General.Butt.Naked ef3efdbb prev d7be892d age 21.54s
not a chance,
instead, this happened
the share that is shown as building off of d7be892d is @ 09:03:39 (209 transactions), prev block 000000000000003aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6
my log:
2013-07-19 14:03:39 received block 000000000000005bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19 from xxx
the next share is at 09:04:10, but since I rejected the share @ 09:03:39, my share is automatically orphaned, once this other person with slower bitcoind builds off of it
It places these late shares into my 'headers' section. If I get a share during this time, then it builds off the share before all these 'punished' ones started appearing in my headers section.... the problem is, by the time I build off share x, punished share y already has one or two other shares below it.... but as it is never put in my share chain, I don't build off of it
re just happened like 3 minutes ago:
2013-07-19 09:03:51.919905 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:03:51.924370 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:03:56.605840 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:03:56.901231 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:03:56.906108 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:04:00.185645 Peer sent entire transaction 2a4f06e011b54f5b6486c0c2da291715f7ef7230ce135af7a4181f0f9c560fc6 that was already received
2013-07-19 09:04:01.902012 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:04:01.906526 Punishing share for 'Block-stale detected! 3aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6 < 5bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19'! Jumping from 8e33f452 to d7be892d!
2013-07-19 09:04:03.161645 GOT SHARE! General.Butt.Naked ef3efdbb prev d7be892d age 21.54s
not a chance,
instead, this happened
the share that is shown as building off of d7be892d is @ 09:03:39 (209 transactions), prev block 000000000000003aecb7f4a40238707f6223f6a12160a1d71fd97e98b09facf6
my log:
2013-07-19 14:03:39 received block 000000000000005bc7ac3a792bdb3167e24e2a93201cee07b1271724bcc38c19 from xxx
the next share is at 09:04:10, but since I rejected the share @ 09:03:39, my share is automatically orphaned, once this other person with slower bitcoind builds off of it
was anything ever done to fix this problem:
2013-07-19 03:34:41.882322 Punishing share for 'Block-stale detected! 57be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48 < 7001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813'! Jumping from 360c92d3 to ee79e02a!
2013-07-19 03:34:41.916924 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.109710 BTC including 163 transactions
2013-07-19 03:34:41.976691 Punishing share for 'Block-stale detected! 57be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48 < 7001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813'! Jumping from 360c92d3 to ee79e02a!
2013-07-19 03:34:41.981318 Punishing share for 'Block-stale detected! 57be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48 < 7001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813'! Jumping from 360c92d3 to ee79e02a!
2013-07-19 03:34:41.987124 P2Pool: 17353 shares in chain (9116 verified/17358 total) Peers: 23 (0 incoming)
2013-07-19 03:34:41.987259 Local: 2906MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-5%) Expected time to share: 1.8 minutes
2013-07-19 03:34:41.987383 Shares: 30 (0 orphan, 0 dead) Stale rate: ~0.0% (0-12%) Efficiency: ~121.9% (108-122%) Current payout: 0.1302 BTC
2013-07-19 03:34:41.987427 Pool: 36873MH/s Stale rate: 18.0% Expected time to block: 35.3 days
2013-07-19 03:34:42.061748 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000500 BTC including 1 transactions
2013-07-19 03:34:42.533493 Peer sent entire transaction 4283fa32d281ec5a011b64422b54d5768e5e4121fb2d1a312075ac8dc5094d8d that was already received
2013-07-19 03:34:42.668619 Peer sent entire transaction 6c943279b2c9f112d46eeab4fc6ee816c8ae67d10af5b09adf5af2c341b4ea58 that was already received
2013-07-19 03:34:44.990536 P2Pool: 17353 shares in chain (9116 verified/17358 total) Peers: 23 (0 incoming)
2013-07-19 03:34:44.990685 Local: 2877MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-6%) Expected time to share: 1.8 minutes
2013-07-19 03:34:44.990739 Shares: 30 (0 orphan, 0 dead) Stale rate: ~0.0% (0-12%) Efficiency: ~121.9% (108-122%) Current payout: 0.1302 BTC
2013-07-19 03:34:44.990867 Pool: 36873MH/s Stale rate: 18.0% Expected time to block: 35.3 days
2013-07-19 03:34:46.900987 Punishing share for 'Block-stale detected! 57be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48 < 7001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813'! Jumping from 360c92d3 to ee79e02a!
2013-07-19 03:34:46.906012 Punishing share for 'Block-stale detected! 57be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48 < 7001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813'! Jumping from 360c92d3 to ee79e02a!
2013-07-19 03:34:47.431079 GOT SHARE! General.Butt.Naked c7db9f45 prev ee79e02a age 5.37s
2013-07-19 03:34:47.463691 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000500 BTC including 1 transactions
2013-07-19 03:34:47.993996 P2Pool: 17354 shares in chain (9117 verified/17359 total) Peers: 23 (0 incoming)
2013-07-19 03:34:47.994154 Local: 2934MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-5%) Expected time to share: 1.8 minutes
2013-07-19 03:34:47.994263 Shares: 31 (0 orphan, 0 dead) Stale rate: ~0.0% (0-12%) Efficiency: ~121.9% (108-122%) Current payout: 0.1345 BTC
2013-07-19 03:34:47.994316 Pool: 37036MH/s Stale rate: 18.0% Expected time to block: 35.1 days
2013-07-19 03:34:50.997024 P2Pool: 17354 shares in chain (9117 verified/17359 total) Peers: 23 (0 incoming)
2013-07-19 03:34:50.997169 Local: 2963MH/s in last 10.0 minutes Local dead on arrival: ~1.9% (0-5%) Expected time to share: 1.8 minutes
2013-07-19 03:34:50.997211 Shares: 31 (0 orphan, 0 dead) Stale rate: ~0.0% (0-12%) Efficiency: ~121.9% (108-122%) Current payout: 0.1345 BTC
2013-07-19 03:34:50.997256 Pool: 37036MH/s Stale rate: 18.0% Expected time to block: 35.1 days
2013-07-19 03:34:53.563429 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000500 BTC including 1 transactions
2013-07-19 03:34:54.000214 P2Pool: 17353 shares in chain (9117 verified/17357 total) Peers: 23 (0 incoming)
2013-07-19 03:34:54.000341 Local: 2977MH/s in last 10.0 minutes Local dead on arrival: ~1.9% (0-5%) Expected time to share: 1.8 minutes
2013-07-19 03:34:54.000432 Shares: 31 (1 orphan, 0 dead) Stale rate: ~3.2% (0-17%) Efficiency: ~118.3% (102-122%) Current payout: 0.1302 BTC
2013-07-19 03:34:54.000484 Pool: 37249MH/s Stale rate: 18.2% Expected time to block: 34.9 days
...
i just haven't seen a case of it recently, since i've sold nearly all my mining stuff and i don't get shares frequently enough on 'NewShare'... I'm pretty sure I have all the commits in that v11?
oh, here is the share that my node punished, but was built on by another node, after the new block hit the network (note the # of transactions):
P2Pool > Share 360c92d3
Parent: ee79e02a
Children: 6b5c7b6f
Time first seen: Fri Jul 19 2013 03:34:40 GMT-0500 (Central Daylight Time) (1374222880.676804)
Hash: 00000000030c538de4ecbfe7436a95c181324f3b175999efa9b12c2f360c92d3
Previous block: 0000000000000057be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48
Transaction count: 218
here's mine:
P2Pool > Share c7db9f45
Parent: ee79e02a
Time first seen: Fri Jul 19 2013 03:34:47 GMT-0500 (Central Daylight Time) (1374222887.431045)
Hash: 00000000028742e35d4990ad89fafd690a5f9acf51839822fb9e77a3c7db9f45
Previous block: 000000000000007001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813
Transaction count: 1
here is the share that orphaned mine:
P2Pool > Share 6b5c7b6f
Parent: 360c92d3
Children: d21c7b73
Time first seen: Fri Jul 19 2013 03:34:53 GMT-0500 (Central Daylight Time) (1374222893.53492)
Hash: 000000000233a54352f42f7128b3754ea29ef46f827aa86c058b07f36b5c7b6f
Previous block: 000000000000007001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813
Transaction count: 0
----------------------------
Share 360c92d3 was invalid, if it had been a block, it would have been an orphaned block. Yet share 6b5c7b6f built off of it anyway.
That's why it seems to me like a slow bitcoind is actually beneficial to your p2pool payout... (but if you were to find a block, it'd significantly increase the chances of it being orphaned)
2013-07-19 08:34:40 received block 000000000000007001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813 from xxxx
(last ed)
remember the couple of times I had a share say DOA, but it became 'undead'? it stated 'punishing share X, Jumping from XYZ to ABC', but my share didn't build off of ABC, it built off of something else.
***** (err, nm, another ed)
2013-07-19 04:15:06.480554 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.057000 BTC including 68 transactions
2013-07-19 04:15:07.288865 P2Pool: 17341 shares in chain (9370 verified/17345 total) Peers: 23 (0 incoming)
2013-07-19 04:15:07.289069 Local: 2562MH/s in last 10.0 minutes Local dead on arrival: ~2.2% (0-6%) Expected time to share: 2.1 minutes
2013-07-19 04:15:07.289186 Shares: 43 (1 orphan, 0 dead) Stale rate: ~2.3% (0-13%) Efficiency: ~120.2% (108-123%) Current payout: 0.1830 BTC
2013-07-19 04:15:07.289235 Pool: 39596MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:09.459348 GOT SHARE! President Goodluck Jonathan 8626472f prev 5be29d92 age 2.98s
2013-07-19 04:15:09.509994 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.057000 BTC including 68 transactions
2013-07-19 04:15:10.291544 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:10.291688 Local: 2548MH/s in last 10.0 minutes Local dead on arrival: ~2.2% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:10.291746 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1874 BTC
2013-07-19 04:15:10.291815 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:10.840606 Skipping from block bac4b4efff835cfd24edd7db7b3075ec6658de2851599a8a2 to block 6627017acb7c38e75a2f5940a91e3a49c2eb8a48b5d5850ff0!
2013-07-19 04:15:10.848847 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000000 BTC including 0 transactions
2013-07-19 04:15:11.673938 Peer sent entire transaction 87c425a112650a3e432ef2b3cdfdd6f4267783f961d59e311ac07a19fc153be1 that was already received
2013-07-19 04:15:11.891762 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.010500 BTC including 19 transactions
2013-07-19 04:15:13.295846 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:13.296010 Local: 2548MH/s in last 10.0 minutes Local dead on arrival: ~2.2% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:13.296102 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:13.296148 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:16.299090 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:16.299208 Local: 2534MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:16.299252 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:16.299323 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:18.647097 Skipping from block 6627017acb7c38e75a2f5940a91e3a49c2eb8a48b5d5850ff0 to block c5384208fef2f79a67756939a1b74483b5ae172034604f0a1!
2013-07-19 04:15:18.652127 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000000 BTC including 0 transactions
2013-07-19 04:15:19.007902 Peer sent entire transaction c07be95e6515be4313bd3d45a701a7b0c80631656fa315f2ebd590885b860472 that was already received
2013-07-19 04:15:19.126141 Peer sent entire transaction d8852a96fb0baccf20ab63a4ef8b5279cdf8936b91532ee79a378e33b64397b3 that was already received
2013-07-19 04:15:19.149887 Peer sent entire transaction c07be95e6515be4313bd3d45a701a7b0c80631656fa315f2ebd590885b860472 that was already received
2013-07-19 04:15:19.302421 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:19.302596 Local: 2519MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:19.302641 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:19.302698 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:20.244176 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.001500 BTC including 3 transactions
2013-07-19 04:15:22.306876 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:22.307012 Local: 2505MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:22.307071 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:22.307121 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:25.309867 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:25.309991 Local: 2491MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:25.310035 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:25.310096 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:28.313789 P2Pool: 17342 shares in chain (9372 verified/17347 total) Peers: 23 (0 incoming)
2013-07-19 04:15:28.313892 Local: 2448MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:28.313981 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:28.314028 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:31.317044 P2Pool: 17342 shares in chain (9372 verified/17347 total) Peers: 23 (0 incoming)
2013-07-19 04:15:31.317190 Local: 2462MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:31.317254 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:31.317398 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:31.708525 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.001500 BTC including 3 transactions
2013-07-19 04:15:34.084637 Peer sent entire transaction f0c20825cf24ce2de6a99b4bcab7a474f9c059fa3b85a4941c338dba8712b1f1 that was already received
2013-07-19 04:15:34.321196 P2Pool: 17309 shares in chain (9372 verified/17313 total) Peers: 23 (0 incoming)
2013-07-19 04:15:34.321338 Local: 2448MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.3 minutes
2013-07-19 04:15:34.321384 Shares: 44 (2 orphan, 0 dead) Stale rate: ~4.5% (1-16%) Efficiency: ~117.5% (104-122%) Current payout: 0.1826 BTC
2013-07-19 04:15:34.321452 Pool: 39604MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 09:15:10 received block 000000000000006627017acb7c38e75a2f5940a91e3a49c2eb8a48b5d5850ff0 from xxx
2013-07-19 09:15:17 received block 000000000000000c5384208fef2f79a67756939a1b74483b5ae172034604f0a1 from xxx
2013-07-19 09:15:46 received block 00000000000000363d2c8c884d121023477f034b59aa9adbfa70a37f757c7c80 from xxx
i'm positive that's related in some fashion (btw the bitcoin log is in utc, the p2pool log is local time)
***********************aha
2013-07-19 06:12:05.527339 Skipping from block 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db to block 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6!
2013-07-19 06:12:05.531629 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000000 BTC including 0 transactions
2013-07-19 06:12:05.821742 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:05.839350 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000000 BTC including 0 transactions
2013-07-19 06:12:05.871325 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.012700 BTC including 12 transactions
2013-07-19 06:12:06.802035 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:06.901303 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:06.906323 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:11.145712 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:11.145847 Local: 2770MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.8 minutes
2013-07-19 06:12:11.145905 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3276 BTC
2013-07-19 06:12:11.146008 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:11.925786 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:11.931408 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:14.149381 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:14.149512 Local: 2784MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.8 minutes
2013-07-19 06:12:14.149556 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3276 BTC
2013-07-19 06:12:14.149778 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:16.901703 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:16.906788 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:20.155998 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:20.156147 Local: 2820MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.8 minutes
2013-07-19 06:12:20.156191 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3276 BTC
2013-07-19 06:12:20.156253 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:20.945753 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:21.846793 Peer sent entire transaction a7f4b4bd7a2427f80d72bb89430d6d16ae679c834447a30bc387814fa2e93009 that was already received
2013-07-19 06:12:21.903446 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:21.908569 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:23.159719 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:23.159876 Local: 2834MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.8 minutes
2013-07-19 06:12:23.159920 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3276 BTC
2013-07-19 06:12:23.159982 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:26.901461 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:26.906588 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:31.924158 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:31.929291 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:35.171838 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:35.172043 Local: 2870MH/s in last 10.0 minutes Local dead on arrival: ~4.3% (2-9%) Expected time to share: 1.7 minutes
2013-07-19 06:12:35.172605 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3276 BTC
2013-07-19 06:12:35.172731 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:36.030837 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:36.901392 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:36.906492 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:41.179238 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:41.179376 Local: 2849MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.8 minutes
2013-07-19 06:12:41.179421 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3277 BTC
2013-07-19 06:12:41.179484 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:41.923279 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:41.928323 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:44.183066 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:44.183224 Local: 2877MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.7 minutes
2013-07-19 06:12:44.183304 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3277 BTC
2013-07-19 06:12:44.183408 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:46.901433 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:46.906483 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:47.186886 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:47.187011 Local: 2927MH/s in last 10.0 minutes Local dead on arrival: ~4.3% (2-9%) Expected time to share: 1.7 minutes
2013-07-19 06:12:47.187055 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3277 BTC
2013-07-19 06:12:47.187102 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:50.250939 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from ee9923d6 to 0a5d2cdc!
2013-07-19 06:12:50.270487 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.021400 BTC including 24 transactions
2013-07-19 06:12:51.123081 GOT SHARE! General.Butt.Naked d038d3a6 prev 0a5d2cdc age 0.85s
2013-07-19 06:12:51.164553 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.021400 BTC including 24 transactions
2013-07-19 06:12:53.193310 P2Pool: 17296 shares in chain (10058 verified/17302 total) Peers: 23 (0 incoming)
2013-07-19 06:12:53.193454 Local: 2913MH/s in last 10.0 minutes Local dead on arrival: ~4.3% (2-9%) Expected time to share: 1.7 minutes
2013-07-19 06:12:53.193554 Shares: 82 (4 orphan, 1 dead) Stale rate: ~6.1% (2-14%) Efficiency: ~124.4% (114-130%) Current payout: 0.3320 BTC
2013-07-19 06:12:53.193622 Pool: 43101MH/s Stale rate: 24.5% Expected time to block: 30.2 days
2013-07-19 06:13:04.636960 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.026400 BTC including 29 transactions
2013-07-19 06:13:05.205195 P2Pool: 17297 shares in chain (10059 verified/17303 total) Peers: 23 (0 incoming)
2013-07-19 06:13:05.205341 Local: 2899MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.7 minutes
2013-07-19 06:13:05.205436 Shares: 82 (5 orphan, 1 dead) Stale rate: ~7.3% (3-16%) Efficiency: ~122.3% (112-128%) Current payout: 0.3277 BTC
2013-07-19 06:13:05.205483 Pool: 42881MH/s Stale rate: 24.2% Expected time to block: 30.3 days
... so I'm guessing I must have built on some super old share, since I punished some godawful amount of other ones.... so it had no chance to not be orphaned... btw, wtf changing the share it's jumping to as well
I guess w/ 30s this won't occur as much... that makes 3 out of 5 orphans, possibly 4 out of 5 if you count the one up above (not sure about that). same 3/5ths or so as before. if pool hash rate was unchanged, presumably with 30s shares, it'd only be about 1/5th of the orphans
2013-07-19 03:34:41.882322 Punishing share for 'Block-stale detected! 57be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48 < 7001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813'! Jumping from 360c92d3 to ee79e02a!
2013-07-19 03:34:41.916924 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.109710 BTC including 163 transactions
2013-07-19 03:34:41.976691 Punishing share for 'Block-stale detected! 57be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48 < 7001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813'! Jumping from 360c92d3 to ee79e02a!
2013-07-19 03:34:41.981318 Punishing share for 'Block-stale detected! 57be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48 < 7001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813'! Jumping from 360c92d3 to ee79e02a!
2013-07-19 03:34:41.987124 P2Pool: 17353 shares in chain (9116 verified/17358 total) Peers: 23 (0 incoming)
2013-07-19 03:34:41.987259 Local: 2906MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-5%) Expected time to share: 1.8 minutes
2013-07-19 03:34:41.987383 Shares: 30 (0 orphan, 0 dead) Stale rate: ~0.0% (0-12%) Efficiency: ~121.9% (108-122%) Current payout: 0.1302 BTC
2013-07-19 03:34:41.987427 Pool: 36873MH/s Stale rate: 18.0% Expected time to block: 35.3 days
2013-07-19 03:34:42.061748 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000500 BTC including 1 transactions
2013-07-19 03:34:42.533493 Peer sent entire transaction 4283fa32d281ec5a011b64422b54d5768e5e4121fb2d1a312075ac8dc5094d8d that was already received
2013-07-19 03:34:42.668619 Peer sent entire transaction 6c943279b2c9f112d46eeab4fc6ee816c8ae67d10af5b09adf5af2c341b4ea58 that was already received
2013-07-19 03:34:44.990536 P2Pool: 17353 shares in chain (9116 verified/17358 total) Peers: 23 (0 incoming)
2013-07-19 03:34:44.990685 Local: 2877MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-6%) Expected time to share: 1.8 minutes
2013-07-19 03:34:44.990739 Shares: 30 (0 orphan, 0 dead) Stale rate: ~0.0% (0-12%) Efficiency: ~121.9% (108-122%) Current payout: 0.1302 BTC
2013-07-19 03:34:44.990867 Pool: 36873MH/s Stale rate: 18.0% Expected time to block: 35.3 days
2013-07-19 03:34:46.900987 Punishing share for 'Block-stale detected! 57be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48 < 7001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813'! Jumping from 360c92d3 to ee79e02a!
2013-07-19 03:34:46.906012 Punishing share for 'Block-stale detected! 57be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48 < 7001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813'! Jumping from 360c92d3 to ee79e02a!
2013-07-19 03:34:47.431079 GOT SHARE! General.Butt.Naked c7db9f45 prev ee79e02a age 5.37s
2013-07-19 03:34:47.463691 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000500 BTC including 1 transactions
2013-07-19 03:34:47.993996 P2Pool: 17354 shares in chain (9117 verified/17359 total) Peers: 23 (0 incoming)
2013-07-19 03:34:47.994154 Local: 2934MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-5%) Expected time to share: 1.8 minutes
2013-07-19 03:34:47.994263 Shares: 31 (0 orphan, 0 dead) Stale rate: ~0.0% (0-12%) Efficiency: ~121.9% (108-122%) Current payout: 0.1345 BTC
2013-07-19 03:34:47.994316 Pool: 37036MH/s Stale rate: 18.0% Expected time to block: 35.1 days
2013-07-19 03:34:50.997024 P2Pool: 17354 shares in chain (9117 verified/17359 total) Peers: 23 (0 incoming)
2013-07-19 03:34:50.997169 Local: 2963MH/s in last 10.0 minutes Local dead on arrival: ~1.9% (0-5%) Expected time to share: 1.8 minutes
2013-07-19 03:34:50.997211 Shares: 31 (0 orphan, 0 dead) Stale rate: ~0.0% (0-12%) Efficiency: ~121.9% (108-122%) Current payout: 0.1345 BTC
2013-07-19 03:34:50.997256 Pool: 37036MH/s Stale rate: 18.0% Expected time to block: 35.1 days
2013-07-19 03:34:53.563429 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000500 BTC including 1 transactions
2013-07-19 03:34:54.000214 P2Pool: 17353 shares in chain (9117 verified/17357 total) Peers: 23 (0 incoming)
2013-07-19 03:34:54.000341 Local: 2977MH/s in last 10.0 minutes Local dead on arrival: ~1.9% (0-5%) Expected time to share: 1.8 minutes
2013-07-19 03:34:54.000432 Shares: 31 (1 orphan, 0 dead) Stale rate: ~3.2% (0-17%) Efficiency: ~118.3% (102-122%) Current payout: 0.1302 BTC
2013-07-19 03:34:54.000484 Pool: 37249MH/s Stale rate: 18.2% Expected time to block: 34.9 days
...
i just haven't seen a case of it recently, since i've sold nearly all my mining stuff and i don't get shares frequently enough on 'NewShare'... I'm pretty sure I have all the commits in that v11?
oh, here is the share that my node punished, but was built on by another node, after the new block hit the network (note the # of transactions):
P2Pool > Share 360c92d3
Parent: ee79e02a
Children: 6b5c7b6f
Time first seen: Fri Jul 19 2013 03:34:40 GMT-0500 (Central Daylight Time) (1374222880.676804)
Hash: 00000000030c538de4ecbfe7436a95c181324f3b175999efa9b12c2f360c92d3
Previous block: 0000000000000057be3f5b065b99eb28f8cdbac6b8d6d648e02da1526285ba48
Transaction count: 218
here's mine:
P2Pool > Share c7db9f45
Parent: ee79e02a
Time first seen: Fri Jul 19 2013 03:34:47 GMT-0500 (Central Daylight Time) (1374222887.431045)
Hash: 00000000028742e35d4990ad89fafd690a5f9acf51839822fb9e77a3c7db9f45
Previous block: 000000000000007001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813
Transaction count: 1
here is the share that orphaned mine:
P2Pool > Share 6b5c7b6f
Parent: 360c92d3
Children: d21c7b73
Time first seen: Fri Jul 19 2013 03:34:53 GMT-0500 (Central Daylight Time) (1374222893.53492)
Hash: 000000000233a54352f42f7128b3754ea29ef46f827aa86c058b07f36b5c7b6f
Previous block: 000000000000007001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813
Transaction count: 0
----------------------------
Share 360c92d3 was invalid, if it had been a block, it would have been an orphaned block. Yet share 6b5c7b6f built off of it anyway.
That's why it seems to me like a slow bitcoind is actually beneficial to your p2pool payout... (but if you were to find a block, it'd significantly increase the chances of it being orphaned)
2013-07-19 08:34:40 received block 000000000000007001ad6e6314607c256c0d40ff802e0854978ae76bd5f89813 from xxxx
(last ed)
remember the couple of times I had a share say DOA, but it became 'undead'? it stated 'punishing share X, Jumping from XYZ to ABC', but my share didn't build off of ABC, it built off of something else.
***** (err, nm, another ed)
2013-07-19 04:15:06.480554 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.057000 BTC including 68 transactions
2013-07-19 04:15:07.288865 P2Pool: 17341 shares in chain (9370 verified/17345 total) Peers: 23 (0 incoming)
2013-07-19 04:15:07.289069 Local: 2562MH/s in last 10.0 minutes Local dead on arrival: ~2.2% (0-6%) Expected time to share: 2.1 minutes
2013-07-19 04:15:07.289186 Shares: 43 (1 orphan, 0 dead) Stale rate: ~2.3% (0-13%) Efficiency: ~120.2% (108-123%) Current payout: 0.1830 BTC
2013-07-19 04:15:07.289235 Pool: 39596MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:09.459348 GOT SHARE! President Goodluck Jonathan 8626472f prev 5be29d92 age 2.98s
2013-07-19 04:15:09.509994 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.057000 BTC including 68 transactions
2013-07-19 04:15:10.291544 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:10.291688 Local: 2548MH/s in last 10.0 minutes Local dead on arrival: ~2.2% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:10.291746 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1874 BTC
2013-07-19 04:15:10.291815 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:10.840606 Skipping from block bac4b4efff835cfd24edd7db7b3075ec6658de2851599a8a2 to block 6627017acb7c38e75a2f5940a91e3a49c2eb8a48b5d5850ff0!
2013-07-19 04:15:10.848847 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000000 BTC including 0 transactions
2013-07-19 04:15:11.673938 Peer sent entire transaction 87c425a112650a3e432ef2b3cdfdd6f4267783f961d59e311ac07a19fc153be1 that was already received
2013-07-19 04:15:11.891762 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.010500 BTC including 19 transactions
2013-07-19 04:15:13.295846 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:13.296010 Local: 2548MH/s in last 10.0 minutes Local dead on arrival: ~2.2% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:13.296102 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:13.296148 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:16.299090 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:16.299208 Local: 2534MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:16.299252 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:16.299323 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:18.647097 Skipping from block 6627017acb7c38e75a2f5940a91e3a49c2eb8a48b5d5850ff0 to block c5384208fef2f79a67756939a1b74483b5ae172034604f0a1!
2013-07-19 04:15:18.652127 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000000 BTC including 0 transactions
2013-07-19 04:15:19.007902 Peer sent entire transaction c07be95e6515be4313bd3d45a701a7b0c80631656fa315f2ebd590885b860472 that was already received
2013-07-19 04:15:19.126141 Peer sent entire transaction d8852a96fb0baccf20ab63a4ef8b5279cdf8936b91532ee79a378e33b64397b3 that was already received
2013-07-19 04:15:19.149887 Peer sent entire transaction c07be95e6515be4313bd3d45a701a7b0c80631656fa315f2ebd590885b860472 that was already received
2013-07-19 04:15:19.302421 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:19.302596 Local: 2519MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:19.302641 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:19.302698 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:20.244176 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.001500 BTC including 3 transactions
2013-07-19 04:15:22.306876 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:22.307012 Local: 2505MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:22.307071 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:22.307121 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:25.309867 P2Pool: 17342 shares in chain (9371 verified/17346 total) Peers: 23 (0 incoming)
2013-07-19 04:15:25.309991 Local: 2491MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:25.310035 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:25.310096 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:28.313789 P2Pool: 17342 shares in chain (9372 verified/17347 total) Peers: 23 (0 incoming)
2013-07-19 04:15:28.313892 Local: 2448MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:28.313981 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:28.314028 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:31.317044 P2Pool: 17342 shares in chain (9372 verified/17347 total) Peers: 23 (0 incoming)
2013-07-19 04:15:31.317190 Local: 2462MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.2 minutes
2013-07-19 04:15:31.317254 Shares: 44 (1 orphan, 0 dead) Stale rate: ~2.3% (0-12%) Efficiency: ~120.3% (108-123%) Current payout: 0.1870 BTC
2013-07-19 04:15:31.317398 Pool: 39634MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 04:15:31.708525 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.001500 BTC including 3 transactions
2013-07-19 04:15:34.084637 Peer sent entire transaction f0c20825cf24ce2de6a99b4bcab7a474f9c059fa3b85a4941c338dba8712b1f1 that was already received
2013-07-19 04:15:34.321196 P2Pool: 17309 shares in chain (9372 verified/17313 total) Peers: 23 (0 incoming)
2013-07-19 04:15:34.321338 Local: 2448MH/s in last 10.0 minutes Local dead on arrival: ~2.3% (0-6%) Expected time to share: 2.3 minutes
2013-07-19 04:15:34.321384 Shares: 44 (2 orphan, 0 dead) Stale rate: ~4.5% (1-16%) Efficiency: ~117.5% (104-122%) Current payout: 0.1826 BTC
2013-07-19 04:15:34.321452 Pool: 39604MH/s Stale rate: 18.7% Expected time to block: 32.8 days
2013-07-19 09:15:10 received block 000000000000006627017acb7c38e75a2f5940a91e3a49c2eb8a48b5d5850ff0 from xxx
2013-07-19 09:15:17 received block 000000000000000c5384208fef2f79a67756939a1b74483b5ae172034604f0a1 from xxx
2013-07-19 09:15:46 received block 00000000000000363d2c8c884d121023477f034b59aa9adbfa70a37f757c7c80 from xxx
i'm positive that's related in some fashion (btw the bitcoin log is in utc, the p2pool log is local time)
***********************aha
2013-07-19 06:12:05.527339 Skipping from block 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db to block 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6!
2013-07-19 06:12:05.531629 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000000 BTC including 0 transactions
2013-07-19 06:12:05.821742 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:05.839350 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.000000 BTC including 0 transactions
2013-07-19 06:12:05.871325 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.012700 BTC including 12 transactions
2013-07-19 06:12:06.802035 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:06.901303 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:06.906323 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:11.145712 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:11.145847 Local: 2770MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.8 minutes
2013-07-19 06:12:11.145905 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3276 BTC
2013-07-19 06:12:11.146008 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:11.925786 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:11.931408 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:14.149381 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:14.149512 Local: 2784MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.8 minutes
2013-07-19 06:12:14.149556 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3276 BTC
2013-07-19 06:12:14.149778 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:16.901703 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:16.906788 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:20.155998 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:20.156147 Local: 2820MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.8 minutes
2013-07-19 06:12:20.156191 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3276 BTC
2013-07-19 06:12:20.156253 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:20.945753 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:21.846793 Peer sent entire transaction a7f4b4bd7a2427f80d72bb89430d6d16ae679c834447a30bc387814fa2e93009 that was already received
2013-07-19 06:12:21.903446 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:21.908569 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:23.159719 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:23.159876 Local: 2834MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.8 minutes
2013-07-19 06:12:23.159920 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3276 BTC
2013-07-19 06:12:23.159982 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:26.901461 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:26.906588 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:31.924158 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:31.929291 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:35.171838 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:35.172043 Local: 2870MH/s in last 10.0 minutes Local dead on arrival: ~4.3% (2-9%) Expected time to share: 1.7 minutes
2013-07-19 06:12:35.172605 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3276 BTC
2013-07-19 06:12:35.172731 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:36.030837 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:36.901392 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:36.906492 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:41.179238 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:41.179376 Local: 2849MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.8 minutes
2013-07-19 06:12:41.179421 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3277 BTC
2013-07-19 06:12:41.179484 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:41.923279 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:41.928323 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:44.183066 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:44.183224 Local: 2877MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.7 minutes
2013-07-19 06:12:44.183304 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3277 BTC
2013-07-19 06:12:44.183408 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:46.901433 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:46.906483 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from 0a5d2cdc to 98d51495!
2013-07-19 06:12:47.186886 P2Pool: 17294 shares in chain (10056 verified/17300 total) Peers: 23 (0 incoming)
2013-07-19 06:12:47.187011 Local: 2927MH/s in last 10.0 minutes Local dead on arrival: ~4.3% (2-9%) Expected time to share: 1.7 minutes
2013-07-19 06:12:47.187055 Shares: 81 (4 orphan, 1 dead) Stale rate: ~6.2% (2-14%) Efficiency: ~124.1% (114-129%) Current payout: 0.3277 BTC
2013-07-19 06:12:47.187102 Pool: 43008MH/s Stale rate: 24.4% Expected time to block: 30.2 days
2013-07-19 06:12:50.250939 Punishing share for 'Block-stale detected! 498db794c8dd3e68b1d5f94d51db49739e3dd7891e7315b1db < 39f22c0b821136d9eb42b44c7cb28ed6c8237bccd9b0b13fa6'! Jumping from ee9923d6 to 0a5d2cdc!
2013-07-19 06:12:50.270487 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.021400 BTC including 24 transactions
2013-07-19 06:12:51.123081 GOT SHARE! General.Butt.Naked d038d3a6 prev 0a5d2cdc age 0.85s
2013-07-19 06:12:51.164553 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.021400 BTC including 24 transactions
2013-07-19 06:12:53.193310 P2Pool: 17296 shares in chain (10058 verified/17302 total) Peers: 23 (0 incoming)
2013-07-19 06:12:53.193454 Local: 2913MH/s in last 10.0 minutes Local dead on arrival: ~4.3% (2-9%) Expected time to share: 1.7 minutes
2013-07-19 06:12:53.193554 Shares: 82 (4 orphan, 1 dead) Stale rate: ~6.1% (2-14%) Efficiency: ~124.4% (114-130%) Current payout: 0.3320 BTC
2013-07-19 06:12:53.193622 Pool: 43101MH/s Stale rate: 24.5% Expected time to block: 30.2 days
2013-07-19 06:13:04.636960 New work for worker! Difficulty: 2.000000 Share difficulty: 100.000358 Total block value: 25.026400 BTC including 29 transactions
2013-07-19 06:13:05.205195 P2Pool: 17297 shares in chain (10059 verified/17303 total) Peers: 23 (0 incoming)
2013-07-19 06:13:05.205341 Local: 2899MH/s in last 10.0 minutes Local dead on arrival: ~4.4% (2-9%) Expected time to share: 1.7 minutes
2013-07-19 06:13:05.205436 Shares: 82 (5 orphan, 1 dead) Stale rate: ~7.3% (3-16%) Efficiency: ~122.3% (112-128%) Current payout: 0.3277 BTC
2013-07-19 06:13:05.205483 Pool: 42881MH/s Stale rate: 24.2% Expected time to block: 30.3 days
... so I'm guessing I must have built on some super old share, since I punished some godawful amount of other ones.... so it had no chance to not be orphaned... btw, wtf changing the share it's jumping to as well
I guess w/ 30s this won't occur as much... that makes 3 out of 5 orphans, possibly 4 out of 5 if you count the one up above (not sure about that). same 3/5ths or so as before. if pool hash rate was unchanged, presumably with 30s shares, it'd only be about 1/5th of the orphans
Thanks a lot for the tips.
The problem is cgminer - it just does not like p2pool or the fedora core 17 combination. Switched back to DiabloMiner.
I was using BFGminer some year ago with no problems (dunno now).
The problem is cgminer - it just does not like p2pool or the fedora core 17 combination. Switched back to DiabloMiner.
I was using BFGminer some year ago with no problems (dunno now).
I have a question in regards to the pseudo difficulty set by the client.
Being that the share difficulty is 3x higher than it was before and I'm mining between 5,500 MH/s and 6,000 MH/s with my Jalapeno and having a poor connection at the current moment; would increasing the difficulty factor to say 4-8:
A.) Find shares more quickly?
B.) Raise my income vs running it at the default '1' difficulty
Thanks!
Being that the share difficulty is 3x higher than it was before and I'm mining between 5,500 MH/s and 6,000 MH/s with my Jalapeno and having a poor connection at the current moment; would increasing the difficulty factor to say 4-8:
A.) Find shares more quickly?
B.) Raise my income vs running it at the default '1' difficulty
Thanks!
I believe I saw it somewhere - might be problem with ulimit -n,but I think I increased it to 2048 and it did not help.
Restarting p2pool helps.
Any ideas how to debug the problem or what to do ?
Shall I upgrade fedora (python-twisted-core-12.2.0-2.fc19.x86_64) ?
Thanks a lot for your time !
Restarting p2pool helps.
Any ideas how to debug the problem or what to do ?
Shall I upgrade fedora (python-twisted-core-12.2.0-2.fc19.x86_64) ?
Thanks a lot for your time !
"fc19" is Fedora Core 19, that's really new, I'm unsure why they don't have a higher limit by default. On a modern Linux system, with a lot going on, you should give yourself as many open file descriptors as you can.
I don't use Fedora, but the file should still be in the same place (I hope). Edit the /etc/security/limits.conf file, put this at the bottom, don't forget the stars in the far left column:
Code:
* soft nofile 65536
* hard nofile 65536
Get rid of any other lines in the file that have "nofile" in them. Unfortunately, it seems the maximum is 65536, the system simply won't let you set a higher limit (even though I wanted to).
Then, log out and log back in. You should have a much higher limit now, verify with "ulimit -n" as you said.
Also, in your text you pasted, it says (in the big loud message) your Bitcoin daemon isn't running. Something's seriously wrong on your system. You should always have 3 programs running: bitcoind (or Bitcoin-Qt), p2pool, and bfgminer (or whatever miner you use).
Josh
Code:
# Increase open file limits
sudo sh -c 'echo "* soft nofile 16384" >> /etc/security/limits.conf'
sudo sh -c 'echo "* hard nofile 65536" >> /etc/security/limits.conf'
sudo sh -c 'echo "* soft nproc 4096" >> /etc/security/limits.conf'
sudo sh -c 'echo "* hard nproc 16384" >> /etc/security/limits.conf'
for Fedora it's /etc/security/limits.d/90-nproc.conf
Jump to: