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

[yslyung]

Somehow I think P2Pool dying out. The network performance is ridiculous, the last visitors on my Node passed weeks ago. I think I switch my node down.

 

Don't you use your own node then?

The last couple of weeks have been excellent for p2pool - way above average.

math is hard . . .

[chalkboard17]

I'm facing a problem.
Every so often board 1 stops hashing for a few minutes, decreasing my overall long term hashrate from ~1385gh/s to ~1350gh/s resulting in an over 2.5% loss that would force me to use a centralized pool.

This is happening as I write this post.
http://prntscr.com/7f3hc8
http://prntscr.com/7f2vt3
http://prntscr.com/7f2vmw
The 4 drops in the day chart are all because of this problem.

I never had such problem before.
I had to do this in order to avoid having hashrate less than 1250gh/s
I have stable internet connection and good computer. I don't believe it's my node or else it would change pool or make both boards stop.
I am running bitcoin-xt 0.10.2 and board 1 always run 8c hotter than #2, but none of them have ever reached 60c and they run in a cool place.

My diff1 and diffa always were very equal but when I do the cited software modification diff1 doubles and diffa decreases a little bit. Is that ok?
Any input is greatly appreciated and I hope I can fix this as I really want to run my own node and help decentralization.
Thank you.

[-ck]

Serious question: What would it take to get you and CK to merge your pool with P2Pool, and focus on it's scalability problems?

We've both said numerous times, there is no valid solution to its most significant scalability problems. Pooled mining is a solution to the variance of solo mining - the more miners there are the less the variance. p2pool is the anti-solution to pooled mining - above a certain size, the more miners there are, the more variance there is; it is just solo mining on a smaller scale. It doesn't matter how much money you throw at us, we can't solve this problem in its current form. Rewriting the p2pool software in a scalable language like C only makes each node able to handle more miners - and that's not really important since the idea is each miner runs their own node for their own hardware. It does not solve the design issue.

While I do understand your points, I find it ironic for you to criticize P2Pool's infrastructure while running your own closed source centralized pool.

Kano's ckpool runs ckpool software which is absolutely all free and open code. Centralised it may be, but closed it most definitely is not.

[chalkboard17]

Update on my previous post: It just now happened on chain 2. Only took a few seconds to start back to normal.
It seems sometimes it takes many minutes while sometimes it takes a few seconds. Still, I am losing money with this and unfortunately will be forced to leave p2pool (which I do not want) if I cannot fix this. Really appreciate some help on this. Thanks.
EDIT again two hours after this post: happening more frequently

[kano]

...
How do you store submitted work for your pool? Do you plan to keep all the data in a query-able state for all time?

After thinking about this on and off for over a year now I'm OK with having an ~estimated~ luck, that is consistently calculated from the data we have available.

The share storage in my pool I have documented ... let me find the link ...
https://bitcointalk.org/index.php?topic=789369.msg10731200#msg10731200

It serves it's intended purpose which is to reflect how the pool is preforming overall, over time.

I view having to use imperfect data as a trade off for getting completely trust-less decentralization, something I value much more than a 100% accurate all the time luck stat.

While I do understand your points, I find it ironic for you to criticize P2Pool's infrastructure while running your own closed source centralized pool.

Heh - oops - you got that wrong
It's open source - here:
https://bitbucket.org/ckolivas/ckpool/src

... oh -ck said it above also

[luthermarcus]

I don't know why people attack kano, ck or forestv or anyone else for that matter. They put out allot for the community and you guys should have more respect to dev's that put out open source and I'm not just talking about his pool. Unless your asking a relevant question or imputing relevant info to benefit the topic your causing more harm than good to the cause. Please refrain from calling out people for the whole communities sake.

[jcumins]

I don't know why people attack kano, ck or forestv or anyone else for that matter. They put out allot for the community and you guys should have more respect to dev's that put out open source and I'm not just talking about his pool. Unless your asking a relevant question or imputing relevant info to benefit the topic your causing more harm than good to the cause. Please refrain from calling out people for the whole communities sake.

I could not agree more.  Kano , ck , forest and many others go above and beyond, i for one have the greatest respect for them.

 

[minerpool-de]

Somehow I think P2Pool dying out. The network performance is ridiculous, the last visitors on my Node passed weeks ago. I think I switch my node down.

 

Don't you use your own node then?

The last couple of weeks have been excellent for p2pool - way above average.

I dont mine anymore since 08/2014. Here in Germany the mines is senseless. You pay a lot of money for the electricity. But what are 1.2 TH / s compared to the overall performance of the network?

[yslyung]

@windpath . . . site down ?

http://minefast.coincadence.com/p2pool-stats.php

whooops looks like it's back. my bad prolly.

btw a block for today. looking for more ! so far p2pool have been doing pretty well. fingers crossed.

[Meuh6879]

what are you trying to say ?

we're talking about merged mining uno with p2pool

you are on a BITCOIN thread ... you talk about UNO crypto-currency.

[Meuh6879]

I normally get 1380gh/s on eligius and ghash. On p2pool I always get ~1230gh/s.

P2Pool local node don't lie.

Pool ... can lie (network problem, DOA lost).

[Meuh6879]

The last couple of weeks have been excellent for p2pool - way above average.

math is hard . . .

i prefer graph ...

[jonnybravo0311]

I normally get 1380gh/s on eligius and ghash. On p2pool I always get ~1230gh/s.

P2Pool local node don't lie.

Pool ... can lie (network problem, DOA lost).

It isn't really about lying.  A lot of hardware has issues with p2pool.  When they first came out, the S2 would lose 10-15% hash on p2pool.  Neptunes just don't work at all.  AM tubes don't work.

chalkboard17, I'm sure you've probably done the following, so forgive the redundancy if you have:
* update the firmware from Bitmain
* install ck/kano S5 binaries
* change the queue depth to 0 or 1
* use the '+' and '/' at the end of your BTC address to help flatten the graphs and get a more consistent reported hash

[yslyung]

what are you trying to say ?

we're talking about merged mining uno with p2pool

you are on a BITCOIN thread ... you talk about UNO crypto-currency.

i don't even know or have any idea how are you a hero member at all ?

1st PLEASE read the posts regarding merged mining about 2 pages back.

2nd i think you are a little lost with regards of discussion

3rd yes i am very well aware that i am on a bitcoin thread -> pool -> p2pool that can MERGE mine other crypto coin aka altcoins

so what are you trying to say ? i think you are LOST somewhere.

do you run your own node ? do you merge mine ? do you have any idea at all ? do you read before you post ?

yes the graph you posted that occasionally spikes 1ph or more is from me directing the "extra" hashpower to help p2pool to hit some blocks & i hope you managed to gain some btc from mining at p2pool.

[forrestv]

Hello everyone,

BIP66 implements a Bitcoin softfork which will take effect sometime between the next few days and the next few weeks. Miners that have not upgraded to Bitcoin Core >=0.10.0 will generate invalid blocks after that point.

Bitcoin softforks are handled within P2Pool by a corresponding fork which forces P2Pool users to upgrade to a newer version of P2Pool. In this case, the new version of P2Pool will require Bitcoin Core >=0.10.0 to start. This is facilitated by first getting 50% of the P2Pool hashrate to upgrade by external means (this forum and the mailing list below), upon which the "A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION! An upgrade is likely necessary. Check http://p2pool.forre.st/ for more information." warning is displayed to the rest of the users, which hopefully quickly upgrade. Upon 95% of the hashrate having converted, the fork happens, and users that haven't upgraded are split off to mine in their own mini-P2Pool. I regret not taking action earlier; I hadn't been aware of the softfork until an email on the bitcoin-dev mailing list today.

So, a new P2Pool version will be released within the next day or two, once testing has finished. Users will be urged to upgrade here and on the p2pool-notifications mailing list (which I'd urge you to subscribe to now if you haven't). Without this P2Pool softfork, we will continue mining with an unknown number of users generating invalid blocks, which clearly isn't desirable.

[windpath]

Hello everyone,

BIP66 implements a Bitcoin softfork which will take effect sometime between the next few days and the next few weeks. Miners that have not upgraded to Bitcoin Core >=0.10.0 will generate invalid blocks after that point.

Bitcoin softforks are handled within P2Pool by a corresponding fork which forces P2Pool users to upgrade to a newer version of P2Pool. In this case, the new version of P2Pool will require Bitcoin Core >=0.10.0 to start. This is facilitated by first getting 50% of the P2Pool hashrate to upgrade by external means (this forum and the mailing list below), upon which the "A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION! An upgrade is likely necessary. Check http://p2pool.forre.st/ for more information." warning is displayed to the rest of the users, which hopefully quickly upgrade. Upon 95% of the hashrate having converted, the fork happens, and users that haven't upgraded are split off to mine in their own mini-P2Pool. I regret not taking action earlier; I hadn't been aware of the softfork until an email on the bitcoin-dev mailing list today.

So, a new P2Pool version will be released within the next day or two, once testing has finished. Users will be urged to upgrade here and on the p2pool-notifications mailing list (which I'd urge you to subscribe to now if you haven't). Without this P2Pool softfork, we will continue mining with an unknown number of users generating invalid blocks, which clearly isn't desirable.

Thank you Forrest, good to see you around!

[jonnybravo0311]

Hello everyone,

BIP66 implements a Bitcoin softfork which will take effect sometime between the next few days and the next few weeks. Miners that have not upgraded to Bitcoin Core >=0.10.0 will generate invalid blocks after that point.

Bitcoin softforks are handled within P2Pool by a corresponding fork which forces P2Pool users to upgrade to a newer version of P2Pool. In this case, the new version of P2Pool will require Bitcoin Core >=0.10.0 to start. This is facilitated by first getting 50% of the P2Pool hashrate to upgrade by external means (this forum and the mailing list below), upon which the "A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION! An upgrade is likely necessary. Check http://p2pool.forre.st/ for more information." warning is displayed to the rest of the users, which hopefully quickly upgrade. Upon 95% of the hashrate having converted, the fork happens, and users that haven't upgraded are split off to mine in their own mini-P2Pool. I regret not taking action earlier; I hadn't been aware of the softfork until an email on the bitcoin-dev mailing list today.

So, a new P2Pool version will be released within the next day or two, once testing has finished. Users will be urged to upgrade here and on the p2pool-notifications mailing list (which I'd urge you to subscribe to now if you haven't). Without this P2Pool softfork, we will continue mining with an unknown number of users generating invalid blocks, which clearly isn't desirable.

Thanks for the update, and I echo windpath's sentiments: glad to see you around.  I'll be sure to update my nodes as soon as you have completed your work.

[OgNasty]

The Prodigal Son has returned!

[p3yot33at3r]

The Prodigal Son has returned!

Absolutely!

Hopefully this will be the start of a new era of communication with p2pool users on this forum 

Forrestv - will there be any other improvements/fixes/additions to the new p2pool release?

Thanks, & welcome back 

[yslyung]

the man is watching.

waiting for the release (hoping there will be improvements) & ready to upgrade.

thx forrestv & rest of the gang.