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

[fire000]

Lmao how hard is it to understand that /0 is a manual override code for diff....     It can only be set above the current diff to have any effect eg if the current diff is say 6 mil a share it need to be set above this to see any effect on diff.....     If it is set under this value of 6 mil it defaults to the current share diff ........    Weather you set it at 5 mil 4 mil 3.5 mil or 0 as the value is less than the min current diff in this case of 6 mil  it not rocket science and the proof is ya only got to test it and take note of the diff your miner is set at to see it in effect 1st hand DO I HAVE TO SCREEN SHOT IT to highlight it too you that the / number if less than the current share diff it will default to the current min share diff of the node as ya do not know where to find the diff reading on ya miner ??

Ps does not need to look at code etc to know you can not set a diff under the current share diff if you do it will default to current share diff hence the comment above

You have yet to provide proof of your statements.  I have shown you where the code explicitly sets the difficulty to 2**256-1 if you set the difficulty to /0.  Show me where it doesn't.

I understand quite well that /0 or /100 or /10000000 is a manual override for share difficulty.  What I want YOU to show to me is proof of your statement

If it is set under this value of 6 mil it defaults to the current share diff.

Show me that.  Not by screenshots.  By the CODE.

Your next statement:

Weather you set it at 5 mil 4 mil 3.5 mil or 0 as the value is less than the min current diff in this case of 6 mil  it not rocket science and the proof is ya only got to test it and take note of the diff your miner is set at to see it in effect 1st hand DO I HAVE TO SCREEN SHOT IT to highlight it too you that the / number if less than the current share diff it will default to the current min share diff of the node as ya do not know where to find the diff reading on ya miner ??

That's just outright incorrect.  Your miner does NOT show the value you set in /0 or /100 or /100000.  Your miner shows the PSEUDO share value you defined using +0 or +100 or +1000.  Your miner has absolutely no concept of anything set with using /#.

I am not going to go digging through code when it common knowelge you can not put a share in that not above the share value and be credited for it as a paying share......   hence that statement above if your share is not over that current share diff you not going to be credited with it as a paying share are ya ??       So it defaults to the current share diff value not rocket science  Ps next time ya quote something quote the full statement not part of it

It can only be set above the current diff to have any effect eg if the current diff is say 6 mil a share it need to be set above this to see any effect on diff... If it is set under this value of 6 mil it defaults to the current share diff

You are obviously failing to understand.  Your miner has no knowledge whatsoever of you setting a share difficulty of /0 or /256 or /245982345.  None.  Whatsoever.  Your miner shows you the PSUEDO share value you have set using +0 or +256 or +1000.

What I am stating is the following:

If you set your share difficulty to /0, that then gets translated by the p2pool code to set your desired share target to be 2**256-1.  If you set your share difficulty to ANY other value, p2pool will evaluate that value and attempt to add it to the share chain.  It will not be added if your desired share target is LESS than the required difficulty to actually get on the chain in the first place.  If you set your share difficulty to something LARGER than the p2pool minimum, when you find a share at least your target difficulty it WILL be added to the share chain (assuming it's not orphaned or DOA), and its payout value WILL be weighted appropriately.  This is also proven in the code.

I want you, or anybody, to prove to me that setting /0 somehow gets translated into p2pool minimum difficulty.  That's what I'm looking for.  Proof.  The ACTUAL CODE that does this.  I have shown the ACTUAL CODE that supports my theory.  You have given nothing but incoherent blathering about how you're right and everybody knows it.

Let me put it another way.  I WANT to be proven wrong.  I WANT to be shown where I'm incorrect.  Do that.  Prove me wrong.

What part are you NOT UNDERSTANDING and you have said it your self above IF that diff is set lower that the share diff to get to the chain it does what ?   It defaults to the min share value to get to the chain to stop people from putting in under target shares you have said this yourself.....    So again /0 or /100 or /1000 any number under the current share value will see it set to the min value to put a share into the chain to stop undervalue shares getting to the chain which = what oh that would be min diff

[fire000]

so basically as said miles back in this whole topic lol

also further to this current talk in here lol the /0 command sets to the bear min of the share diff on the miner as per the node diff so if the diff is 5mil for example it set the diff to 5mil   if it 7mil it sets to 7mil....     

But on saying this that /0 command can be used to set a diff higher than the min diff only for example if the diff was 5mil    you can set ya rig to a diff via the / number command to say 7.5 mil   eg /7500000   if this set under the current share diff on the nodes it defaults to the min diff on the node eg if you set it for 2.5 mil for example and the current diff was 5mil for a share it would default to the min diff of 5mil as that 2.5mil setting is below the current diff of 5mil

[jonnybravo0311]

so basically as said miles back in this whole topic lol

also further to this current talk in here lol the /0 command sets to the bear min of the share diff on the miner as per the node diff so if the diff is 5mil for example it set the diff to 5mil   if it 7mil it sets to 7mil....     

But on saying this that /0 command can be used to set a diff higher than the min diff only for example if the diff was 5mil    you can set ya rig to a diff via the / number command to say 7.5 mil   eg /7500000   if this set under the current share diff on the nodes it defaults to the min diff on the node eg if you set it for 2.5 mil for example and the current diff was 5mil for a share it would default to the min diff of 5mil as that 2.5mil setting is below the current diff of 5mil

/0 behaves differently than /1.  That's what the code says, and what I'm stating.  By setting it to /0, the CODE translates that to 2**256-1.  If you set it to /1, the code sets the difficulty to min(int((0xffff0000 * 2**(256-64) + 1)/difficulty - 1 + 0.5), 2**256-1).  See the difference?  0 means 2**256-1.  1 means evaluate the minimum of int((0xffff0000 * 2**(256-64) + 1)/difficulty - 1 + 0.5) and 2**256-1.  Look at both statements if you just isolate this part of the code and execute it.  Let me explain it line by line:

Code:

def difficulty_to_target(difficulty):
    assert difficulty >= 0
    if difficulty == 0: return 2**256-1
    return min(int((0xffff0000 * 2**(256-64) + 1)/difficulty - 1 + 0.5), 2**256-1)

Line 1 - defines the difficulty_to_target function.  It takes a single parameter - the difficulty
Line 2 - makes sure the difficulty passed is 0 or larger
Line 3 - if the difficulty equals 0, return a value of 2**256-1
Line 4 - if the difficulty equals ANY OTHER NUMBER, return the value that is the minimum of the two numbers.

Pay very close attention to the bolded part.  Therefore, if you set your miner like this:

ADDRESS/0

When that function is called, difficulty equals 0.  Therefore, it returns 2**256-1.

If you set your miner like this:

ADDRESS/1

When that function is called, difficulty equals 1.  Therefore, it returns the minimum of int((0xffff0000 * 2**(256-64) + 1)/difficulty - 1 + 0.5) and 2**256-1.

Do you understand this?

[CartmanSPC]

Someone go mine on http://minefast.coincadence.com with address/0 and see what it returns for your p2pool share diff.

You can see the result by going to your address details page here and looking at what is says under "Miner Share Difficulty":
http://minefast.coincadence.com/miner.php?id=[address]

Ex:
http://minefast.coincadence.com/miner.php?id=1Po4Fa4drFtaDZ2Rr51mVs26L9bADJqZBG

[jonnybravo0311]

I've done precisely that on my own node.  Which is why I started this whole thing to begin with... I want somebody to show me where in the code this happens.

Setting difficulty to /0:

Code:

2014-08-08 14:20:45.767005 New work for worker! Difficulty: 565.596240 Share difficulty: 5424434.245682 Total block value: 25.242381 BTC including 1461 transactions

Setting difficulty to /10000000:

Code:

2014-08-08 14:22:44.088361 New work for worker! Difficulty: 506.191697 Share difficulty: 10000044.116454 Total block value: 25.008233 BTC including 73 transactions

As you can see, it is obviously treating /0 the same as /1, /2, /256, /anything_under_p2pool_minimum.

So... now that I've spent freaking hours looking at this and arguing that it behaves differently, it has finally dawned on me why.  I'm thinking in terms of the RAW number value that is set.

Yes, the number is indeed set to 2**256-1 if you set your difficulty as /0.  However, that 2**256-1 means it's the EASIEST share, not the hardest.

Hopefully this answers it once and for all for everyone (ok, well it clears it up for me anyway), and I'm sorry I spent pages of this thread figuring that out.

[CartmanSPC]

It's all good man...were all here to help and support each other  

[jonnybravo0311]

It's all good man...were all here to help and support each other  

You want to know when if finally clicked?  When I was evaluating that method.  I coded my own version and just printed results.  As expected, when I passed "0" to it, it gave me back the 2**256-1.  However, when I passed "1" to it, it then gave me some very large number as well.  When I saw that result, at first I didn't believe it, so I looked at it again, and like that proverbial lightbulb going on, I said to myself, "you freaking idiot, the larger the number the easier the share."

[bryonp]

O M G

After all that, can you advise what would be the right way to go???
/0   /1
or just leave it alone???
All of this on the ants??

Thanks...

[mdude77]

O M G

After all that, can you advise what would be the right way to go???
/0   /1
or just leave it alone???
All of this on the ants??

Thanks...

I recommend leaving it alone.

M

[PatMan]

so basically as said miles back in this whole topic lol

fire000/s0br - please go back to bigging up your own pool instead of trolling here. P2pool pays, unlike your mining.BitcoinAffiliatenetwork.com one:

I haven't been paid out by the pool for several days now, I sent a PM to s0ber last night to have a look at my account to see what's happening so far I have no reply from s0ber nor I have received any payments from the pool since 6th of AUG. Hey S0ber is the pool hacked?  

Peace  

Don't feed the troll peeps.

[fire000]

so basically as said miles back in this whole topic lol

fire000/s0br - please go back to bigging up your own pool instead of trolling here.

P2pool pays, unlike your mining.BitcoinAffiliatenetwork.com

one:

I haven't been paid out by the pool for several days now, I sent a PM to s0ber last night to have a look at my account to see what's happening so far I have no reply from s0ber nor I have received any payments from the pool since 6th of AUG. Hey S0ber is the pool hacked?  

Peace  

Don't feed the troll peeps.

Right to state something here as this guy wants to look at one comment only in there lol a number of user have reported they are been paid with no issues BUT you will also notice the admin in following comments the admin had rewritten the payout system and the USER named above has been paided as they also state themsleves SO NICE TRY

Now to the second part of this

P2pool pays unlike you mining xxxxxxx one

A simple look at stats p2 vs xxxxx pool shows that in fact the xxxxx pool is outdoing P2 earning wise as it is hitting blocks at a better strike rate than p2 with just under the hash rate of the p2 pool  PS has been testing this for a few days now hence knowning what my DIFF 1 share rate is between the two miners P2 is NO where match a normal pool share rate ya may want to look at ya diff 1 shares vs ya diiff a shares if using an ant miner    

The diff 1 shares are what ya miner is mining at on a diff 1 (the correct earning rate for ya hash)    the diffa is the shares you have been paid for you will notice that diffa number in most cases well under the diff1 number due to the high share diff on p2 when it should read very close to the diff 1 number  which in turn is seeing normal pools killing p2 for earnings as ya not hitting paying shares on p2 enough to line up to the diff1 on your miner.    

To put this in sample form if your miner was to hit say 16 mil diff1 shares a day that diffA rate needs to be around that 16 mil as well if it is say 6.5 mil  only your rig had under paid for the day (happens alot on p2)   if it 16 mil you are on par with the rigs earnings .............   ESP on small rigs


Also hardy call it trolling when it was a fact state re the /0 command that it defaults to the min share diff as highlighted in the posts above this one so no matter if you use the /0 command or not it will make no diffence in you rig share unless set above the min share diff point as also highlighted above and stated pages back by myself...    So nice try....    These are just cold hard facts which anyone can test and see the results 1st hand

[fire000]

just thinking about this /0 command I have a question re it if one was to set that at say 19.7 g so basically the current BTC diff how does that treat the payouts........    Cause in theory if a user was to hit  a 19.7g share (a btc block) there would only be 1 share to that block and the user should see the whole payout themselfs plus payout from the next few blocks due to the ppnls as the shares return to normal.....    so how does p2 treat this ?

As if my line is correct here there a major flaw in the P2 system which could see any big farm or a couple bring the P2 down by setting the manual overwrite to the BTC block value so therefore killing off the other normal shares for the block to the point ya would have to be hitting a btc block to be paid.........  or close to it if there was say 6 farms on p2 hitting blocks in a string as they would be grabbing all the shares and pushing that share value flying if they were set to the block value as their share rate

[cathoderay]

Woke up this morning to a nice little earner - that's 5 blocks inside 24 hours.....GET IN!!!  

there a major flaw in the P2 system

WTF do you care? You're not mining here anyway, stop trolling this thread & concentrate on your own pool, shills/fake accounts are a sad ghash.io tactic.

Ignored & Sod off.

[fire000]

Woke up this morning to a nice little earner - that's 5 blocks inside 24 hours.....GET IN!!!  

there a major flaw in the P2 system

WTF do you care? You're not mining here anyway, stop trolling this thread & concentrate on your own pool, shills/fake accounts are a sad ghash.io tactic.

Ignored & Sod off.

Lmao not trolling lol just asking a bloodly good question what to stop a couple farms from taking over the p2 network ?  Based on that flaw as if I am right here and that manual diff setting will allow for the current btc block value to be set (so grabbing all the shares for the block) they in theory could over run the P2 network to the point they play with the share value and lift that to the point no smaller miner could hit or would have a hard time hitting  over a short space of time if this is correct......

[organofcorti]

Woke up this morning to a nice little earner - that's 5 blocks inside 24 hours.....GET IN!!!  

there a major flaw in the P2 system

WTF do you care? You're not mining here anyway, stop trolling this thread & concentrate on your own pool, shills/fake accounts are a sad ghash.io tactic.

Ignored & Sod off.

Lmao not trolling lol just asking a bloodly good question what to stop a couple farms from taking over the p2 network ?  Based on that flaw as if I am right here and that manual diff setting will allow for the current btc block value to be set (so grabbing all the shares for the block) they in theory could over run the P2 network to the point they play with the share value and lift that to the point no smaller miner could hit over a short space of time if this is correct......

No. The only time that p2pool is at risk from the actions of a large miner is if that miner has > 50% of the p2pool network, regardless of share difficulty.

If you are asking for information, please do so in a less inflammatory way.

[fire000]

Woke up this morning to a nice little earner - that's 5 blocks inside 24 hours.....GET IN!!!  

there a major flaw in the P2 system

WTF do you care? You're not mining here anyway, stop trolling this thread & concentrate on your own pool, shills/fake accounts are a sad ghash.io tactic.

Ignored & Sod off.

Lmao not trolling lol just asking a bloodly good question what to stop a couple farms from taking over the p2 network ?  Based on that flaw as if I am right here and that manual diff setting will allow for the current btc block value to be set (so grabbing all the shares for the block) they in theory could over run the P2 network to the point they play with the share value and lift that to the point no smaller miner could hit over a short space of time if this is correct......

No. The only time that p2pool is at risk from the actions of a large miner is if that miner has > 50% of the p2pool network, regardless of share difficulty.

If you are asking for information, please do so in a less inflammatory way.

think ya missed the point above will try this a different way....    Lets look at the current hash on the pool

http://p2pool.info/

and lets say the top 10-15 users were set all to the current BTC block as their diff which via the manual override would they not control the share diff on P2 as they would hitting most of the blocks and grabbing all the shares due to the diff setting on their miners of the btc block??   And the higher the diff was set the higher the p2 diff would become ?

[organofcorti]

think ya missed the point above will try this a different way....    Lets look at the current hash on the pool

http://p2pool.info/

and lets say the top 10-15 users were set all to the current BTC block as their diff which via the manual override would they not control the share diff on P2 as they would hitting most of the blocks and grabbing all the shares due to the diff setting on their miners of the btc block??   And the higher the diff was set the higher the p2 diff would become ?

OK. Provide me a proof and I'll take your concerns seriously.

[fire000]

think ya missed the point above will try this a different way....    Lets look at the current hash on the pool

http://p2pool.info/

and lets say the top 10-15 users were set all to the current BTC block as their diff which via the manual override would they not control the share diff on P2 as they would hitting most of the blocks and grabbing all the shares due to the diff setting on their miners of the btc block??   And the higher the diff was set the higher the p2 diff would become ?

OK. Provide me a proof and I'll take your concerns seriously.

It a bit hard to gave proof without a farm lol.....     But if that manual diff override is able to be set at the current block diff eg 19.7g   and a user hit at that diff they in theory would be the only share for that block as the system would have to credit them all the shares to gave them the full pay out right ?   So that would mean their hit all 3000 odd shares at once YES??   Now if this was applied to all these 10 -15 miners which would be hitting a high number of the blocks they would send the diff flying due to rapid hitting of them shares


As the higher you lift that manual diff above the min share value the higher your payout is per share as it worth more than the min share eg lets say the min diff share is atm 6mil  and worth .010   to the miner<<<<    a share that was set at 12mil via the manual diff would be worth twice more than a 6mil share to a miner so their share would be .020 as they have hit x 2 min shares so they basically put 2 shares in at once which in theory effects diff straight up as the p2 would have to adjust for them 2 shares at once rather than 1

[jonnybravo0311]

think ya missed the point above will try this a different way....    Lets look at the current hash on the pool

http://p2pool.info/

and lets say the top 10-15 users were set all to the current BTC block as their diff which via the manual override would they not control the share diff on P2 as they would hitting most of the blocks and grabbing all the shares due to the diff setting on their miners of the btc block??   And the higher the diff was set the higher the p2 diff would become ?

OK. Provide me a proof and I'll take your concerns seriously.

It a bit hard to gave proof without a farm lol.....     But if that manual diff override is able to be set at the current block diff eg 19.7g   and a user hit at that diff they in theory would be the only share for that block as the system would have to credit them all the shares to gave them the full pay out right ?   So that would mean their hit all 3000 odd shares at once YES??   Now if this was applied to all these 10 -15 miners which would be hitting a high number of the blocks they would send the diff flying due to rapid hitting of them shares


As the higher you lift that manual diff above the min share value the higher your payout is per share as it worth more than the min share eg lets say the min diff share is atm 6mil  and worth .010   to the miner<<<<    a share that was set at 12mil via the manual diff would be worth twice more than a 6mil share to a miner so their share would be .020 as they have hit x 2 min shares so they basically put 2 shares in at once which in theory effects diff straight up as the p2 would have to adjust for them 2 shares at once rather than 1

Short answer is your theory is incorrect.  Even if a miner sets their share difficulty to 19.7G other miners are still finding shares and adding them to the chain.  When any miner finds a block... Either the miner who set his difficulty to 19.7G or one who hasn't, the block finder gets 0.125BTC for that share.

[fire000]

think ya missed the point above will try this a different way....    Lets look at the current hash on the pool

http://p2pool.info/

and lets say the top 10-15 users were set all to the current BTC block as their diff which via the manual override would they not control the share diff on P2 as they would hitting most of the blocks and grabbing all the shares due to the diff setting on their miners of the btc block??   And the higher the diff was set the higher the p2 diff would become ?

OK. Provide me a proof and I'll take your concerns seriously.

It a bit hard to gave proof without a farm lol.....     But if that manual diff override is able to be set at the current block diff eg 19.7g   and a user hit at that diff they in theory would be the only share for that block as the system would have to credit them all the shares to gave them the full pay out right ?   So that would mean their hit all 3000 odd shares at once YES??   Now if this was applied to all these 10 -15 miners which would be hitting a high number of the blocks they would send the diff flying due to rapid hitting of them shares


As the higher you lift that manual diff above the min share value the higher your payout is per share as it worth more than the min share eg lets say the min diff share is atm 6mil  and worth .010   to the miner<<<<    a share that was set at 12mil via the manual diff would be worth twice more than a 6mil share to a miner so their share would be .020 as they have hit x 2 min shares so they basically put 2 shares in at once which in theory effects diff straight up as the p2 would have to adjust for them 2 shares at once rather than 1

Short answer is your theory is incorrect.  Even if a miner sets their share difficulty to 19.7G other miners are still finding shares and adding them to the chain.  When any miner finds a block... Either the miner who set his difficulty to 19.7G or one who hasn't, the block finder gets 0.125BTC for that share.

But what about the share value the user has set  at a diff of  19.7 g it is worth more than a normal 6mil one in terms of payout....    If a user was to set at 19.7 g = a 25 btc value  They would have to be credited all shares for the round to match the shares worth that they had set via the manual diff ??  eg the same as the example above re the 6mil to 12 mil share where ya set a higher diff the share value rises in terms of payout value of the shares vs a lower share put in