[ANN] The First Litecoin PPS Pool (litecoinpool.org)

[ssinc]

I'm pretty sure the pool is getting DDOS'd as I keep getting notifications that my miners are idle when they seem to be hashing just fine. 

is it only me or the pool lost the half of its hash rate? we are @ 1,468 MH/s, and the LTC network in general has lost almost 3 Gh/s, I think that Mtgox news is doing more damage than good to LTC,.

[1713535761]

1713535761

[RockyMtnMiners]

Could also be a bunch of hashpower switched over to Feathercoin. FTC's profitability has been a good bit higher than LTC's the last few days.

[razorfishsl]

when the pool payout is set, why does the pool not pay out the full amount in the account?

If I set it to 0.6  it pays out 0.6 and leaves the balance....if i set it to 0.8 it pays out only 0.8 even if there is more in the account...
 do I really have to set it to  0.xxxxxxxxxxxx to get the full payout?

[pooler]

when the pool payout is set, why does the pool not pay out the full amount in the account?

If I set it to 0.6  it pays out 0.6 and leaves the balance....if i set it to 0.8 it pays out only 0.8 even if there is more in the account...
 do I really have to set it to  0.xxxxxxxxxxxx to get the full payout?

That is actually meant to be a feature.
Automatic payouts are recurring, so the exact amount is not important. What is not paid out by a given automatic payment will be paid out by the next.
Most users are mining 24/7, so there's no point in paying out the exact amount every time the payout threshold is reached, because their balances grow continuously.
The advantage is, of course, that you get payments with nice round numbers, which some people prefer.

If you want a full payout, simply request an instant payout on your payments page.

[mmitech]

the pool is down for me, my workers are Idle

[pooler]

the pool is down for me, my workers are Idle

I'm working to resolve this as soon as possible. Unfortunately this time the attack was done on a pretty large scale.

EDIT: The attack was successfully mitigated, and all systems are back up. Sorry for the inconvenience.

[mmitech]

the pool is down for me, my workers are Idle

I'm working to resolve this as soon as possible. Unfortunately this time the attack was done on a pretty large scale.

EDIT: The attack was successfully mitigated, and all systems are back up. Sorry for the inconvenience.

keep up the good work

[pooler]

In the past few weeks I've been working on a rewrite of our poolserver software, redesigning it to take into account all the Stratum-specific optimizations I could think of and to include some new features.
This new design enables lower-latency communication, which should result in even lower stale rates. Preliminary tests have shown a reduction of server-side latency by a factor of 2 to 4.

I have also implemented the "resume" extension to Stratum, which apparently no other pool currently supports. This means that if your Internet connection has a hiccup, the server may still accept any shares that your miners found while disconnected, if they reconnect and submit them within a reasonable time. As simple as this may sound, it is actually tricky to implement, because (unlike getwork) Stratum is not a stateless protocol.

Before deploying this new software to the main pool servers, I'd like to ask miners to beta-test it for some time, so that I can make sure everything works as expected. To this end, I have set up a testing server at testing.litecoinpool.org:3333; you can connect to it in the same way you connect to the other pool servers, and all shares you submit should be credited to your pool account as normal. Keep in mind that I might have to restart the software from time to time to test new code, so very occasional disconnections should be considered normal.
Please report any unexpected behavior you may encounter directly to me via email, PM or in our IRC channel.

[mmitech]

In the past few weeks I've been working on a rewrite of our poolserver software, redesigning it to take into account all the Stratum-specific optimizations I could think of and to include some new features.
This new design enables lower-latency communication, which should result in even lower stale rates. Preliminary tests have shown a reduction of server-side latency by a factor of 2 to 4.

I have also implemented the "resume" extension to Stratum, which apparently no other pool currently supports. This means that if your Internet connection has a hiccup, the server may still accept any shares that your miners found while disconnected, if they reconnect and submit them within a reasonable time. As simple as this may sound, it is actually tricky to implement, because (unlike getwork) Stratum is not a stateless protocol.

Before deploying this new software to the main pool servers, I'd like to ask miners to beta-test it for some time, so that I can make sure everything works as expected. To this end, I have set up a testing server at testing.litecoinpool.org:3333; you can connect to it in the same way you connect to the other pool servers, and all shares you submit should be credited to your pool account as normal. Keep in mind that I might have to restart the software from time to time to test new code, so very occasional disconnections should be considered normal.
Please report any unexpected behavior you may encounter directly to me via email, PM or in our IRC channel.

pooler keep up the good work, Later I will point one of my miners there and see what happens.

[CoinBuzz]

I am waiting for register here, it's been 3months.

Can you allow me to register?

I also emailed to the applications, but did not get any answer.

[pooler]

I also emailed to the applications, but did not get any answer.

It's possible that your email or my reply was caught by a spam filter. Please try sending your application again.

[CoinBuzz]

I also emailed to the applications, but did not get any answer.

It's possible that your email or my reply was caught by a spam filter. Please try sending your application again.

Sent again.

[pooler]

I am glad to announce that beta testing of the new poolserver software is complete. I wish to thank all those who helped by mining on our special testing server.

Testing with real-world mining traffic revealed a very pleasant surprise: server-side latency, which according to preliminary tests should have been reduced by a factor of 2 to 4, was actually reduced by a factor of about 10, often making it negligible when compared to network latency.
What this means in practice is that our servers will now be able to handle a much higher number of connections while realizing an even lower stale rate (it was not uncommon for test miners to achieve stale rates lower than 0.1%, even when hundreds of clients were connected to the server).

I will gradually deploy the new software over the next few hours; your miners may experience a brief disconnection, but they should be able to reconnect automatically in a few seconds.

A lot of people have asked me to reopen registrations for the pool in the past few months, and I'm very happy to say that now we finally have an exclusive, scalable solution that will make this possible without sacrificing the quality of our service. Stay tuned!

[forsetifox]

Thanks for reducing the payout threshold Pooler.

 

[juanjan]

Hi pooler!

Thanks for the invitation and good work!

[demonmaestro]

Ill try to keep this under one thread but i got a little issue. working here.. Using cgminer it says my Kh/s are about 900kh/s BUT on the pools website it says its only at 300KH/s whats up with that and that is after a few hours of running?

Thanks for the help.

[pooler]

Using cgminer it says my Kh/s are about 900kh/s BUT on the pools website it says its only at 300KH/s whats up with that and that is after a few hours of running?

From the FAQ:

The pool reports a much lower hash rate than cgminer. What's going on?
If the estimate displayed on the site stays too low for more than 15 minutes, then you are almost certainly experiencing hardware errors.
cgminer checks every solution generated by your GPU, and if one turns out to be incorrect because of hardware errors it (rightfully) doesn't even submit it. Since pools can only estimate your hash rate based on how many solutions you submit in a given amount of time, their estimate will be lower than your real raw hashrate. This raw hashrate, which is correctly displayed by cgminer, is, however, not meaningful if the solutions your card generates are wrong.
You need to make sure that all (not just the top one) of the HW figures in cgminer are zero or next-to-zero; if that's not the case, you need to review your settings. Make sure you carefully read the documentation about scrypt mining provided with cgminer.

You may want to post the settings you are currently using and your GPU model.

[demonmaestro]

From the FAQ:

The pool reports a much lower hash rate than cgminer. What's going on?
If the estimate displayed on the site stays too low for more than 15 minutes, then you are almost certainly experiencing hardware errors.
cgminer checks every solution generated by your GPU, and if one turns out to be incorrect because of hardware errors it (rightfully) doesn't even submit it. Since pools can only estimate your hash rate based on how many solutions you submit in a given amount of time, their estimate will be lower than your real raw hashrate. This raw hashrate, which is correctly displayed by cgminer, is, however, not meaningful if the solutions your card generates are wrong.
You need to make sure that all (not just the top one) of the HW figures in cgminer are zero or next-to-zero; if that's not the case, you need to review your settings. Make sure you carefully read the documentation about scrypt mining provided with cgminer.

You may want to post the settings you are currently using and your GPU model.

They are Sapphire HD 7850 - all 3 of them

[Beaflag VonRathburg]

From the FAQ:

The pool reports a much lower hash rate than cgminer. What's going on?
If the estimate displayed on the site stays too low for more than 15 minutes, then you are almost certainly experiencing hardware errors.
cgminer checks every solution generated by your GPU, and if one turns out to be incorrect because of hardware errors it (rightfully) doesn't even submit it. Since pools can only estimate your hash rate based on how many solutions you submit in a given amount of time, their estimate will be lower than your real raw hashrate. This raw hashrate, which is correctly displayed by cgminer, is, however, not meaningful if the solutions your card generates are wrong.
You need to make sure that all (not just the top one) of the HW figures in cgminer are zero or next-to-zero; if that's not the case, you need to review your settings. Make sure you carefully read the documentation about scrypt mining provided with cgminer.

You may want to post the settings you are currently using and your GPU model.

They are Sapphire HD 7850 - all 3 of them
https://mycryptocoin.us/downloads/litecoin.jpg

It appears you're actually trying to ignite your GPUs. You need to completely revise your settings to bring the temps and HW errors down.

[Pentel]

They are Sapphire HD 7850 - all 3 of them


It appears you're actually trying to ignite your GPUs. You need to completely revise your settings to bring the temps and HW errors down.

Holy sh*t 101c for GPU 1