Topic: What's going on with P2Pool NODE 73.252.200.173 [San Francisco, California] ? (Read 690 times)

Use the existing p2pool thread for support please:
https://bitcointalksearch.org/topic/1500-th-p2pool-decentralized-dos-resistant-hop-proof-pool-18313

Thank you for the reply.

Not going to that node.

I'll check it the one you mentioned.

As mentioned in p2pool.org's node scanner, its ping time is a simple HTTP request from your browser, not the ICMP ping that's used when you ping from your network using the ping command. You should follow the ICMP ping results, as that is usually a more reliable measure of latency than a browser's HTTP request.


I can't say for certain whether or not that node is good, bad, or dead. All I can say is that that node is active and open to the public, for now. If you choose to mine at that node, you would have to trust that node's operator to keep it running (and running well). This is why it is highly recommended to set backup P2Pool nodes in your miners' configuration when mining with P2Pool, so that if your primary pool goes down, your miners would failover to another P2Pool node without missing a beat.

Personally, I would not mine at that node.

If you decide to move away from p2pool.org's node, then I recommend OgNasty's NastyPool node. Better yet, if you have the required computing resources and technical know-how, set up your own P2Pool node — this frees you from having to trust a node operator.


That is up to you. I would not recommend it, though. I personally would not mine at that node.


The hashrate and efficiency statistics are blank because there are zero users there.


The pool rate is the total hashrate for P2Pool as a whole, not for the node you're looking at.

Thanks for the feedback, and in regards to the portion you responded to, I am familiar with, in general networking, outside of mining.

to be more to the point, is this a node I should switch to?

Why are some of the statistics not showing on the NODE SCANNER?

Are there concerns about the  Hash Rate & Efficiency being blank?

There are also ZERO users there

The pool rate looks interesting, right?

Pool rate: 2.63PH/s (19% DOA+orphan) Share difficulty: 712000

If the node is located physically closer to you than other nodes, then you will have a lower ping. There are simply less hops to make and less physical wire for the signal to travel through so there is less network latency. Otherwise, that node may simply have a faster internet connection and the connection between you and that node is faster than between you and other nodes.

New to mining, been running on p2pool.org for a few days now, things look good.

Started to consider to connect with another node for latency reasons, and
this node 73.252.200.173 gives me 40-50% better ping performances and as
I understand, the faster you can send/receive, the better hashing/mining performance, right?

This node is showing the following from the NODE Scanner:
Address                                                    Fee    Uptime    Efficiency    Hash rate    Users    Ping            GBTL      Version

73.252.200.173 [San Francisco, California]    0%   7.0 days   N/A            0 H/s   0           281ms   224.16 ms   unknown

The Ping Results from my network, to this node are better than 50ms which is what started to draw my attention.

i don't know as-of-yet what to be concerned about in regards to the other info, but when I click on the additional node detail, it seems
a little more interesting again.

Is this node good/bad/dead or worse?

Could I get a little help in considering this node, or another node to connect to?

P2Pool BTC

Graphs

Version: unknown 7032706f6f6c2d6d6173746572
Pool rate: 2.63PH/s (19% DOA+orphan) Share difficulty: 712000
Node uptime: 7.0 days Peers: 6 out, 18 in
Local rate: 0.00H/s (NaN% DOA) Expected time to share: Infinity years
Shares: 0 total (0 orphaned, 0 dead) Efficiency:
Payout if a block were found NOW: 0 BTC to 1Eg5ddhe5ABzXJ1inqVkjbNaoKJSUd5H3. Expected after mining for 24 hours: 0.00 BTC per block.
Current block value: 16.09807563 BTC Expected time to block: 12.8 days

Thank  you for your help and guidance here!