 Show Posts
|
|
Pages: [1] 2 3 »
|
That was part of our old database.
I have no idea why that information was there and I plan on figuring out which idiot from my team did that.
I am in the process of emailing all the affected users to let them know.
Very bad security practice to leave the accounts passwords unencrypted, i hope your not the coder for that site! Would advise all users to get their miners away from there ASAP A. We had to keep the WORKER passwords unencrypted so that users could see them and edit them more easily. B. This is our OLD database on the OLD site. We have since completely rewritten the site's code and it doesn't even use mysql anymore. C. This happened because one of the guys on the team was doing some debugging and like an idiot did not secure his testing site. |
|
|
|
|
That was part of our old database.
I have no idea why that information was there and I plan on figuring out which idiot from my team did that.
I am in the process of emailing all the affected users to let them know.
We managed to minimize the damage on our end though only about 1 or 2 coins were lost.
|
|
|
|
Thanks for the update. What was your motivation to move to pay-per-share?
It is fairer to the people who stick with us as well as more consistent for people that don't want to stick around long. I feel like all around our RSMPPS system is better. |
|
|
|
Ok guys please relax. I was moving to a new apartment the last few days so I was not able to answer your questions. There were some issues with the stats display that were showing people having higher earnings than they really had. You can verify your earnings very simply. We now operate on a system very similar to Pay Per Share. That means you get paid the same amount for each share. You can find that amount by doing this: (Number of shares) divided by (current difficulty) multiplied by (50 coins per block) = your earnings. If you did work on a recent block and did not receive a payout it is most likely because you have not hit the default 1 BTC threshhold for payouts. You can change that by simply adding your workers to your account on the site. You can also request a payout manually by hitting "PAY ME" after you log in. If you have any serious(or even small) problems you can always email me. My email is admin@nofeemining.comI have fixed the problems of everyone who has emailed me. Rest assured if there has been any problem that has caused you to lose any amount of your balance for work that you did I will reimburse you personally. Remember that I also mine on this pool with my workers and this pool is a free service that is supported by donations. |
|
|
|
btw is there any way to reset your pwd ?
I didn't get around to adding it to the site but if you have forgotten it just send an email to admin@nofeemining.com and I'll take care of it for you. I'll add it into the new backend when I get a chance |
|
|
|
(Added padding: 10px; to input's)  vs (Original, FF5 Win7)  Also, you should set the "Sign up"-password field to actually be a password field. I specifically didn't make it a password field because otherwise you could type in a password incorrectly and not realize it. I wanted to make signup as easy as possible with the least amount of information entered. Thank you for the help though. Either way we are switching our infrastructure in a few days so I'll just fix it in the new one. |
|
|
|
NoFeeMining pls correct api out -> "poolspeed" many time out zero! pls aproximate data or simple correct bug/
ok thank you for the bug report |
|
|
|
It will definitely be sorted once the new infrastructure is up
Man, that can't come soon enough. I keep having connection issues and its extra annoying because each time my card goes idle my screen flickers. Also payments are being slaughtered by being idle so often. It will most likely be ready in the next few days |
|
|
|
It only now started to keep the connection, the constant resets fked things up  Hope from now and next block onwards this will be sorted  It will definitely be sorted once the new infrastructure is up |
|
|
|
I had to disable nofee until I manually test if its working.
Right now it would want to jump to nofee then timeout and cycle continues. wasting a ton of gpu cycles.
Its been working fine the last 20 minutes. It only got slow for about 10-15 minutes after the block was found. |
|
|
|
Hi
Ive noticed after a new block the pool is absolutely impossible to submit shares to. my miner keeps dropping then after an hour or so, which would be the case now again with this new block, I get majority of my submitted shares in.
Can you please sort this out?
Yep I am aware of the issue and it will be fixed very soon. The problem is inherent with our current pool setup. Rather than spending a lot of time fixing it on the current back end I decided to create an entire new backend to fix all of our previous problems. The new backend is almost ready and won't have that problem so no worries. In the meantime you can set up your miners to point to multiple pools if you want. If they lose connection to our pool they will automatically ask the other pools for more work to compensate. |
|
|
|
What is the correct format? |
|
|
|
So whats the deal with payouts on this blocks:
23 Jul 2011 5 25 CDT 112h 40m 2,427,589 137621 No (80 / 120) JLD13
I got rewarded nothing after only staying for about 70% of the round, if you ended up changing the payout scheme halfway through a block thats pretty messed up.
Don't worry it's just a bug with the stats because two blocks were found so close to each other. As soon as that block is confirmed all of your earnings will move to confirmed and everything will be ok. The bug is sort of intentional as it's meant to ease the load on the server. That will not happen with our new backend which we are switching to very soon. |
|
|
|
Getting a lot of work queue empty messages, but my other pool is going just fine. Is there something going on with the server?
We finally cracked that block and the server is transfering the 6 million shares. Our current back end is not very efficient with large numbers of shares so the server is lagging. It seems like its almost done though We will be moving to a new backend sometime this week so these will be problems of the past soon. |
|
|
|
having trouble with your api. I think it's because it's https instead of http. Any chance of changing to http for a sec for me to check?
Ta mate.
done, no need to rush its permanent |
|
|
|
Is there a way to change the address where idle alerts are sent? I registered with my email address but I like the alerts to go to my phone. I put in 2Gh/s, hopes it helps with this round. Connection is stable and the site easy to use. Nice work.
SMS alerts are on the list of things to do but right now I am working on changing the entire infrastructure of the pool so it may be a little bit until it's done. |
|
|
|
Whats with the new captcha screen? Errors in IE8, so can't access it: We had it enabled for a while while we were getting attacked |
|
|
|
|
Found our second block. Onto the third. 2 BTC bonus for this one.
Congratulations to Llama for getting the bonus on the 2nd block!!
|
|
|
|
|
