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

[bitcoinbearhk]

Mining for 13 hours at 5.2TH/s, expected time to share 2.0hrs....

Actual share obtained so far:  1 total (1 ophaned, 0 good) ......


Pure bad luck or setup issue??? 

Seriously, should have got 6 shares under the "expected" scenario.

[squashpile]

That's tough to take, but probably bad luck. What are your node stats? I have nothing close to your HR, but I have gone two days @ 1.1 TH/s without a share recently. Bad luck and then from the 16th to 17th did 8-9 days of mining on P2pool. The best day. It made up for it all.
You running on windows on linux?
Got any screen output? Any P2Pool errors?

I have been having some Bitcoind crashing issues lately. I'm trying to work on those now. Pretty sure it's memory related. I hope.

Mining for 13 hours at 5.2TH/s, expected time to share 2.0hrs....

Actual share obtained so far:  1 total (1 ophaned, 0 good) ......


Pure bad luck or setup issue???  

Seriously, should have got 6 shares under the "expected" scenario.

[bitcoinbearhk]

That's tough to take, but probably bad luck. What are your node stats? I have nothing close to your HR, but I have gone two days @ 1.1 TH/s without a share recently. Bad luck and then from the 16th to 17th did 8-9 days of mining on P2pool. The best day. It made up for it all.
You running on windows on linux?
Got any screen output? Any P2Pool errors?

I have been having some Bitcoind crashing issues lately. I'm trying to work on those now. Pretty sure it's memory related. I hope.

Mining for 13 hours at 5.2TH/s, expected time to share 2.0hrs....

Actual share obtained so far:  1 total (1 ophaned, 0 good) ......


Pure bad luck or setup issue???  

Seriously, should have got 6 shares under the "expected" scenario.

P2Pool BTC

Graphs

Version: 13.4

Pool rate: 2.00PH/s (12% DOA+orphan) Share difficulty: 8820000

Node uptime: 13.5 hours Peers: 6 out, 0 in

Local rate: 5.31TH/s (1.2% DOA) Expected time to share: 2.0 hours

Shares: 1 total (1 orphaned, 0 dead) Efficiency: 0.000%

Payout if a block were found NOW: 0.00823785 BTC to xxxxxxxxxxxxxxxxxxxx. Expected after mining for 24 hours: 0.0665 BTC per block.

Current block value: 25.05109951 BTC Expected time to block: 14.2 hours

 

[squashpile]

You are good. DOA looks good compared to public nodes. I bet shares start rolling in. Stay with it   2hrs.. expected. Ha you good. Just restart everything if you are worried.


2.91 TH/s (DOA 70.50 GH/s / 2.43%)
Expected time to share: 3h 40m 1 s

That's tough to take, but probably bad luck. What are your node stats? I have nothing close to your HR, but I have gone two days @ 1.1 TH/s without a share recently. Bad luck and then from the 16th to 17th did 8-9 days of mining on P2pool. The best day. It made up for it all.
You running on windows on linux?
Got any screen output? Any P2Pool errors?

I have been having some Bitcoind crashing issues lately. I'm trying to work on those now. Pretty sure it's memory related. I hope.

Mining for 13 hours at 5.2TH/s, expected time to share 2.0hrs....

Actual share obtained so far:  1 total (1 ophaned, 0 good) ......


Pure bad luck or setup issue???  

Seriously, should have got 6 shares under the "expected" scenario.

P2Pool BTC

Graphs

Version: 13.4

Pool rate: 2.00PH/s (12% DOA+orphan) Share difficulty: 8820000

Node uptime: 13.5 hours Peers: 6 out, 0 in

Local rate: 5.31TH/s (1.2% DOA) Expected time to share: 2.0 hours

Shares: 1 total (1 orphaned, 0 dead) Efficiency: 0.000%

Payout if a block were found NOW: 0.00823785 BTC to xxxxxxxxxxxxxxxxxxxx. Expected after mining for 24 hours: 0.0665 BTC per block.

Current block value: 25.05109951 BTC Expected time to block: 14.2 hours

 

[bryonp]

Mining for 13 hours at 5.2TH/s, expected time to share 2.0hrs....

Actual share obtained so far:  1 total (1 ophaned, 0 good) ......


Pure bad luck or setup issue??? 

Seriously, should have got 6 shares under the "expected" scenario.

Just so you can compare here is mine... at 4.0TH
I some days get a share an hour and other days 1 share per 6 hours.....

Graphs

Version: unknown 7032706f6f6c2d6e2d6d6173746572

Pool rate: 2.20PH/s (11% DOA+orphan) Share difficulty: 8500000

Node uptime: 11.7 hours Peers: 6 out, 0 in

Local rate: 3.52TH/s (3.3% DOA) Expected time to share: 2.9 hours

Shares: 4 total (0 orphaned, 0 dead) Efficiency: 112.5%

Payout if a block were found NOW: 0.0441345 BTC to xxxxxxxxxxxxxxxxxxxxxxx. Expected after mining for 24 hours: 0.0401 BTC per block.

Current block value: 25.09223858 BTC Expected time to block: 12.9 hours

hope it helps......

(I used to get worried but I just leave it run and some days really make up for the bad ones... after a month of pure p2pool I am ahead of any pool I used to join!)

[murdof]

Can anyone suggest what is a good additional coin (profitable) to merge with p2pool???
I would assume, that as you are working on BTC you can make additional funds?

What's profitable today, might not be next week - so I mine them all, just in case......

BTC, DVC, IXC, I0C, GRP, HUC, FSC &, until yesterday NMC - which happens to be the most lucrative atm.......

You have an exchange for FSC?

Why do you say until yesterday NMC?

[murdof]

Thanks, added SP10, will ask in the spondoolies thread about 30.

Don't own SP30 but I watch closely the SP thread and I know people with SP30 that mine with P2Pool without issues.

They mine here: http://is.centralcavern.uk:9332/static/

[RoadStress]

Thanks, added SP10, will ask in the spondoolies thread about 30.

Don't own SP30 but I watch closely the SP thread and I know people with SP30 that mine with P2Pool without issues.

They mine here: http://is.centralcavern.uk:9332/static/

Code:

Local Shares: Total: 125 (Orphan: 14, Dead: 3)

Is that a normal orphan rate?

[murdof]

Code:

Local Shares: Total: 125 (Orphan: 14, Dead: 3)

Is that a normal orphan rate?

Global reject is ~ 15%

This is 13.6% - so i would say it is normal. Variance can give you probably lower but always have a look at global.

[RoadStress]

Code:

Local Shares: Total: 125 (Orphan: 14, Dead: 3)

Is that a normal orphan rate?

Global reject is ~ 15%

This is 13.6% - so i would say it is normal. Variance can give you probably lower but always have a look at global.

I know that having a low ping helps, but I don't expect every p2pool miner to obey this rule so that's why I wanted to see if it's normal or not but not compared to the global reject. Besides having a 0ms ping is there anything that I can do about this?

[PatMan]

You have an exchange for FSC?

Why do you say until yesterday NMC?

I used to use Atomic Trade - but FSC has gone    (along with my few million.......)

There is a problem with NMC "timeout getting getauxblock" when merge mining - devs are looking into it:

https://bitcointalk.org/index.php?topic=18313.msg8433539#msg8433539

I turned it off due to high cpu/mem usage until it's fixed.

Peace  

[mdude77]

You have an exchange for FSC?

Why do you say until yesterday NMC?

I used to use Atomic Trade - but FSC has gone    (along with my few million.......)

There is a problem with NMC "timeout getting getauxblock" when merge mining - devs are looking into it:

https://bitcointalk.org/index.php?topic=18313.msg8433539#msg8433539

I turned it off due to high cpu/mem usage until it's fixed.

Peace  

The problem is on the windows side too.  It hung my local p2pool instance.. python would not die.  I had to hard reset the computer.

M

[PatMan]

Yeah, I believe it's a system wide problem - might still be worth dropping a post on the NMC thread though - might speed up the fix a bit 

[bitcoinbearhk]

Noticed that the hash rate on P2Pool dropped significantly after the very lucky 4 blocks for today.  Wonder if this is some kind of "unlucky avoidance" tactics? 

[murdof]

Code:

Local Shares: Total: 125 (Orphan: 14, Dead: 3)

Is that a normal orphan rate?

Global reject is ~ 15%

This is 13.6% - so i would say it is normal. Variance can give you probably lower but always have a look at global.

I know that having a low ping helps, but I don't expect every p2pool miner to obey this rule so that's why I wanted to see if it's normal or not but not compared to the global reject. Besides having a 0ms ping is there anything that I can do about this?

The Iceland node has less than 10% rejected.
I think in rejected only orphan counts and not the dead.

So you are far better than average.

[bitcoinbearhk]

I have got a lot of this message on my node:

Punishing share for "Block-stale detected .......

Does this mean anything bad?

[squashpile]

Nope.. that message is fine. No issues.

I have got a lot of this message on my node:

Punishing share for "Block-stale detected .......

Does this mean anything bad?

[squashpile]

Pool over 3 PH/s right now.

Noticed that the hash rate on P2Pool dropped significantly after the very lucky 4 blocks for today.  Wonder if this is some kind of "unlucky avoidance" tactics?  

[windpath]

The pool hash rate has been growing relatively steadily since June 23rd, how long that growth line will continue is anybodies guess:

[pmorris]

Hi all

I have set out to make the best public p2pool node network out there. It's a big task to convince miners that it's worth moving their hard earned GHash to a new node/pool but here are the reasons why I hope you will consider using my bitroute.io nodes:

1. Mining using p2pool will return the highest ROI for your GHash - possibly over 100% fair value on a long run basis if you have the right node. But given the thread you probably know that.

2. Supporting p2pool is in the long term interests of a decentralised and healthy bit coin network. Again, telling you something you already know.

3. You need access to the lowest latency between your miner and the p2pool network to achieve over 100% efficiency.

Bitroute has two permanently connected p2pool and bitcoin servers - one in Newark, NJ, and one in London, UK, with a 75ms RTT ping between them and virtually no latency variance. Each node (a Linode 4) has a 500Mbit otherwise unutilised network pipe, 4Gb of RAM and 4 core processor.

So the time between your miner finding a share and it being widely broadcast to the global p2pool network will be as low as possible so you can get more than your fair share of shares.

There is also another full bitcoin node in Tokyo permanently connected to London and Newark to make sure that any blocks mined are immediately propagated to miners in Asia as well as Europe and the US to minimize the risk of orphaned blocks and lost revenue.

4. You need absolutely reliable nodes to minimize downtime. Bitroute uses production quality Linode servers using a highly stable Linux distribution and a locked down firewall.

They run the latest release (0.9.2.1) of Bitcoin Core and the latest version of p2pool from Github. There are no fancy settings, altcoins, weird configuration files or other stuff being run on these machines to interfere with their reliability or performance. As far as possible with current Bitcoin software these should be rock solid.

In addition each machine checks once a minute that the bitcoind and p2pool nodes are running. Should either bitcoind or p2pool crash unexpectedly then the server will automatically restart them.

5. The nodes will pay 0.5% of returns to Forrest, the developer of p2pool, to ensure he can continue to support and develop the software we rely on.

6. The nodes run a stock bitcoin configuration. No abusive block sizes or non-standard relaying policies etc. The aim is to mine and benefit the bitcoin network rather than try to game the system for an extra satoshi or two.
 

The downsides:

7. Bitroute will collect a 0.5% fee from miners to pay for the service.

8. As with all PPNS/p2pool nodes you'll need to mine for about a day until your proportion of payouts starts to reach its full potential.


How:

If you're interested please point your miner (with long polling connections if possible) to whichever of these machines is closest to you (they respond to a ping so feel free to measure):

newark.bitroute.io:9332

london.bitroute.io:9332


You can also see their individual stats by pointing your web browser at the addresses above as usual.


If you have any concerns or suggestions on what would make this p2pool node more appealing just please let me know.


Thanks
Paul