Quote from: Halofire on March 19, 2014, 04:25:42 PM

Quote from: TheStuhlman on March 19, 2014, 03:34:07 PM

Another big pool is having problems in the last two days, so I delayed Nitro2 till they resolve their issues, releasing Nitro2 now will be counterproductive, we do not want to take miners from other pools, we are trying to spread the hash, not pile up more miners on Nitro.
If you guys do not mind I'd rather wait 2 more days for this after which we will release Nitro2 that should give everyone proper time to prepare.
Also some other pools are doing quite well marketing right now, so do not want to jump in quick on their growth. Our idea behind Nitro2 is to
move some of our miners from pool A to pool B and not get a rush from new miners. The latest increase in miners on Nitro is not caused by us.
It should be resolved soon.

Nitro: We gotta wait 2 more days when it's been 2-3 weeks at least since I've known you've had the highest hashrate problem? N-factor is only 2 weeks away. Every day counts. Please reconsider. By delaying Nitro 2, you are still enabling the problem. Even is you did 'steal' miners from other pools, you would be allowing the other pools to be mining correctly, no orphans. miners and pools both make more UTC by opening Nitro 2. So it's a win win.

I wanted to remain loyal to my pool and spread the hashes, but I've lost 50% of my minings in pointless hashing due to orphans at leet. 4-5 UTC in last 5 hours, calculated at least 600 UTC loss for a 30 day period, but since there are variables, I'd say I've lost at least 450 coins for the last 3 weeks. I receive 25 UTC/day. so that's approximately half. Am I a loyal fool? At .00022, I am just breaking even for electric.

Laterbreh: I appreciate all you've done and loyalty is a big deal for me, which is why I haven't left leet until now. I can't afford to lose anymore, I've hit the turning point. Maybe another coin, another time, or if nitro really reduces it's hashrate. Mining at your pool is 2x more expensive. Nfactor coming up, i need to make back some UTC before it's too late. The thing I don't understand is why lesser pools than leet have 0 orphans from what I've read in the past in this thread.

An idea for the future: since miners and pool owners can't come to an agreement or figure this problem out, in my opinion, this is a problem that can only be solved by encoding something in the coin. We need a "pool-resistant" or "pool difficulty specific" coin for lack of better term, where a coin can sense which nodes have more hashing power than others and raises difficulty for those nodes with higher hashes.

Halo I explained that high orphan rate is not related to high hash rate at another pool. There is way too many factors to this. You can ask the other pool owners if they are having the same problem. All the pools get orphans, and it occurs more when the block time is faster. But your persistence to blame the orphan problem on us is beyond me. Why would our hashrate cause orphans at one pool and not another?

I know exactly why you are having issues and I posted it earlier on this thread. If you had bothered to read my advice you would not have been in this situation. I said it once and say it again once your pool reach 270MH it will fail, did you believe me then NO, and when the ddos hit our pool the quick jump on your pool put you over that fail line. So the fail came sooner than later. And it was compounded by the ddos on us to a point of no return.
Every time our pool went down for a little bit, the problem at your pool was growing. If you remember the first day of UTC launch, IDcray had the same issue because they had high hashrate from day one, and they closed signups quickly because they did not know how to deal with it. Now you want more, when the next Nfactor kicks in the fail line will be at 180MH after which a small pool will fail to operate. Our creation of Nitro 2 is mainly to satisfy the community, and bring some peace to this thread. It's a shame we have to keep going back to this. Read my earlier posts on this thread about these issues.

As for your suggestion for pool resistant hash diff etc.., please read it again. If your suggestion is practical I would be mining UTC blocks on a CPU at 0.000001 difficulty and you will be mining it at your pool at 5 or 6 diff.