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

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Meuh6879 on August 03, 2015, 05:32:27 PM

if the difficulty is too high, when you have an HW error ... you loose more than when the difficulty is adequat to your power.

That's incorrect. Adjusting diff has zero influence on the significance of hardware errors. Diff is mostly of cosmetic significance, and even more so on p2pool.

Meuh6879

legendary

Activity: 1512

Merit: 1012

if the difficulty is too high, when you have an HW error ... you loose more than when the difficulty is adequat to your power.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: Meuh6879 on August 03, 2015, 04:25:21 PM

Quote

I`m assuming that if I switch node, the payout should, initially at least, be the same ?

no because each node emit his difficulty ...
that why i prefer run a full node to have my (little) associate difficulty inline with my power mining machine.

That's not correct. Your expected payout should have very little variance when switching nodes. Each node keeps a copy of the share chain, and your expected payout is based upon the weighted shares you've submitted that are in the payout list. The only differences you'd see between nodes would be if the nodes are working on a different set of transactions to create a block, and the transaction fees associated to them differed.

Meuh6879

legendary

Activity: 1512

Merit: 1012

Quote

I`m assuming that if I switch node, the payout should, initially at least, be the same ?

no because each node emit his difficulty ...
that why i prefer run a full node to have my (little) associate difficulty inline with my power mining machine.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Their stats are completely off. All of the miners on my node report considerably lower on this node than it does on my own. A miner I have on OgNasty's pool shows higher on this node than it does on Nasty's. No clue what's going on with their stats reporting but it sure as hell doesn't match any other node.

For example, take miner 1AckkfhXexaVqgg5Xc6dmidqmnKQRBbBw2 (a miner on europe.p2pool.co):

On http://europe.p2pool.co:9332/current_payouts it shows an expected payout of 1.02512013BTC
On windpath's node that same miner shows 0.49956312BTC
On my node that miner shows 0.49979125BTC

Now take a miner on my node 14hqYFqU9B8FzkQboDPjKsiyPs1B8Wf1ZB:

On that node it shows 0.03165553BTC
On windpath's node it shows 0.05680994BTC
On my node it shows 0.05683253BTC

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: vulgartrendkill on August 03, 2015, 02:11:48 PM

hey there folks,

I`ve just started using p2pool in the last few months, and I`m really wishing I had started earlier. Anyways, I`m currently using http://europe.p2pool.co:9332/static/, and looking at the stats for the various miners, some look way off what I am used to seeing for payouts including mine. When I connect to a different node the `predicted payout` reduces to more in line with what I have come to expect each block.

I`m assuming that if I switch node, the payout should, initially at least, be the same?

Is this node maybe a little broken or just incredibly generous (not really possible???)?

Maybe i`m just not understanding P2pool well enough?

Thanks

The expected payout at any given time can change (usually slightly) based on the transaction fee's expected to be included that are in a given nodes mempool.

I looked at a few random miners from that node, and it is indeed reporting significantly higher then it should for all of them.

After digging around a little bit it would appear that all that node's miners are earning more then they should, while miners from other nodes are all earning less.

http://europe.p2pool.co:9332/current_payouts

I'd like someone else to take a look and confirm before I start throwing wild accusations around, but this seems way off to me.

vulgartrendkill

hero member

Activity: 518

Merit: 500

hey there folks,

I`ve just started using p2pool in the last few months, and I`m really wishing I had started earlier. Anyways, I`m currently using http://europe.p2pool.co:9332/static/, and looking at the stats for the various miners, some look way off what I am used to seeing for payouts including mine. When I connect to a different node the `predicted payout` reduces to more in line with what I have come to expect each block.

I`m assuming that if I switch node, the payout should, initially at least, be the same?

Is this node maybe a little broken or just incredibly generous (not really possible???)?

Maybe i`m just not understanding P2pool well enough?

Thanks

notbatman

legendary

Activity: 2212

Merit: 1038

The weekend has arrived and as usual my micro-mining operation has come under attack. Also as usual my miner was being luckier than normal when the attack hit. It lasted for 15 hours between 6 AM and 9 PM exactly until my payout fell back within the normal range.

I'm unable to figure out how they shaved off 200 GH/s, the last time I lost GH/s I was mining DOGE on my GPUs and it was a man-in-the-middle attack redirecting the hashing to Switzerland and a week later to Puerto Rico, this however is not a MitMA. The goal of the attackers seems to be to force my luck down and not to steal any hashing power, very odd.

EDIT:

After some poking around I've found my error rate jumped from 0.0003% to 0.0004%, this is the first time I've ever seen it at 0.0004%.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: yslyung on August 02, 2015, 01:42:44 AM

guys, anyone care to share merge mine lines for i0c & ixc configs ? can't seem to get it to work.

ixc seems to be synching but i0c says no block source available.

also what are the ports for ixc & i0c ?

TIA

now whereistheBLOCK ?

IXC:

rpcport=8338
port=8337

But there are no more IXCoins to mine Sad

I0C:

rpcport=7338
port=7337

Block is on it's way Cheesy

yslyung

legendary

Activity: 1500

Merit: 1002

Mine Mine Mine

guys, anyone care to share merge mine lines for i0c & ixc configs ? can't seem to get it to work.

ixc seems to be synching but i0c says no block source available.

also what are the ports for ixc & i0c ?

TIA

now whereistheBLOCK ?

Meuh6879

legendary

Activity: 1512

Merit: 1012

No ... but this week, we (i ?) have a problem ... (0,000001 spam ?)

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Does anyone out there in p2pool land know what this means?:

Code:

2015-07-31 17:03:20.612059 > Merged block submittal result: time-too-new Expected: True
2015-07-31 17:03:21.167570 > Merged block submittal result: time-too-new Expected: True
2015-07-31 17:03:22.272490 > Merged block submittal result: time-too-new Expected: True
2015-07-31 17:03:22.763514 > Merged block submittal result: time-too-new Expected: True

EDIT: Never mind, found out it's a coin issue & not p2pool

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Another 2 blocks within 24 hours - excellent considering the hash rate is still quite low

yslyung

legendary

Activity: 1500

Merit: 1002

Mine Mine Mine

hmmm, i know about the p2pool share diff which adjust dynamically if i dont add the "/" after btc add.

i'm saying that p2p does not adjust individual worker diff not the share diff.

i have more than 1 miner mining at the node but p2p cmd window shows only 1 worker not like before the update, it shows individual workers. logically it should show the number of workers with their individual stats.

for now i'm setting the worker diff manually as it does not adjust it automatically & share diff to minimum.

eg. "btc_add/1=1000" according to the miners hashrate output.

what i shappening now is that all other workers are at different hashrate so p2p should be adjusting them individually for the workers diff & share diff if left on default. but it is only showing 1 worker doing it's job and all of the workers are at the same worker diff & share diff. all workers are using different btc add & their hashrate are different too.

sorry for the confusion if there's any.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: yslyung on July 29, 2015, 03:18:42 AM

i see only 1 worker in the cmd window but i have 3 other workers total of 4 different btc addy mining at my node. if i do not set diff manually, all of the 4 different miners diff will be the same following the btc add with the highest hashrate/diff.

eg.

"New work for worker! Difficulty: 12192.630174 Share difficulty: 5341839.751636 Total block value: 25.019255 BTC including 100 transactions"

this started since the update. before it will show 4 workers work in the cmd window & their individual diff assigned automatically.

before eg.

New work for worker! Difficulty: xxx Share difficulty: 5341839.751636 Total block value: 25.019255 BTC including 100 transactions
New work for worker! Difficulty: xxx Share difficulty: 5341839.751636 Total block value: 25.019255 BTC including 100 transactions
New work for worker! Difficulty: xxx Share difficulty: 5341839.751636 Total block value: 25.019255 BTC including 100 transactions
New work for worker! Difficulty: xxx Share difficulty: 5341839.751636 Total block value: 25.019255 BTC including 100 transactions

"xxx" = to p2pool auto assigned diff to respective miner's hashrate, obviously higher hashrate higher diff & vice versa.

anyone else experiencing/noticed the same issue ?

running on core v0.11 64 bit win 7 64 bit

Your node adjusts the share difficulty dynamically. As your node hash rate increases, the share difficulty also increases. Because your shares are of a higher difficulty, they are weighted more, and thus are worth more BTC each than the minimum difficulty share. Conversely, as your node's hash rate decreases, the share difficulty decreases until it hits the network share minimum difficulty.

You can avoid this by manually setting your share difficulty using the "/" parameter:

Code:

BTC_ADDRESS/xxx

where xxx is some number. If you want to guarantee minimum share difficulty, you can set that to 1 - which will in turn mean your worker will submit network minimum difficulty shares.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

P2Pool node is regulating own diff to not get more that 1 response per second.
If all your workers have set lower diff that this - it will raise it anyway.

yslyung

legendary

Activity: 1500

Merit: 1002

Mine Mine Mine

i see only 1 worker in the cmd window but i have 3 other workers total of 4 different btc addy mining at my node. if i do not set diff manually, all of the 4 different miners diff will be the same following the btc add with the highest hashrate/diff.

eg.

"New work for worker! Difficulty: 12192.630174 Share difficulty: 5341839.751636 Total block value: 25.019255 BTC including 100 transactions"

this started since the update. before it will show 4 workers work in the cmd window & their individual diff assigned automatically.

before eg.

New work for worker! Difficulty: xxx Share difficulty: 5341839.751636 Total block value: 25.019255 BTC including 100 transactions
New work for worker! Difficulty: xxx Share difficulty: 5341839.751636 Total block value: 25.019255 BTC including 100 transactions
New work for worker! Difficulty: xxx Share difficulty: 5341839.751636 Total block value: 25.019255 BTC including 100 transactions
New work for worker! Difficulty: xxx Share difficulty: 5341839.751636 Total block value: 25.019255 BTC including 100 transactions

"xxx" = to p2pool auto assigned diff to respective miner's hashrate, obviously higher hashrate higher diff & vice versa.

anyone else experiencing/noticed the same issue ?

running on core v0.11 64 bit win 7 64 bit

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: forrestv on July 25, 2015, 11:25:18 PM

Quote from: K1773R on July 23, 2015, 11:25:57 AM

Quote from: CartmanSPC on July 23, 2015, 01:55:30 AM

Was reviewing the code and came across this one part:

https://github.com/forrestv/p2pool/blob/master/p2pool/data.py#L152

Question: Why limit it to "50 kB of new txns/share"?

i even contacted you about that bug months ago Wink

was asking forrestv about it, but he didnt respond. created a hackish fix in my repo.

It's limited to prevent DoS attacks on P2Pool by e.g. making a bunch of fake transactions and then forcing them to be relayed across the entire P2Pool network. With this limit, an attacker can only force every other P2Pool node to download, at most, 50kB per share the attacker mines.

Given that 100kB transactions are possible, it should probably be 100kB, not 50kB, but it doesn't have much of an effect otherwise, since 50kB/share is comparable to the maximum transaction throughput allowed by Bitcoin (500kB/block).

K1773R, your "hackish fix" will result in your shares being orphaned if it ever results in differing behavior. The contents of the generate_transaction function are used to determine consensus, so if your version acts different, other nodes will see your shares as invalid.

Good that we talk about it now. When i was still mining BTC with p2pool, i wondered why not all of my (sometimes bigger than 100kB) would be included in p2pool blocks. It didnt really bother me back then, as some other pool would mine them.
I think raising it (not as high as my hackish fix) would be a good addition to a future hardfork.

Im absolutely aware that i would get my shares rejected. I wasnt using it for BTC.
I wanted to mine the huge ANC stuck txs, so i had to create my own p2pool and set the limit higher.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Thanks for the detailed reply, forrestv! I appreciate that you've become more active in this thread again. It's always nice to have the guy who wrote the code explaining it, rather than the rest of us trying to reverse engineer it in an effort to provide an explanation.

forrestv

hero member

Activity: 516

Merit: 643

Quote from: K1773R on July 23, 2015, 11:25:57 AM

Quote from: CartmanSPC on July 23, 2015, 01:55:30 AM

Was reviewing the code and came across this one part:

https://github.com/forrestv/p2pool/blob/master/p2pool/data.py#L152

Question: Why limit it to "50 kB of new txns/share"?

i even contacted you about that bug months ago Wink

was asking forrestv about it, but he didnt respond. created a hackish fix in my repo.

It's limited to prevent DoS attacks on P2Pool by e.g. making a bunch of fake transactions and then forcing them to be relayed across the entire P2Pool network. With this limit, an attacker can only force every other P2Pool node to download, at most, 50kB per share the attacker mines.

Given that 100kB transactions are possible, it should probably be 100kB, not 50kB, but it doesn't have much of an effect otherwise, since 50kB/share is comparable to the maximum transaction throughput allowed by Bitcoin (500kB/block).

K1773R, your "hackish fix" will result in your shares being orphaned if it ever results in differing behavior. The contents of the generate_transaction function are used to determine consensus, so if your version acts different, other nodes will see your shares as invalid.

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