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

As long as you account for the roughly 12 hours for confirmation before payment, yes, it's immediate after the block is found.

I've seen other people have issues with "Failure: twisted.internet.defer.TimeoutError: in _on_discovery_timeout" in their p2pool log.  I had these messages as well.  Some people commented on system performance. There may be issues with system performance, but that is definitely not my issue.  My server is smokin' with dedicated business network line.     Anyway, it was my iptables config.  In addition to the standard bitcoind and p2pool ports, I also had to open up UDP for port 1900, both inbound and outbound.  I am still a bit confused as to why port 1900, because I think that port is for uPnP, which I'm not really using and is disabled on my router.  If it is for uPnP updates only, then I could have probably just ignored the message anyway.  And, the next time I restart the service, I will specifically set uPnP=0 to see if that stops the traffic on port 1900.  But I don't want to restart my service just for that.  Having port 1900 open does cause a bit more traffic, of course, but it's nothing to worry about unless you are already struggling with system performance.

For your reference, here is my iptables config.  I'm running both Bitcoin and Litecoin P2Pool.  My Litecoin P2Pool is using p2p port 10333, since 9333 conflicts with bitcoind.  My host is also running DNS and NTP, so those ports are open.  And I am allowing ping.  Most ports are configured with limits as minimal protection against DDoS attacks.  I know the limits won't prevent hard-core DDoS attacks.

# Generated by iptables-save v1.4.12 on Fri Sep 12 13:48:46 2014
*filter
:INPUT DROP [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:LOGNDROP - [0:0]
-A INPUT -i lo -j ACCEPT
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 8 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 22 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -p udp -m udp --dport 53 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -p udp -m udp --dport 123 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 9327 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 9332 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -p udp -m udp --dport 1900 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 9333 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 10333 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8333 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 9338 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A INPUT -j LOGNDROP
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 0 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 80 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 123 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 1900 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 443 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 8333 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 9333 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 9338 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 10333 -m limit --limit 25/min --limit-burst 100 -j ACCEPT
-A OUTPUT -j LOGNDROP
-A LOGNDROP -p tcp -m limit --limit 5/min -j LOG --log-prefix "IPTables Denied TCP: " --log-level 7
-A LOGNDROP -p udp -m limit --limit 5/min -j LOG --log-prefix "IPTables Denied UDP: " --log-level 7
-A LOGNDROP -j DROP
COMMIT

I'm not letting anything fool me here.  According to your node, the node has found a total of 7 shares since you started it.  1 of which is an orphan, 1 of which is dead.  Your node has found a share since my first reply to you (it was a total of 6 at that point).  Your expected payout is currently 0.02889951BTC.  You received 3 payouts recently (equivalent to 1 share on the chain at the time) from blocks 320161, 320165 and 320217.  320217 was the last block found by p2pool, and that was just about 18 hours ago.  When the next block is found, you will receive a payout at your address for the expected payout amount from the weighted shares you have on the chain at the time the block is found.

In the past you might have waited for days because p2pool didn't find blocks for days.  It's not because of any bug in the p2pool code, it's the nature of how the PPLNS system works.  You need to get shares onto the chain.  Until you do, you get no payout.  You could turn your node and miners off right now, and if p2pool found a block, you'd still get paid for the shares you have on the chain, and would continue to be paid every time p2pool found a block until such time as you no longer had shares on the chain.

In short, there's nothing wrong with your setup.  In fact, you're actually doing a bit better than expected in terms of shares vs. your hash rate.  As of right now, p2pool believes you're hashing at over 4TH/s based on your expected payout.

Don't let those payouts fool you. This is what happened.

I powered my P2Pool backup on my ESXi host.
Pointed my Neppy to it and got one payout, then took it down to patch P2Pool; I couldn't remember the commands.
Started P2Pool again and few hours later I got the next payment; deciding I wanted my friend to use my P2Pool I stopped P2Pool once more and removed the --fee from the start command and restarted P2Pool.
Those shares you are seeing is from the last restart point.

In the past I have seen it were I wait for days before receiving any payout or after the 2nd or 3rd day doing a shutdown/reboot of the P2Pool before it starts paying out in a timely rate, almost if there is some bug in the P2Pool code itself.

On my firewall I have both 9332 and another port open to my P2Pool server.

I used to run this when I had two Avalon's, 30 of the 333Mhs USB keys and 5 ice furys.

Gotcha... sorry, didn't read it properly I guess.  Not enough coffee yet   Looking at your node I can see that you've got a few shares on the chain and are expecting a payout when the pool next finds a block.  I can also see that you've received a few payouts already at your address, so things are working as expected.

Maybe I'm also reading your reply incorrectly here as well, but with p2pool you don't wait for days for a payout.  As soon as a block is found you get paid if you've got valid shares on the chain.  Have there been times when it's taken a while to find a block?  Sure.  That's variance for you.  I'm not entirely sure what you mean by "a bad block or something in the chain".  If the block is orphaned, then you won't get a payout for it.  Other than that case, I don't know what a "bad block" is.  Any solved block that makes it onto the BTC block chain distributes 25BTC and transaction fees.  In p2pool's case, that amount is distributed to all miners who happen to have valid shares on the share chain: 0.5% to the block finder, the remaining 99.5% to the other shares.

My site is in my tag. http://p2pool.smoothrunnings.ca:9332/

No I am just trying to make a point of asking because back before Neptune's were even being shipped there were times where we would be waiting for days for the payout to happen because of bad block or something in the chain. It was affecting everyone not matter which pool use used.

Are you saying you have 20 shares on the chain, yet have received no payout in 3 days?  Since 9/9 p2pool has found 11 blocks.  There's something wrong with your setup if your logs are saying you've found 20 shares in that time, but you've received nothing.

So if in 3 days say there has been zero payment, does this still mean no blocks were found?

Correct.  Those 20 shares will count towards your payout whenever a block is found within 24 hours of that share.  It's a rolling system, so as old shares drop off new shares will count towards new blocks.

So I if I have found 20 shares in 15 hours say and not received a single payout I guess this means a block wasn't found in 15 hours?

You're getting blocks and shares mixed up.

The entire pool rate is averaging 3.5PH/s, which means the _pool_ will solve a block on average every 9 hours at that speed.  At 3TH/s you're going to average about 1-1.5 _shares_ in that same timeframe.

The amount of shares you complete is how your payouts are determined - if you have at least one active solved share in the blockchain when a block is found (on p2pool) you will receive a payout.  Depending on the node frontend you're using that information can be found pretty easily and presented on the front page, on others it may require a little more digging.

At about 3TH/s you should expect a payout of between .02 - .03 BTC with every block at the current pool hash rate.

How long should it take t complete a block at 3TH/s? My stats say 9h but it's been 13h already, I guessing I have hit a bad block?

Thanks

So is there no formula and or rule for figuring out if the best incoming connections your own P2Pool node base on your internet connection speed?

Thanks,

...

It will be in the list on the site.

This was most likely due to the DOA share finding a block.


When a share comes in as DOA (i.e. P2Pool has moved on to a new share hash) it is still submitted to bitcoind because it might still be a valid block even though it is a dead share. In my experience it does not happen often, but it happened today...

Don't forget my front end down below in my sig

I am bit confused.

I removed the --fee from my server start string, it shows a fee of 0% on my site yet I just got a payout, my miner wallet got 0.004x and when I checked my p2pool wallet I see a payment of 0.008x does this mean the fee system is still working or am I not understanding something?

Thanks,

Bonus 

Valid Block 320165 found from DOA share.

(note: it will not show up in most front-ends but if you had active shares you were paid)

Until next Thursday my focus is getting the new p2pool.org up and running, after that I will direct all my attention to the open source version of the Coin Cadence front-end. I hope to have a beta version up by October 1st.

In the mean time you may want to check out these popular front ends:

Node Status: https://github.com/johndoe75/p2pool-node-status
Example: http://minefast.coincadence.com:9332/static/node-status/

Extended:https://github.com/hardcpp/P2PoolExtendedFrontEnd
Example: http://minefast.coincadence.com:9332/static/extended/

Edit: For Bitcoin forrestv's version is what you want.