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

Well when recoding p2pool, It would be Nice to solve the "payload too long" issue as well.

Does somebody know how to deal with this? Huh

Please check this post: https://bitcointalk.org/index.php?topic=18313.msg10164796#msg10164796

Roll Eyes

What is Your Bitcoind GetBlockTemplate Latency? Has You p2pool node external IP to see stats?

Thanks for the reply!

Well my stats looks like this:

Code:

P2Pool Status
Local rate 155.77 GH/s (DOA 3.67 GH/s / 2.35%) Shares Total: 2 (Orphan: 0, Dead: 1, Unknown: 1)
Global pool rate 1.93 PH/s (DOA 321.61 TH/s / 16.67%) Share difficulty 6,707,631.61
Current block value Expected time to share 2d 3h 22m 33 s
Total node payout if block found NOW Expected time to block 1d 3h 11m 10 s
Node peers [in] 2 / 30 [out] Node uptime 2d 6h 35m 22 s
Node p2pool version 13.5-73-g12ca9d8-dirty Protocol version 1300
Node efficiency 60.00% Node getwork latency 305 ms
Node fee 0% Node donation 0%

Bitcoin Status
Network rate 303.41 PH/s Blocks 339,372
Current block 998,775 bytes / 1,600 txs Block difficulty 43,971,662,056.08958
Hashes to win 9.22 EH Block probability per GH 5.295015761671106e-12%
Total Bitcoins Expected time to block 0h 0m 30 s
Exchange rate Block interval 0h 10m 30 s
Connections [in] 12 / 523 [out] Node uptime 2d 6h 37m 53 s
Node bitcoind version 99900 Protocol version 70002
Relay fee Peer latency 675 ms

I assume my Bitcoind GetBlockTemplate Latency is 675ms, right? From what I've read, the latencies are OK and they are stable when the "payload too long" error is not occurring. Only when the error comes up in the console of p2pool then those latencies are indeed skyrocketing. As I understand from the logs and statistics this payload error does not look like a cause from latencies, but latencies are the symptoms of the payload error. So where all the sudden arises this payload error from? Is it the "maxblocksize" of Bitcoind Core which is 1MB? Because the payload error is always in combination when the blocktime between blocks were +10mins (and +2000 transactions). Get the idea the problem comes from that direction.

Any thoughts?

Yes.
1) Switch to latest p2pool version.
git clone https://github.com/forrestv/p2pool
2) to limit outgoing/incomming connections of p2pool use this settings:
--max-conns 6 \
--outgoing-conns 6 \
3) use 0.9.4.0 bitcoin core version with bitcoin.conf like this (nothing more is necessary):
server=1
rpcuser=your_rpc_user
rpcpassword=your_rpc_password

Thanks for the tips. I have the latest p2pool and bitcoind code and have limited my incoming and outgoing p2pool connections. However, my bitcoin.conf file does set blockmaxsize, minrelaytxfee, maxconnections, blockminsize, blockprioritysize, and mintxfee. Do you believe that one of those settings could cause this issue within p2pool?

Do You know the reason for each one parameter in Your bitcoin.conf file? If no, or they are not really necessary from very good reason, remove them. Give it a chance to work. Wink