Author

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

sr. member
Activity: 379
Merit: 250
Welcome to dogietalk.bs
Woke up this morning to a nice little earner - that's 5 blocks inside 24 hours.....GET IN!!!  Grin

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.
member
Activity: 98
Merit: 10
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 Huh?

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
member
Activity: 98
Merit: 10
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.
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  Wink

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 Smiley  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


hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
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  Wink

Don't feed the troll peeps.
legendary
Activity: 1540
Merit: 1001
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
member
Activity: 85
Merit: 10
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...

legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
It's all good man...were all here to help and support each other  Grin
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."
legendary
Activity: 1270
Merit: 1000
It's all good man...were all here to help and support each other  Grin
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
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.
legendary
Activity: 1270
Merit: 1000
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

legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
so basically as said miles back in this whole topic lol

Quote
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?
member
Activity: 98
Merit: 10
so basically as said miles back in this whole topic lol

Quote
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


member
Activity: 98
Merit: 10
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 Huh??

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
Quote
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:
Quote
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 Huh??
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 HuhHuh??       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
Quote
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 Huh?   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 Smiley
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
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 Huh??

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
Quote
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:
Quote
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 Huh??
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 HuhHuh??       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
Quote
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.
member
Activity: 98
Merit: 10
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 Huh??

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
Quote
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:
Quote
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 Huh??
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 HuhHuh??       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
Quote
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

full member
Activity: 168
Merit: 100
For some reason this new difficulty increase has been great for my luck. I have been finding blocks left and right.
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
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 Huh??

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
Quote
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:
Quote
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 Huh??
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 /#.
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Unless you are running 1th rigs forgot p2pool as you will earn no where the amount you would on a normal pool...
I don't necessarily agree with this statement, although I don't have empirical data to back it up.  Hashrate is hashrate, it should even out in the end.  Even if you don't get a share today in this block, your share will count for the next block and you would get a payout then.

This is regularly stated here, however it only holds true *if* bitcoin difficulty remains the same.  Which it doesn't, so therefore it's false.

If your luck averages out over the difficulty period, then yes, it will.  However, the lower your hashrate, the less likely it is to average out over a fixed period of time (a given difficulty period).  The higher the difficulty, the worse it gets.

M
While your statement about rising difficulty is true, the application of it here is not addressing the statement made by fire000.  His statement implied a difference between using a dragon miner at 1TH/s vs using a combination of other miners to also achieve that 1TH/s.  In this sense, hash rate is hash rate.  If you have 500 Antminer U2s all hashing at 2GH/s each, or 5 over clocked S1s hashing at 200GH/s each, or 1 dragon hashing at 1TH/s, you still have 1TH/s mining.

Your statement is entirely accurate about it not evening out in the end, precisely because of increased difficulty.
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
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
 
Show me the proof in the code that it does so.  I have linked multiple places in the code that completely contradict this statement.  All I've gotten back so far is, "based on my personal experience" and other anecdotal evidence.  As is the saying, "Show me the money!" Someone show me where setting the address to /0 sets share difficulty to p2pool minimum share difficulty by quoting the actual CODE from p2pool (and not some modified version of the code like the vardiff patch or some scrypt coin) from forrestv github.

As I wrote a number of times a few pages back, manually setting the share difficulty only makes sense if you're mining on a node where there is a very large discrepancy between your hash rate and the total hash rate of the node.  For example, if you were to bring a 180GH/s miner to a node with 10TH/s, set that S1s difficulty manually.  The same holds true going the other way.  If you're bringing 10TH/s to a node with 1TH/s, set your share difficulty HIGHER than the default p2pool share value.  I even provided a way for you to calculate what you should set it to to get an average of 1 share an hour.

Regarding your comments on the minimum requirements to join p2pool, you've hit it pretty much dead on accurate.  If you want to ensure you've got a good chance of having a share on the chain for every block found, that means you're going to need enough hardware to find a share every 12 hours or so.  Currently the share difficulty is 6.5M.  So, to find 2 shares a day, you'd need just about 650GH/s.

Your statement about the hardware to bring to the party is incorrect, though.  It's not like a dragon or an S2 is somehow better at finding shares than an S1 is.  Hash rate is hash rate, no matter how you get there.


Dude that easy to see 1st hand lol that /0 is a manual diff setting override try this and watch what happens on ya miner diff....   1st set to 7500000 watch ya miner diff rise above the node diff and set at 7.5mil....     Then set any number under the current node diff eg 4mil it will default to the min node diff as it will NOT allow you to set a diff under the current min diff of the node share rate so basically a 0 setting or a 4mil or 5 mil setting is going to gave a min diff or the node at 6.5 .....

Show me the code.  Don't tell me, "dude that easy to see 1st hand lol...".  Here's my proof.  First, the reading of manually set difficulty:
Code:
desired_pseudoshare_target = None
        desired_share_target = None
        for symbol, parameter in zip(contents2[::2], contents2[1::2]):
            if symbol == '+':
                try:
                    desired_pseudoshare_target = bitcoin_data.difficulty_to_target(float(parameter))
                except:
                    if p2pool.DEBUG:
                        log.err()
            elif symbol == '/':
                try:
                    desired_share_target = bitcoin_data.difficulty_to_target(float(parameter))
                except:
                    if p2pool.DEBUG:
                        log.err()

        if random.uniform(0, 100) < self.worker_fee:
            pubkey_hash = self.my_pubkey_hash
        else:
            try:
                pubkey_hash = bitcoin_data.address_to_pubkey_hash(user, self.node.net.PARENT)
            except: # XXX blah
                pubkey_hash = self.my_pubkey_hash

        return user, pubkey_hash, desired_share_target, desired_pseudoshare_target
Now, here's the difficulty_to_target definition:
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)
This CLEARLY sets the difficulty to 2**256-1 if you set /0.  Using python and printing what 2**256-1 resolves to:
Code:
Python 2.7.8 (default, Jul  3 2014, 06:13:58) 
[GCC 4.2.1 Compatible Apple LLVM 5.1 (clang-503.0.40)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> x=2**256-1
>>> print x
115792089237316195423570985008687907853269984665640564039457584007913129639935
>>> exit()
Now, here's where the comparison between YOUR set value and the value p2pool determines happens:
Code:
if desired_share_target is None:
            desired_share_target = 2**256-1
            local_hash_rate = self._estimate_local_hash_rate()
            if local_hash_rate is not None:
                desired_share_target = min(desired_share_target,
                    bitcoin_data.average_attempts_to_target(local_hash_rate * self.node.net.SHARE_PERIOD / 0.0167)) # limit to 1.67% of pool shares by modulating share difficulty

            local_addr_rates = self.get_local_addr_rates()
            lookbehind = 3600//self.node.net.SHARE_PERIOD
            block_subsidy = self.node.bitcoind_work.value['subsidy']
            if previous_share is not None and self.node.tracker.get_height(previous_share.hash) > lookbehind:
                expected_payout_per_block = local_addr_rates.get(pubkey_hash, 0)/p2pool_data.get_pool_attempts_per_second(self.node.tracker, self.node.best_share_var.value, lookbehind) \
                    * block_subsidy*(1-self.donation_percentage/100) # XXX doesn't use global stale rate to compute pool hash
                if expected_payout_per_block < self.node.net.PARENT.DUST_THRESHOLD:
                    desired_share_target = min(desired_share_target,
                        bitcoin_data.average_attempts_to_target((bitcoin_data.target_to_average_attempts(self.node.bitcoind_work.value['bits'].target)*self.node.net.SPREAD)*self.node.net.PARENT.DUST_THRESHOLD/block_subsidy)
                    )
This block is NEVER reached.  Why?  Because the value of "desired_share_target" at this point is not None.  It is 2**256-1.  Therefore, your desired target difficulty remains at 2**256-1 when you set it to "0" manually by using /0.

Now that I've shown my proof why you're wrong, show me why you're right.
legendary
Activity: 1540
Merit: 1001
hash rate they may be out doing the 2 terra's but earning wise what happening may pay to look at how many shares they are putting in ......   in theory on a s1 you should hit around 16mil diff 1 shares every 2 days on normal mining pools    that is 2-3 shares p2 wise they are luck to hit 1 so off your example above 3 by 12 ants = 36 ant miners in total you should be seeing around 90 odd share every 2 days between them or there abouts to be on par with their diff 1 share rate and that the issue they are hitting no where near their diff 1 share rates......

The last 27 shares found on my node (out of 52 total for 1.5 day uptime):

8 shares - S1 group 1
5 shares - S1 group 2
5 shares - S1 group 3
9 shares - Terraminer group

Very appropriately proportional.  Roughly 7.2TH/s for the S1's, roughly 3TH/s for the Terraminers.  2:1 hash ratio, 2:1 share ratio.





dude look at them number close they are no where near what they should be for an s1 diff 1 share rate.......      the 1st group has hit at less than a share each in 1.5 days    and it get worst from there I rest my case    


8 * 6.5 mil =   5200000 diff 1 share    for that 1st group of 12 miners they should be around 32000000 diff 1 share at the end of day 2 they are about 26 mil shares down atm vs ya mining a normal pool...... diff 1 share wise  so there a huge loss there atm vs mining at a normal pool

You're comparing apples and oranges.  A share in the p2pool alt chain is worth a *lot* more than a normal diff 1 share on a normal pool.

M
Jump to: