Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 530. (Read 2592017 times)

Damn I'm going to have to leave unless I can make cgminer use only bfl on second instance.

No (see my guide for why).

So jalapeno p2pool yes or no?

Germany node:

2013-06-12 02:30:22 received block 00000000000000d9a40124da12aa3c7b26d7adad47eab9dc5cd95113d345a7b6
2013-06-12 02:30:24 received block 000000000000003eb0df7952601d567ed07a1683793c3aeb1c90fae6b378cfaf

that bitparking one came in late =p

US node:

2013-06-12 02:30:22 received block 000000000000003eb0df7952601d567ed07a1683793c3aeb1c90fae6b378cfaf
2013-06-12 02:30:26 received block 00000000000000d9a40124da12aa3c7b26d7adad47eab9dc5cd95113d345a7b6 from 5.9.24.81:25861
2013-06-12 02:30:27 received block 00000000000000d9a40124da12aa3c7b26d7adad47eab9dc5cd95113d345a7b6 from 127.0.0.1:14265

that p2pool one came in late, and was even sent faster from Germany than from my local p2pool

Yes, there are 2 other contributing factors:

• a node always prefer mining on a share it just produced (this is a gamble which doesn't change the fairness, you either get 2 shares through or none),
• according to the payouts this address controls nearly 10% of the P2Pool hashrate so it can orphan other shares more easily than the common node

The longer chain always win, so this behavior is expected. It shouldn't produce any unbalance though, there are more chances that the rest of the network (90% of the hashrate) will invalidate the "Block-stale" shares. 1 times out of 10 this address finds a share just before a block and 1 times out of 100 it should find the following share (some time they both will be valid, some time the first will be a Block-stale that makes it through thanks to the second and some time the Block-stale will be orphaned). So what you witnessed should happen every 100 blocks (16 hours or less given the rise of hashrate) on average (with these time scales you would need several weeks of data sampling to get a good enough sample of data).

It is possible
Share chain time line:

s1
s2
s3
...
sa
sbsxsy
and your sb is orphaned. Longer chain win.
If he get fast 2 shares he can orphan every other share.
Worst case scenario: every node got share, one node got 2 fast shares and orphan all other.

the one before the block and the one after the block are from 185Kip6odGYs4eSHD6DYsWVDJBg2DNLfiV, though wouldn't that only matter if the next one in the chain was also 185Kip6odGYs4eSHD6DYsWVDJBg2DNLfiV? (as mine would have been sandwiched between the two)

ed:  ok, so the real issue here would then be that 185Kip6odGYs4eSHD6DYsWVDJBg2DNLfiV is operating at 2s latency or higher?   

all i can think of is that his client tossed out my share as being invalid, then he got another share and his node broadcast that share, and for some reason, my share got replaced by his.  that should only happen if he had gotten another one after that though, eh?  is there some other explanation?   because that could be abused

yeah, like this

2013-06-10 06:10:29.076187 Punishing share for 'Block-stale detected! 4d2f83a096d4f50ce5fccfd3d81fb97988ad9eac42ddfad5b6 < 1c3c0e8358b6fe20f6d09bfeef1f9aa0fc897ad634c8da56aa'! Jumping from 5538fa58 to
 be8220df!
2013-06-10 06:10:31.197403 GOT SHARE! Brusthonin 10823d52 prev be8220df age 1.81s
2013-06-10 06:10:33.597242  Shares: 33 (1 orphan, 4 dead) Stale rate: ~15.2% (6-31%) Efficiency: ~104.6% (85-116%) Current payout: 0.3049 BTC
2013-06-10 06:10:43.603981  Shares: 33 (2 orphan, 4 dead) Stale rate: ~18.2% (8-35%) Efficiency: ~100.9% (80-113%) Current payout: 0.3017 BTC

that just happened, again

oh, here is what it looked like from my a different node:

2013-06-10 06:10:29.383634 Skipping from block 4d2f83a096d4f50ce5fccfd3d81fb97988ad9eac42ddfad5b6 to block 1c3c0e8358b6fe20f6d09bfeef1f9aa0fc897ad634c8da56aa!
2013-06-10 06:10:30.688724 Punishing share for 'Block-stale detected! 4d2f83a096d4f50ce5fccfd3d81fb97988ad9eac42ddfad5b6 < 1c3c0e8358b6fe20f6d09bfeef1f9aa0fc897ad634c8da56aa'! Jumping from 5538fa58 to
 be8220df!
2013-06-10 06:10:35.396229 P2Pool: 17360 shares in chain (17364 verified/17364 total) Peers: 64 (8 incoming)
2013-06-10 06:10:35.396380  Local: 0H/s in last 0.0 seconds Local dead on arrival: Expected time to share:
2013-06-10 06:10:35.396506  Shares: 0 (0 orphan, 0 dead) Stale rate: Efficiency: Current payout: 0.3049 BTC
2013-06-10 06:10:35.396555  Pool: 736GH/s Stale rate: 18.9% Expected time to block: 1.1 days

nobody mining on it though, so doesn't show reports of new work.  the US node runs slower since it's on a crappy dual xeon and only using 8 cores.  oh, you can see how it did log my share as valid though, since the payout increased to 0.3049

the times:

06/10/2013_06:56:34:620911792 (US)
06/10/2013_06:56:34:634211668 (Germany)

Ideally: run another node with appropriate settings, parse the result of getblocktemplate to compute the fees over an extended period.

My estimation is less accurate than that: it's based on a relatively medium sample size (several dozens with these settings over the past days). This can only illustrate what you could get these past days (and maybe detect a trend too). If one large pool upgrades its configuration and starts confirming the transactions currently waiting this number might go down. On the other side if one service starts to generate large numbers of transactions with fees just below what most of the miners accept (accepting a delay until a minority of miners confirm it or the txs age enough), this number will go up.

If I understand correctly, P2Pool doesn't want to build a share on top of one it knows to be stale (built on a previous Bitcoin block).

It may be because your bitcoind has better connections to the Bitcoin P2P network and learns of new blocks before others: if the majority of the network is slower it will not see the share as a "Block-stale" as you do and not punish it, refusing your share in the relatively rare case when you submit one just after this "Block-stale". You could lose a bit of income this way, but it should not be noticeable (this can only affect you during the ~5s a block needs to fully propagates the Bitcoin network, which is less than 1% of the block interval: in the worst case you shouldn't lose more than 0.5% of efficiency).

If you modified the source to turn off the 'punishing share', you would find your node at the opposite end of the spectrum: it would build on a potential stales and make orphans too.

You can find out if it's a problem by computing the number of shares you found just after a block that were orphaned and the number of shares that were accepted. If you have enough logs/hashrate you can get a meaningful sample (one hundred shares generated just after blocks would be adequate) and find if you get more orphans in this population than the orphans you get over the same time period. This would make sure there is some imbalance and I think we could even find out if reversing the logic would benefit you in your case (I'm a bit tired and going to bed, but I think it's simple probabilities).

re:  Punishing share for 'Block-stale detected!, etc.

I get a lot of orphans when this happens... because my bitcoind is too fast?

I went to several other pools (my other one in Florida, OVH in Canada, p2pool.org, some others) and they all had my share listed, which means that it was accepted and got orphaned later.

This occuring after several:

2013-06-09 21:34:35.132788 Skipping from block 4bc4be449a7de0c01cb29a9d661045a19393dea2cefc2e26b to block 9b14c16ea0d67eda77564adca4de0ac3e84b1efbd8cfb5adce!
2013-06-09 21:34:36.831062 Punishing share for 'Block-stale detected! 4bc4be449a7de0c01cb29a9d661045a19393dea2cefc2e26b < 9b14c16ea0d67eda77564adca4de0ac3e84b1efbd8cfb5adce'! Jumping from 2ba6238a to e8ee1640!
2013-06-09 21:34:36.917817 Punishing share for 'Block-stale detected! 4bc4be449a7de0c01cb29a9d661045a19393dea2cefc2e26b < 9b14c16ea0d67eda77564adca4de0ac3e84b1efbd8cfb5adce'! Jumping from 2ba6238a to e8ee1640!
2013-06-09 21:34:36.920728 Punishing share for 'Block-stale detected! 4bc4be449a7de0c01cb29a9d661045a19393dea2cefc2e26b < 9b14c16ea0d67eda77564adca4de0ac3e84b1efbd8cfb5adce'! Jumping from 2ba6238a to e8ee1640!
2013-06-09 21:34:40.064626 GOT SHARE! Brusthonin 32cdc8e4 prev e8ee1640 age 2.69s

... and then that share was orphaned.  It seems to me like if I modified the source to turn off the whole 'punishing share' stuff, I'd get less orphans?

Where were you asked you to reduce your efficiency?

On my P2Pool-Node Hashes 5 GH/s. Thats a chance form 0.5%  to find one p2pool-Blocks.

So why should I reduce my efficency for every Payout to get once the tx-fees in 200 P2pool-Blocks?

 

My dgc p2pool start to use a lot of memory ( 288mb and rising ), it could be due to the number of shares downloaded? (in the data/digicoin folder there is shares.0 , shares.1, shares.2  of about 10mb each)  it's a normal behaviour?

These stats are obviously underestimating what you can get: they are based on what most miners do, not what they could do. The fees could easily be 2 to 2.5% with bitcoind 0.8.2 default settings.


Not if you configure bitcoind and p2pool to lower their network traffic as (again...) explained by the guide in my signature.

TL;DR: I have an average ADSL connection and use it for several other traffic types (Bitcoind+P2Pool is ~30% of my BW).
I can even use 1MB blocks and lower minimum fees without lowering my efficiency (reaching 3 to 5% additional fee income).
I only had to limit the number of bitcoind (10) and P2Pool connections (5 outgoing + 5 incoming) to get this result.

pro: you get to split an extra 0.96% in fees to everyone else (less than 0.25BTC), going by stat info on http://blockchain.info/stats   

con: you get a lot more orphans & more processing power is needed, not altogether related to the getblock latency, but actual transferring within the p2pool network itself

Larger blocks could increase the chances of losing the block as an orphan, but in the case of p2pool thanks to tx pre-forwarding this concern is mostly obviated.
The other drawback to too many tx's is GBT can take longer.  Normal pools do GBT far less often than p2pool.  During the recent spam txo attacks, you've seen p2pool miners increase the minimum tx fee so GBT would be much faster.  0.8.2 improved that performance issue a *lot* thanks to sipa.

pro: the block is worth more, P2Pool users earn more,
con: you might have to tune your setup to keep your efficiency (especially if you have a slow link, see the guide in my signature).

whats the pro and cons of integrating MUCH TX in a P2Pool Block?