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

I happen to really agree with this, just wish I had some spare BTC to add, maybe'll I'll send 0.01 or 0.02, just emptied my wallet as I'm in the process of going from U1's and U2's to Rockminer R-Boxes.  Currently debating whether to go S3 when we get details, or go up to the next level of rockminer when they are released.  If I want to stay with P2Pool, I don't think I have much choice, well at least not until we know whether or not the new rockminer will work well with P2Pool, luckily the R-Boxes do so I'm hopeful.  I'd really like to see this fixed though, because I think the S3 might be the better way to go.

Great. More alt-coins that can't be mined.......

Really, wtf is he doing faffing around with alt-coin additions when there are far more urgent things to be done? Concentrate on the btc side of p2pool - there are plenty of forks for alt-coins already, ffs.

S2's and upcoming S3's are critical to p2pools success.

The bounty for Forrest to get them running smoothly is up to BTC0.75

"for a working solution for p2pool/anitminer S2 & S3 compatibility with the Ants achieving expected hashrate and shares."

Anyone is welcome to contribute to the donation address, bounty is paid to forrestv (or his designee) upon a working, distributed solution or returned in full in 30 days (July 25th), I will pay return tx fees for any donation over BTC0.001, if your donation is less, consider it donated.

Bounty Address: 1Ft1DZ4EcpH1jFttDoPwsFbe11a6diyZ1H

https://blockchain.info/address/1Ft1DZ4EcpH1jFttDoPwsFbe11a6diyZ1H

Signed message:


Message signature:


Please contribute.

That is great news! Just took a look at GitHub though and looks like the only changes were for Terracoin?

Regardless, great to see Forrest active on p2pool GitHub again! Thanks.

Didn't help here.

I just upgraded my node to the latest git.  Actually seems worse than before, barely above 900gh/s.  Before it was 930gh/s.

M

There is an update for the p2pool software, not sure when it came out but I just applied the updates and now my S2's are hashing at the full 1ths.

I just wish I had my new miners a day or two earlier to have more shares.

Agreed, what a great few days for p2pool!

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.

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

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://bitcointalksearch.org/topic/m.7545494

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.

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".

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

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

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

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

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.

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!!!

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...