Topic: Giving up real solomining and going back to solomining on p2pool - page 7. (Read 11012 times)

update... Doing this did not affect zeds difficulty. He was able to find a few shares when my rentals went dead for a short while, but doing this does not appear to lower difficulty for smaller miners on my node.

Maybe a smaller miner who wants less variance can set it up with his miner to get shares more frequently. Although who knows which one will pay off bigger, could go either way.

Zed: maybe you should try btcaddress/3000000 to reduce your variance. Especially since my rentals come on and off due to being outbid. It may work out better for you.

It's possible... Who knows In the past few weeks I've more than tripled my BTC renting hashpower yet none of the blocks have been found with my rentals. Of course I haven't spent enough to have expectations to have found a block yet either...

I know the prohashing forums have also mentioned symptoms from nicehash of abnormally low 'luck' describing how shares that found blocks were not submitted

https://forums.prohashing.com/viewtopic.php?t=968&start=10

Got it

Changed all my workers to BTCaddress/27000000

Will see how it does. Thanks again, very helpful information!

My pleasure... I ran p2pool nodes for a few years .

You can use them in conjunction with each other... like:

The "+" is for your stats.  There are a number of old threads where the value of using it is debated.  My opinion is that it only helps smooth out hash rate graphs on the node.  The lower you set it, the more "pseudo shares" the node recognizes as valid work, and the smoother your hash rate appears on the graphs.  Those lower diff shares don't get added to the share chain (unless of course they satisfy the share chain diff).  The downside of this is that you are flooding the node with a whole boatload of useless information. 

The "/" actually helps the node for the reasons I mentioned in my previous post.

Thanks Jonny. That's pretty cool, and good to know.

I have not had time to dig into the P2pool code yet, but may have some time now that the holidays are upon us.

Currently each of my miners are set up like this:
Btcaddress+135000

I did this because when I am outbid on nicehash and my orders go dead, the work difficulty is lowered. Sometimes it gets so low that when my orders come back online the pool has been disconnected because difficulty is too low.

The only way I know how to fix that is to set the difficulty like I am currently.

I wonder if using btcaddress/difficulty would have the same effect as btcaddress+difficulty to keep my pool connection to nicehash live and also to reduce variance for the smaller miners?

I'll give it a try on Monday and see how it affects the node.
Currently after my latest adjustments from the oter day it looks like the effeciency is doing alot better than before but I want to run it a little longer to see if it is just a coincidence or not.

By the way, block found https://blockchain.info/block-height/444907

Edit: went ahead and changed them to BTCaddress/27000000 on 9 of them and left one of them at btcaddress+135000 so as to try and keep the pool connection live with nicehash.

Will see how it effects efficiency if at all but also to see how it affects the smaller miners. Again thanks for the input Jonny

You can actually help the miners on your node.  Right now, you are relying upon the node to determine the share difficulty it will accept.  Standard p2pool code will base the difficulty on the combined hashing power at the node.  When there is a great disparity (like yours), the smaller miners are subjected to a much greater variance.  Sure, each share found is weighted higher, but the larger variance means the small miner might miss out on payments because they don't have any of the heavily weighted shares on the chain.

The solution is easy, and is something you can do to help.

P2Pool allows a miner to determine his own share difficulty.  This will override the node's setting.  You implement this by using a "/" at the end of your BTC address.  For example, if you want the node to only accept shares from you above 100,000,000, then you would put the following as your username:
This way the other, smaller miners on your node aren't penalized.  The node won't count your hash rate in the calculations of share difficulty.  Now, the smaller miners will find more, less-weighted shares, and you will find the more heavily-weighted shares.  Everyone wins.

That is correct, when my orders were outbid and my miners stopped hashing on this node, you were the only person left mining, thus the difficulty decreased exponentially.

Notice how when you found a share shortly after midnight while my orders were running again, that you were awarded ALOT more for that share than the shares you found while you were the only one mining on the node

The reason for this is that the other nodes raise the difficulty for my node when my rentals are working so they aren't bogged down with shares from my node.

But when shares are found on my node when the rentals are working they carry more weight and thus pay more than if you were on a node with less hashrate.

yeah, looks like I got shares from ~6:30am - 9:30am (EST) when it looks like all of your miners had stopped. There was another break that looks like ~6:15pm - 8:00pm (EST) where I got a few more shares.

That's great zed! Also congrats on getting a share again! Crossing my fingers p2pool finds a block before it drops off the sharechain

That is indeed my 2th machine. When I pointed the miner at your node I started looking at p2pool stuff, and am, in fact setting up my own p2pool node.

I have set up a full bitcoin node which is in the process of syncing now, but seems to be taking forever or at least longer than I thought it would... When the sync completes I will start the p2pool node and point my miner at it. We'll see how that goes.

Looking at the graphs today, it looks like it's currently my 10 orders from nicehash of 50th each, and a miner with 2th Mining on this node.

A few other miners mined for a few minutes with low hashrates under 1th who quickly left and I assume it's because the difficulty that is served to miners is pretty high since the node has a high hashrate.

I played around with p2pool a little when I first started mining a few years ago, but there weren't any places to rent from back then and after my first solo block on solo.ckpool.org I lost interest in p2pool for a few years.

Now that I have renewed interest in it and am able to rent hashpower in large quantities I am able to do more testing and research on it to better understand and fine tune my node.

With p2pools current hashrate a valid share needs to be around 1.2m but since my node is large compared to others the difficulty for a share on my node to be accepted by the other nodes in p2pools network is currently 30 times higher than it is on the smallest nodes.
Of course each share found on my node does have more weight than a share on the smaller nodes so it doesn't effect variance too much unless your a low hashrate miner on this node.

Currently with 10th, expectations are about 5 shares per day so variance is pretty good, you might find 7 today and three tommorow, but since the expectations for p2pool to find a block is currently on average of every four to five days, you should always have shares that are on the sharechain so that you get a reward from every block.

Looking at the only miner besides myself with 2th, I assume it's zed, he should expect to find about 1 share per day on my node, whereas if he set up his own node or mined on another node that was smaller he should expect to find shares more often although they carry less weight than when found on my node.

Looking at his chart, it looks like he found two shares his first day mining on my node which were paid because a block was found, but over the last three days no shares have been found with 2th. It appears those shared have now expired so hoping that your able to get another share before the next block is found.

If you want to find a smaller node you can look at p2pool.info and find a node with low latencies and better than average effeciencies.

My effeciency rate is currently 90% which I'm not happy with at all and am going to do a restart to see if I can get latencies lower and decrease stales/doa's

One other important note, when I restart my node any shares you have are safe because all nodes in the network have a record of all valid shares whether my node is on or offline. If you have valid shares when a block is found you will receive your rewards.

Edit: node restarted

Maybe you should make a post on their thread to let them know that your not going to rent from them anymore and the reasons why.

yeah you may have taxed his servers down it.  but you did pay a small fee on every order  I think 0.0001

And you may have had the better luck with them  since the  s-9's are 11th to 14th

So my rentals will end with them as of today.

Very interesting theory! I think it's sucks myself that they raised the minimum limit to 50th, I don't think me stopping renting from them would make them change their policies though as their is always someone willing to rent their hashpower even at 150 to 200℅ of expected return, there is always that idiot that likes to throw away their money.

I hate to admit it but I think me renting 600 orders at 10th each might have been the reason they changed it in the first place.

Even though I had an unlucky streak at the end i had several shares that came extremely close to finding a block, one of them even came within 1 billion of meeting the difficulty, ouch, that one hurt!

Wishing they'd lower their limit back to 10th!

I just thought of something.

The op has said he had better luck when he rented 10th

He may be correct.

Here is why  a 10th rental  most likely does not have an s9 involved  since most s9's at at least 11th.

Kano has some stats that show the older s9's suck and have really bad luck.

If old s9's suck and have bad luck due to code.  then renting in 10th sections will be better.

but nicehash now forces you to rent in 50th blocks soany chance of avoid an s9 is no longer possible.

So after my rentals finish with nice hash I will no longer rent with them.

Unless they allow 10th rentals again.

All people should not rent from nicehash and 256 hash unless 10th size is allowed.

So the op very likely  has found  back door proof that the older s9's have shit code.

Its not because of the chicken, its because I can't sit comfortably right now.

From the timing of when he mentioned it, it looks like that may very well be a possibility, appears to have happened within minutes of biffa mentioning it... Thanks biffa!

There's the secret sauce! And I thought that only worked on Kano's pool!

Perhaps it was the mention of chicken?