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

Use something like the "balance" program to do TCP load balancing between multiple P2Pool instances. You'll have to start two separate P2Pool instances listening on different worker ports, then use balance to make a public port that round-robins between them.

The fee is probabilistic - 2% of shares will go to you, not 2% of every share, so you're probably just unlucky at the moment.

Load balance just like an httpd

Hmm. Can you give me more info about load-balancing? The only things I found about it are load-balancing the network connection, not 2 instances of a process.
Also, is it normal that the pool is finding valid shares but Payout if a block were found NOW is stuck at 0, even though fee is set to 2%?

Master for now. newshare will be merged in and released very soon.


Yes, I did. It looked like all the open files were sockets from miners, so there may not be anything you can do. Do you expect to have hundreds of simultaneous connections from miners? If so, you might want to look at load-balancing over multiple P2Pool instances. If not, someone may be attacking your node by making hundreds of connections to it.

Hey, did you get my private message?

Are we supposed to be using the newshare branch from forresv's github or the main one?

Nothing. As long as he doesn't have more than 50% of the P2Pool hashrate he is giving us free coins. If he doesn't want to, he should read the guide in my signature.

So what do we want him to do?   Connect to more nodes?   

getting close to 1thash!

Maybe he is hitting full power for 10 sec every 20 sec? ;]
Joking, but it is all about luck. Higher latency means that his shares will be "punished" each block.
How fast he can create 2 shares in row depends on his power and how good he is connected to network.

But his probability to find a share faster than others is only 33%, and about 11% for finding two shares before the rest. If he fails, his shares will be orphaned. As a result, he harms himself more, just as planned!

Easy. He just need found 2 shares in row faster than rest of nodes.
share chain:
S1
S2...
SaSbScSd your Sb is orphaned
SeSfSg Se is orphaned too
He got 4 shares, 2 other orpahned in proecess. Because of high latency he is not aware of other shares.

Yes please! How a high-latency miner with 33% total hashrate can decrease other's efficiency?

two more examples, checking .. 10 minutes later, i guess

P2Pool > Share cf9f191e
Parent: c3435999
Time first seen: Thu Jul 04 2013 07:58:03 GMT-0500 (Central Daylight Time) (1372942683.824745)
Payout address: 1CdYbiq38Qaah942iZHiRBJGeDpPbzBVnQ

orphaned by:

P2Pool > Share 0381e766
Parent: c3435999
Time first seen: Thu Jul 04 2013 07:58:05 GMT-0500 (Central Daylight Time) (1372942685.644919)
Payout address: 1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX

P2Pool > Share ceb6366f
Parent: 0381e766
Time first seen: Thu Jul 04 2013 07:58:13 GMT-0500 (Central Daylight Time) (1372942693.886554)
Payout address: 1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX

and

P2Pool > Share d910f792
Parent: c3435999
Time first seen: Thu Jul 04 2013 07:58:04 GMT-0500 (Central Daylight Time) (1372942684.812593)
Payout address: 1MAv44YHbeh9mt3tHUdxDqG7J8acjA9byh

orphaned by:

P2Pool > Share 0381e766
Parent: c3435999
Time first seen: Thu Jul 04 2013 07:58:05 GMT-0500 (Central Daylight Time) (1372942685.644919)
Payout address: 1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX

P2Pool > Share ceb6366f
Parent: 0381e766
Time first seen: Thu Jul 04 2013 07:58:13 GMT-0500 (Central Daylight Time) (1372942693.886554)
Payout address: 1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX

...

well, the one share every 30 seconds would help.  should be implemented asap

and two seconds is a long time

*************

ed: i dunno, 5 minutes later?

P2Pool > Share 62cb0c45
Parent: f5b92a74
Time first seen: Thu Jul 04 2013 08:14:00 GMT-0500 (Central Daylight Time) (1372943640.972359)
Payout address: 1GLJUmBLH83dbEj5GvbFTyhsJrjUaFV1jH

orphaned by (6 seconds, lol):

P2Pool > Share 7b374ec9
Parent: f5b92a74
Time first seen: Thu Jul 04 2013 08:14:06 GMT-0500 (Central Daylight Time) (1372943646.213323)
Payout address: 1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX

P2Pool > Share 3d593a0f
Parent: 7b374ec9
Time first seen: Thu Jul 04 2013 08:14:06 GMT-0500 (Central Daylight Time) (1372943646.210475)
Payout address: 1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX

and

P2Pool > Share 0928924a
Parent: 095962f9
Time first seen: Thu Jul 04 2013 08:12:24 GMT-0500 (Central Daylight Time) (1372943544.504013)
Payout address: 1GPFgDFABseWT1Mp8J7pxQkNooKrKmKNHb

orphaned by (this one should have been DOA anyway, but just including it since it would have been orphaned regardless):

P2Pool > Share b7be01ca
Parent: 095962f9
Time first seen: Thu Jul 04 2013 08:12:23 GMT-0500 (Central Daylight Time) (1372943543.308732)
Payout address: 1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX

P2Pool > Share f5a3278b
Parent: b7be01ca
Time first seen: Thu Jul 04 2013 08:12:44 GMT-0500 (Central Daylight Time) (1372943564.581696)
Payout address: 1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX

..

check the verified heads, you'll probably find at least one

ah, 15 minutes later.

This seems like a problem with p2pool, not with the miner.  We want more hashrate, but not too much in one spot?

M

because it decreases efficiency of other people using p2pool when someone is using inefficient connection and is able to put out 33% of hashrate?

does it need further explaining?

ok, so i just decided to check the headers for the hell of it

P2Pool > Share 9c6eb9d6
Parent: ded30170
Time first seen: Thu Jul 04 2013 07:36:10 GMT-0500 (Central Daylight Time) (1372941370.955215)
Payout address: 1MAv44YHbeh9mt3tHUdxDqG7J8acjA9byh

trumped by:

P2Pool > Share ff119beb
Parent: ded30170
Time first seen: Thu Jul 04 2013 07:36:11 GMT-0500 (Central Daylight Time) (1372941371.258362)
Payout address: 1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX

P2Pool > Share e82be749
Parent: ff119beb
Time first seen: Thu Jul 04 2013 07:36:13 GMT-0500 (Central Daylight Time) (1372941373.962954)
Payout address: 1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX

so 1 out of 4 headers that happened to be shown

the answer to your question is

no, it wouldn't change anything, unless this amount was higher than the share difficulty

i.e. MrT/500+500, wouldnt matter.  MrT+2000 would, if the share difficulty was under 2000

the hash rate reported on your stats will be bizarre (that's what it uses those small ones for), but in the grand scheme of things you'd still get just as many shares

Why would it be disconcerting?  p2pool is really small.  there are filthy rich miners who have more than the entire hash rate of p2pool.

M

i just turned my stuff back to p2pool for a final hurrah i suppose you could say, before i shut everything down

but doesn't anyone find it concerning that someone has 33% of the hashrate?  i also was unable to locate the IP address of this person, so they're probably behind a firewall, without many outgoing connections, judging from the other nodes I checked (IP address reported as relaying their share is quite a spread)

just found it curious since i've gotten 2 orphans out of 6 already,  both because of the double share from 1Nasty

although i guess it could be partally attributed to using a US server

If you double the difficulty then you half the number of shares you submit, but each share is worth double. Because you're submitting less shares, the variance you will see will increase.