Topic: 📈 NastyFans: The Bitcoin Enthusiast Fan Club (est. 2012) - page 86. (Read 958995 times)

It is a good thing that I am sure then. 

While I do appreciate these concerns, it would be a mistake to think nonnakip and I haven't been discussing implementing NastyPool for years now.  In fact, the reason why NastyPool isn't currently offering PPS is because nonnakip has been testing different payout algorithms against live data.  That was actually one of the driving factors behind our mining lottery contest.  The best thing you can do if you are concerned is to mine on NastyPool and help provide more data for testing.

Rest assured of this...  I will remain in communication with nonnakip and will continue harassing him repeatedly about the concerns and risks of NastyPool so that fans won't have to.  We have had lengthy face to face discussions about the risks and I believe the quote I used to locking down a workable PPS formula was that it was like "catching smoke with your hands."  That being said, we will not take a hands off approach to the payout formula used, and it will start off very conservatively.

I don't want to let the cat out of the bag, but I think the NastyPPS risk will be minimized a great deal over standard PPS.  At this point, I just hope for trust from fans.  Once everyone sees the implementation, I urge you to analyze the hell out of what could go wrong.  Don't think for a second that these PPS concerns aren't being taken seriously or that it won't be implemented in a responsible and safe way that will not harm NastyFans.

Yes BA is shipping.  Way late but on the way.  BFL will not be until this late fall.

PPS nearly put some pools out of business with bad runs of variance.
I am not sure it is a good idea here where it can be much harsher.

It looks like Black Arrow is finally shipping.  Hopefully BFL is not too far behind.

NastyPool is something that has been discussed over a period of years, not days.  Many risks have and will continue to be carefully considered.  The PPS payout method is obviously a risk, but it is a manageable risk, which is the best kind.  I think when you see the actual implementation, you will see that the risk is being minimized a great deal more than some other pool failures that went the way of the dinosaur.

Just be careful about the level of risk you're willing to take... pools have shut down in the past when their luck made their pools a losing operation and weren't earning enough to cover their PPS payouts...

=squeak=

Thank you for feedback.

So long I run it NastyPool will never stop as a public P2Pool node. The PPS-like payout method will be a separate feature available to nastyfans that have interest. OgNasty and me have many requests for this feature from miners that are bigger than all of us. The feature should help us get PPS-lover miners on NastyPool. And that means strengthening P2Pool. And that is our goal.

The overlay was what I had in mind...

and, honestly? If I was interested in PPS? I'd be mining somewhere else... and if you switch to PPS? I will be...

=squeak=

I added your request to my list of things to do. Maybe we can have a overlay so we do not need 2 different graphs. I will try some things.


Correct. There are still many steps. One of the next features is implementing a PPS-like system and a real pool interface on nastyfans.org. Eventually NastyPool will be just like other pools (and maybe better) but with a pure P2Pool engine.


Yes. But the pool hashrate is too low for any alt coins. I already look into alternatives to pay server costs.

It isn't really behaving as a mining pool tho, but more as just another open p2pool node... (or, it was, before adding the proxy and changing the statistics available to be looked at)

Are you still merge-mining alt-coins also to help cover your expenses?

=squeak=

Thanks, but I'd rather have the graph for the payout back... tho having the number for where I'm currently at is nice too. If I had the choice of one or the other, but not both, however, I would prefer the graph.

=squeak=

I allow others to decide this. As a pool it functions 100%. But I see many things to do for the pool still before a person with no nasty experience can feel comfortable. Right now there is no documentation or explanation about the pool. I do not know if promoting the pool right now is positive or negative.

I added payout information for current round. Hopefully a value of 0 will not discourage some miners. A value of 0 for the current round does not mean the miner will never receive payouts.

The page is very primitive still. I plan to provide more advanced statistics per miner later.

Would you mind also adding another line showing what our payout is as well?

=squeak=

Would it make sense to report Nasty pool at:
https://bitcointalksearch.org/topic/btc-mining-pools-list-104664
BTC Mining Pools List

The P2Pool proxy for NastyPool is now on ports 9332 and 9334. Miners should change back to 9332 when it is convenient. When I see no more miners on 9334 I will shutdown the service on that port. Please report if you have any problems.

This means that our P2Pool node is now protected on the worker port by the proxy. This also means that the P2Pool statistics web page is not available because it was also on the worker port.

I now create our own P2Pool data graphs: https://nastyfans.org/miners

The light line shows the reported P2Pool data. The dark line shows a 4 hour running average. The vertical lines show when your miner earned a P2Pool share.

This is the next step of many to integrate P2Pool into NastyPool (the mining pool of nastyfans).

Just switched to 9334. Sorry for the late switch but I will report any problems if they occur.

So far no problems on port 9334.
I just wanted to give you an update.

Distribution 312461 is complete. nastyfans thanks the donators.

Thank you for reporting. Yes these were double entries. One of the servers uses bitcoind in a container to handle monitoring of incoming donations. That bitcoind had no more memory allowed and started returning unexpected results. This caused display error.

I allocated more memory for that container. But bitcoind is getting big to use for such a trivial task. I maybe change how I monitor the donation address. Although I like providing Bitcoin nodes and blockchain copies to help the Bitcoin network.