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

[PatMan]

Right, thanks. That was over 2 years ago though, maybe it's improved? I dunno, might give it a go......depending on how Matt gets on with it.

[mdude77]

My p2pool node in LA is unstable.  My host is having hardware problems.  My VPS keeps rebooting or shutting down of its own accord.

M

[RoadStress]

I use to watch http://minefast.coincadence.com/p2pool-stats.php for p2pool luck and stats, but I see that there is a problem now. 4 orphaned, 0GH/s network speed.

What is going on? Have I missed something? Because I don't see a discussion about it here.

[PatMan]

I use to watch http://minefast.coincadence.com/p2pool-stats.php for p2pool luck and stats, but I see that there is a problem now. 4 orphaned, 0GH/s network speed.

What is going on? Have I missed something? Because I don't see a discussion about it here.

I believe it might be in the process of being moved to p2pool.org.......?

[kgb2mining]

I use to watch http://minefast.coincadence.com/p2pool-stats.php for p2pool luck and stats, but I see that there is a problem now. 4 orphaned, 0GH/s network speed.

What is going on? Have I missed something? Because I don't see a discussion about it here.

I believe it might be in the process of being moved to p2pool.org.......?

The reverse if I read windpath's post correctly from the other day - he was redirecting p2pool.org over to his minefast node to allow him to re-launch the newly revamped p2pool.org site.

If I had to guess I'm going to say that pointing whatever traffic from p2pool.org over to the minefast server had something to do with what we're seeing right now with the node.  I messaged him yesterday about something else so let's see what happens when he has a chance to look at it.

[Acejam]

Looks like p2pool.org:9332 and minefast[2].CoinCadence.com:9332 are both down.

This is why a high availability P2Pool cluster like http://p2pool.io/ is better.   (for those who need to use a public P2Pool node)

[windpath]

Yea, coincadence is down. After pretty much continuous uptime since June I'm interested to discover the problem. Unfortunately I'm out of the country until Monday morning so it will have to wait until then.

Once we release the public dashboard this will no longer be an issue.

I apologize for any inconvenience this has caused our miners.

Hope you all have a great weekend and I'll follow up here on Monday

[jonnybravo0311]

Yea, coincadence is down. After pretty much continuous uptime since June I'm interested to discover the problem. Unfortunately I'm out of the country until Monday morning so it will have to wait until then.

Once we release the public dashboard this will no longer be an issue.

I apologize for any inconvenience this has caused our miners.

Hope you all have a great weekend and I'll follow up here on Monday

The problem is you left the country.  That's the way it ALWAYS works.  No access?  Time to crash!

Hope you're enjoying your time out of the country and not working too hard while gone.  I'm pretty sure we'll all live a few days without knowing the pool luck, or seeing how much our miners have earned over time, or .... wait a minute .... how will I live without knowing that??!!??  Get the hell back here and fix it!!!

[PatMan]

Just a heads up guys:

There is now a C++ client. Those who had been using the python client should probably switch to it (its semantics are identical, it runs on Linux and under Wine, so I assume Windows) and it is much, much faster than the python client.

Trying it out now.......

[pmorris]

Just a heads up guys:

There is now a C++ client. Those who had been using the python client should probably switch to it (its semantics are identical, it runs on Linux and under Wine, so I assume Windows) and it is much, much faster than the python client.

Trying it out now.......

Thanks, any issues? Or is it a drop in replacement once compiled

I'm guessing you would need to run the original p2pool once the C++ relay is running?

[PatMan]

No issues at all, and it is much faster with hardly any resource usage.

No need to compile it, it's ready to run from within the client folder. Yes, I run it with the standard p2pool code.

Well worth it  

Edit: Makes me wonder how much better p2pool would be if it was also in C++......

[P2Pools]

After a lot of hard work and effort, we are pleased to announce the unveiling of our new P2Pool node:
http://p2pools.us
BTC Specific node: http://btc.p2pools.us:3333

Our servers are located in the Greater Boston Area and we encourage everyone who is interested in P2Pool mining to take a look at our node. 

[-ck]

Edit: Makes me wonder how much better p2pool would be if it was also in C++......

c/c++ are much better suited to the task than python. Python may be quick for development but p2pool has outgrown it. I toyed with the idea of rewriting p2pool in c ages ago but it's a veritable bootload of work. On the other hand, I may find a way to hook something like p2pool into my ckpool code or vice versa.

[PatMan]

Edit: Makes me wonder how much better p2pool would be if it was also in C++......

c/c++ are much better suited to the task than python. Python may be quick for development but p2pool has outgrown it. I toyed with the idea of rewriting p2pool in c ages ago but it's a veritable bootload of work. On the other hand, I may find a way to hook something like p2pool into my ckpool code or vice versa.

I suggested rewriting an alternative p2pool based on C++ over a year ago when I first got tired of the lack of development:

https://bitcointalk.org/index.php?topic=213051.0

but was unable to find anyone to do it at the time. I also got chastised for even suggesting it.....

I'm also wondering if Bitmain are using python for the version they're working on, but don't think it will come out for a while yet, if at all. It is a crapload of work ck, but if you get the urge......I'm sure there are many p2pool users here who would be more than happy to help you out - as well as make it worth your while.....

Can't think of anyone better to do it actually.

[norgan]

Edit: Makes me wonder how much better p2pool would be if it was also in C++......

c/c++ are much better suited to the task than python. Python may be quick for development but p2pool has outgrown it. I toyed with the idea of rewriting p2pool in c ages ago but it's a veritable bootload of work. On the other hand, I may find a way to hook something like p2pool into my ckpool code or vice versa.

I suggested rewriting an alternative p2pool based on C++ over a year ago when I first got tired of the lack of development:

https://bitcointalk.org/index.php?topic=213051.0

but was unable to find anyone to do it at the time. I also got chastised for even suggesting it.....

I'm also wondering if Bitmain are using python for the version they're working on, but don't think it will come out for a while yet, if at all. It is a crapload of work ck, but if you get the urge......I'm sure there are many p2pool users here who would be more than happy to help you out - as well as make it worth your while.....

Can't think of anyone better to do it actually.

Hells yeah, I would love to see it written in c/c++ then it can be compiled for a native windows service. (yes I run windows servers).
It would likely make it more accessible to other devs to contribute as well.

[pmorris]

Edit: Makes me wonder how much better p2pool would be if it was also in C++......

c/c++ are much better suited to the task than python. Python may be quick for development but p2pool has outgrown it. I toyed with the idea of rewriting p2pool in c ages ago but it's a veritable bootload of work. On the other hand, I may find a way to hook something like p2pool into my ckpool code or vice versa.

Maybe a re-write could also be an opportunity to tinker with the protocol to improve things. Not sure if these are totally practical but a couple of thoughts I had:

At the moment, as I understand it, there is a single difficulty for the sharechain. I was penciling out a potential alternative whereby each node attempts to target 10 shares in the PPNS sharechain. This would be big enough to minimize volatility but small enough for there to be room in the PPNS for more lower hashrate miners.

Fixing the impact of the 30 second share time causing difficulties with some ASIC miners would good too. Maybe one possibility is that the last 20 shares in the sharechain are not paid. So miners would work on the same blockheader for 10 minutes not updating it for each and every share found. Then when the 20th new share is found a new blockheader is created that incorporates them and the process starts again. I think this would balance out over time to be fair and maybe fix some of the miner compatibility issues?

I was thinking about having shot at implementing p2pool in Go. But it's a big job and complicated. I don't think I have the time or skill to do it.

[nreal]

So it has changed, the time a share is valid. It used to be 3 blocks or three days If i remeber right. Now its like 24 hours, it doesnt matter if a block is found or not. theres graps of my 30mb shares on saturday and sunday, didnt get payment todays (monday) block 

http://p2pool.servebeer.com:9332/static/sharetime.jpg

[jonnybravo0311]

So it has changed, the time a share is valid. It used to be 3 blocks or three days If i remeber right. Now its like 24 hours, it doesnt matter if a block is found or not. theres graps of my 30mb shares on saturday and sunday, didnt get payment todays (monday) block 

http://p2pool.servebeer.com:9332/static/sharetime.jpg

The code is still the same.  Your understanding is a bit incorrect, though.  It's not "when three blocks are found" it is "the average amount of work is completed that would have solved 3 blocks".  It also wasn't "three days" it was "8640 shares".  Since the pool is averaging 3.5PH/s (just using the thread title's estimate here), that means at current difficulty, the pool expects to find a block every 9.35 hours.  That's why you're seeing your share fall off after just over a day.

[wlz2011]

P2POOL池 矿机加难度方法

P2POOL池，这两天测试了新的难度玩法，蚂蚁S3，使用+5120难度，并没有什么影响，反而S值很好，而且蚂蚁S3不显示BestShare的问题也得到了解决，现在显示了。这样的好处是不但不影响任何，反而节约了网络消耗，还提高了S效率，我个人认为也是有效减少P2POOL池全网DOA的一个方法。

暂时定义+难度的方法为：
蚂蚁S3 +5120
蚂蚁S1 +1280
龙矿1T +10240
龙矿1.5T +15360


我个人今天开始测试蚂蚁S3+10240，明天开始测试100T池不加难度（实际难度大概在1万-10万）。

下面是我的S3测试图

非常抱歉，我的英文不好，只能中文 + 谷歌翻译。


P2POOL pool plus the difficulty of mining machine method

P2POOL pool, this two-day test of the new gameplay difficulty, ants S3, use +5120 difficulty, and there is no impact, but the S value is very good, but does not show BestShare S3 ant problems have been resolved, and now shows. The advantage is that not only does not affect any, but to save the network consumption, but also improve the efficiency of S, I personally think it is an effective method to reduce the whole network of DOA P2POOL pool.

+ Difficulty being defined methods:
Ants S3 +5120
Ant S1 +1280
Long ore 1T +10240
Long ore 1.5T +15360


Personally, I started testing today ants S3 + 10240, begin testing tomorrow 100T pool without difficulty (real difficulty probably 10000--100000).

Here is my S3 test chart

I'm sorry, My English is very bad, only Chinese + Google translation.









目前正在测试 蚂蚁S3+10240
Currently being tested ants S3 + 10240





下面这张月图，可以清晰地看见，4台S3（1.9T）S值在0-0.03波动。
长期挖P2POOL 并没有太大的影响，尽管目前效率低。
我相信这些都是暂时的。

This month figure below, you can clearly see, four S3 (1.9T) S values ​​fluctuate 0-0.03.
Long-term dig P2POOL not have much impact, although temporarily low efficiency.
I believe that these are temporary.

[windpath]

OK folks, http://minefast.coincadence.com is back up and running.

Due to the unexpected downtime between September 5th and September 9th, 2014 certain data for that time-frame is not available or inaccurate.

Current Round Luck will be accurate after 2 blocks are found
24 Hour hash rate will be accurate after 24 hours
Seven day luck will be accurate September 15th
Thirty day luck will be accurate October 8th

Node dashboard data is accurate.
Historical block data is accurate.
Historical miner payouts are accurate.

We are still working to determine what caused the instability in the node.

Also, in the near future we will roll out redundant distributed data collection nodes to attempt to avoid future holes in our data collection.

We apologize for the inconvenience.