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

[phillipsjk]

I tried to find out something more about this problem, but I couldn´t.

My problem is, that I don´t get any IN connections.


I have open all ports OUT, and these ports IN: 8333,9332,9333

Thank you in advance for any help.

It takes time.

I was able to check that you ports are open by accessing you node over the Internet.
Well, I only checked port 9332.

[jacob019]

Are there other indicators in P2Pool when you find a block other than the bonus?  How's the bonus differentiated from other payouts to our P2Pool associated address, now that we're seeing fairly regular donations to P2Pool miners?

Even if it says "Block Found!" on the rolling command line status, I'd have a hard time seeing it (not like I sit here watching it scroll by all day).  Is it in another log or do I have to slog through all my rigs and look at their UI's to see if they found a block (like the S1 Mining Status page)?

windpath - It would be great to have an indicator of blocks found (total and individual blocks highlighted) on the Miner Status pages you provide, including for miners outside your node on CoinCadence.

Alternatively can I add similar functionality to my node's UI.... where to source the data?

In the classic p2pool interface you can inspect the shares of recent blocks.  The shares show the payout address so you know who the blockfinder is.

[windpath]

I tried to find out something more about this problem, but I couldn´t.

My problem is, that I don´t get any IN connections.

http://84.42.144.19:9332/static/

Version: 13.4
Pool rate: 292TH/s (17% DOA+orphan) Share difficulty: 1280000
Peers: 8 out, 0 in
Local rate: 8.85GH/s (5.1% DOA) Expected time to share: 7.2 days
Shares: 0 total (0 orphaned, 0 dead) Efficiency: Huh

I use P2Pool release 13.4 for Windows (https://bitcointalk.org/index.php?topic=18313.0)
I have open all ports OUT, and these ports IN: 8333,9332,9333

Thank you in advance for any help.

It can take some time for incoming connections to show up, first time around it took 3 days for my first incoming connection...

[raskul]

nice run of luck today 

[jedimstr]

Boom... that's 4 Blocks for the last 2 days..  *rubs lucky block erupter keychain*

[jedimstr]

No, there is no difference.

All the shares you mine to your address wil be saved in the sharechain.

Well, I found one difference... or more like realized the difference after the fact.

When you throw the rented/remote/extra miners onto another closer node, you don't have the benefit of their hashpower for your local Merge Mining.  Only the remote node gets that benefit, if they're using it at all.

Oh well... don't know if the merged mining is enough of a benefit to outweigh the lower latencies on the remote miners.

[jonnybravo0311]

No, there is no difference.

All the shares you mine to your address wil be saved in the sharechain.

Well, I found one difference... or more like realized the difference after the fact.

When you throw the rented/remote/extra miners onto another closer node, you don't have the benefit of their hashpower for your local Merge Mining.  Only the remote node gets that benefit, if they're using it at all.

Oh well... don't know if the merged mining is enough of a benefit to outweigh the lower latencies on the remote miners.

That's correct.  It is the node's hash rate that gets applied to merge-mined coins.

Hey windpath... why is your node showing the last block (307942) orphaned?  I've got 6 confirmations on it - shows the same on blockchain.info.



What's your node know that the rest of the network doesn't?

[windpath]

windpath - It would be great to have an indicator of blocks found (total and individual blocks highlighted) on the Miner Status pages you provide, including for miners outside your node on CoinCadence.

Alternatively can I add similar functionality to my node's UI.... where to source the data?

Totally agree, I want to start processing and storing data directly from the share chain, but still  have some other items to finish up first (like global miner stats).

I grab the on-node share data from the p2pool log file and store it in MySQL..

[windpath]

No, there is no difference.

All the shares you mine to your address wil be saved in the sharechain.

Well, I found one difference... or more like realized the difference after the fact.

When you throw the rented/remote/extra miners onto another closer node, you don't have the benefit of their hashpower for your local Merge Mining.  Only the remote node gets that benefit, if they're using it at all.

Oh well... don't know if the merged mining is enough of a benefit to outweigh the lower latencies on the remote miners.

That's correct.  It is the node's hash rate that gets applied to merge-mined coins.

Hey windpath... why is your node showing the last block (307942) orphaned?  I've got 6 confirmations on it - shows the same on blockchain.info.



What's your node know that the rest of the network doesn't?

Haha, nothing... It's a valid block, looks like a bug...

I'm away from the office till Monday, will take a look and see if I can fix it from here, but will most likely not be corrected till Monday...

[sconklin321]

Wow 4 Blocks and we're showing on the pools distibution at blockchain.info again!!!  Nice string of luck, and just before the shares from when my miner got lucky a couple days ago expired too.  I'm very happy with P2Pool today!!!

[norgan]

Wow 4 Blocks and we're showing on the pools distibution at blockchain.info again!!!  Nice string of luck, and just before the shares from when my miner got lucky a couple days ago expired too.  I'm very happy with P2Pool today!!!

Boom! Can anyone say gravy train. Toot toot! Haha I had pointed some rented hashing power at me node during the down time and its all paying out right now.

[sconklin321]

Wow 4 Blocks and we're showing on the pools distibution at blockchain.info again!!!  Nice string of luck, and just before the shares from when my miner got lucky a couple days ago expired too.  I'm very happy with P2Pool today!!!

Boom! Can anyone say gravy train. Toot toot! Haha I had pointed some rented hashing power at me node during the down time and its all paying out right now.

Was a nice gravy train, my 0.02 approximate payout dropped to 0.012 sometime after the 4th block.

[norgan]

Wow 4 Blocks and we're showing on the pools distibution at blockchain.info again!!!  Nice string of luck, and just before the shares from when my miner got lucky a couple days ago expired too.  I'm very happy with P2Pool today!!!

Boom! Can anyone say gravy train. Toot toot! Haha I had pointed some rented hashing power at me node during the down time and its all paying out right now.

Was a nice gravy train, my 0.02 approximate payout dropped to 0.012 sometime after the 4th block.

mine is still up where it should be:
http://www.norgzpool.net.au

[windpath]

That's correct.  It is the node's hash rate that gets applied to merge-mined coins.

Hey windpath... why is your node showing the last block (307942) orphaned?  I've got 6 confirmations on it - shows the same on blockchain.info.



What's your node know that the rest of the network doesn't?

Manually corrected the block for display, will have to dig around next week and see what caused it, for some reason the block height was not recorded correctly...

That block puts our 7 day luck at 118%. not to shabby of a comeback before the impending diff jump

[jonnybravo0311]

That's correct.  It is the node's hash rate that gets applied to merge-mined coins.

Hey windpath... why is your node showing the last block (307942) orphaned?  I've got 6 confirmations on it - shows the same on blockchain.info.



What's your node know that the rest of the network doesn't?

Manually corrected the block for display, will have to dig around next week and see what caused it, for some reason the block height was not recorded correctly...

That block puts our 7 day luck at 118%. not to shabby of a comeback before the impending diff jump

Yeah, I'm quite happy we managed to knock out 4 blocks so quickly before what appears to be somewhere around a 25% diff increase.  From 6/25 until today I made 0.65310308BTC from p2pool with my SP10 and 2 S1s.  I'll take that

[phillipsjk]

Between 12% hardware error rate, 20% penalty for no long polling, and another 10% for slow CPU lag (probably 3 seconds), I am getting 43% local DOA though.

Hard numbers?

Hardware error rate:
Blade thinks it is hashing: 10777 MHash/s
P2Pool sees an actual rate of: 9534MH/s
(1-(9534/10777))x100%=11.5%

No long polling penalty
Blade has 32 relatively independent hashing chips.
Blade handles 147 shares per minute.
147 shares/32chip.minute=4.59375shares/chip.minute
(60seconds/minute)/(4.59375shares/chip.minute)=13.1seconds.chip/share
Expected DOA: (13.1seconds.chip/share)/(2*30 second.share-interval)*100%=22%(chip/share-interval)

Slow CPU lag:
Probably the number you are most interested in, but the most shaky as well.
P2Pool reports the "Bitcoind GetBlockTemplate Latency" is an average of  0.454s
With a 10 minute sample period, P2Pool appears to use ( 17.19%/2.34%=7.35x) the CPU time bitcoind does.
7.35x0.454s=about 3.3seconds of CPU lag.
Penalty with 30 second round time: 3.3/30*100%=11.1%
The network probably has some lag as well.

Are the numbers sane?
The above percentages (neglecting hardware error rate) add up to an expected local DOA of 33.1%
P2Pool reports a local DOA rate (over last ~12 hours) of: (DOA mean 3.45GH/s)/(Total mean 9.48GH/s)x100%=36% DOA

My DOA number will vary by 12%; that is why I thought the hardware error rate was maybe counted.

Conclusion
I have a slow CPU, and including zero fee transactions does no generally push my bitcoind latency over 1 second (with 500000 byte blocks). Yes, including zero-fee transactions will increase your latency: as does including paying transactions. Currently fees are insignificant compared to the block-reward.

Assuming 500mBTC of fees per block, we are talking a 2% bonus on 25BTC blocks.
If trying to fill a block pushes your Bitcoind latency up to 1 second, you can expect to get orphaned 0.2% of the time (when you otherwise wouldn't) assuming a 500 second block interval.
Edit: That seems to imply that paying transactions need to add up to at least 50mBTC to compensate for the CPU lag of including them. My network probably has at least 1 second of lag if I send the whole block at once (not sure how much gets "pre-sent".

[sconklin321]

Has anyone heard the outcome of the Petamine vote?  Just curious if we're going to see a 1 ph/s influx and a jump of share difficulty.

[oda.krell]

FYI, I just opened a thread on the speculation subforum about incentivizing p2pool, and how it is probably in the interest of investors and (most) traders to do so. Thought you might be interested, and would like to get your input as well:

https://bitcointalk.org/index.php?topic=667821.msg7545494

[Muhammed Zakir]

Between 12% hardware error rate, 20% penalty for no long polling, and another 10% for slow CPU lag (probably 3 seconds), I am getting 43% local DOA though.

Hard numbers?

Hardware error rate:
Blade thinks it is hashing: 10777 MHash/s
P2Pool sees an actual rate of: 9534MH/s
(1-(9534/10777))x100%=11.5%

No long polling penalty
Blade has 32 relatively independent hashing chips.
Blade handles 147 shares per minute.
147 shares/32chip.minute=4.59375shares/chip.minute
(60seconds/minute)/(4.59375shares/chip.minute)=13.1seconds.chip/share
Expected DOA: (13.1seconds.chip/share)/(2*30 second.share-interval)*100%=22%(chip/share-interval)

Slow CPU lag:
Probably the number you are most interested in, but the most shaky as well.
P2Pool reports the "Bitcoind GetBlockTemplate Latency" is an average of  0.454s
With a 10 minute sample period, P2Pool appears to use ( 17.19%/2.34%=7.35x) the CPU time bitcoind does.
7.35x0.454s=about 3.3seconds of CPU lag.
Penalty with 30 second round time: 3.3/30*100%=11.1%
The network probably has some lag as well.

Are the numbers sane?
The above percentages (neglecting hardware error rate) add up to an expected local DOA of 33.1%
P2Pool reports a local DOA rate (over last ~12 hours) of: (DOA mean 3.45GH/s)/(Total mean 9.48GH/s)x100%=36% DOA

My DOA number will vary by 12%; that is why I thought the hardware error rate was maybe counted.

Conclusion
I have a slow CPU, and including zero fee transactions does no generally push my bitcoind latency over 1 second (with 500000 byte blocks). Yes, including zero-fee transactions will increase your latency: as does including paying transactions. Currently fees are insignificant compared to the block-reward.

Assuming 500mBTC of fees per block, we are talking a 2% bonus on 25BTC blocks.
If trying to fill a block pushes your Bitcoind latency up to 1 second, you can expect to get orphaned 0.2% of the time (when you otherwise wouldn't) assuming a 500 second block interval.
Edit: That seems to imply that paying transactions need to add up to at least 50mBTC to compensate for the CPU lag of including them. My network probably has at least 1 second of lag if I send the whole block at once (not sure how much gets "pre-sent".

Thanks for that! Explained in simple words but understood a lot!
Kindly,
        Muhammed Zakhir

[sconklin321]

Well someone is definitely having their prayers answered by the hashing gods...whoever it is, don't stop praying...5 blocks in 3 days is nice.