Sounds like you ran out of resources on that particular box. Care to share some system information? Architecture, distro, kernel version, what kind of other programs you have running at the same time, and the output of free and ulimit -s would be nice.


There's no "--scrypt" (that's cgminer/bfgminer) or "-scrypt" option. The correct syntax is "--algo=scrypt", or "-a scrypt", as you can see from the output of "minerd --help".

The old getwork protocol, now deprecated, is still accessible at litecoinpool.org on port 9332. Be advised, however, that you will get a much higher stale rate if using getwork instead of Stratum.
Depending on how the ban is implemented, it may be possible to circumvent it by connecting through a SOCKS proxy located outside your network.

There is no "AVX2 version". There is only one binary which includes implementations for various microarchitectures and instruction sets. If the CPU and the OS both support AVX2, then the miner automatically takes advantage of AVX2 (as long as you're not using some old version of it, of course).
If you compare a Haswell core with a Sandy Bridge or Ivy Bridge core running at the same clock frequency, the former can mine almost twice as fast as the latter.

As a matter of fact, new users are being accepted every day, and I often see new miners coming from the larger pools.
That said, it's always been against my principles to actively try to "steal" users from other pools.

Personally I believe there is currently not enough awareness of this problem, and this can create a vicious circle: new miners tend to join the largest pool (because they naively think that bigger is better), which makes the pool even larger.
Mining should remain a decentralized effort. If you think a pool is getting too large, maybe you should direct your complaint to them, and try to raise awareness among miners about the dangers of centralization.

Related link: https://litecoin.info/Spread_the_Hashes

It worked for me using Firefox 25, but now that you mention it I see why there could be a problem with other browsers.
Could you please try again and see if it works now?

You didn't really use "my.worker:password" to authenticate, did you? Pools usually require you to register an account on their website and to use the credentials of one of your workers to authenticate when mining. (That is not the case with P2Pool.)
There are also syntax errors in your commands above, but I suppose those were introduced by Google Translator, otherwise minerd would have complained.

I think they're using about 500 GPUs, or at least that's what it looks like from the logs. Still, it probably isn't the largest GPU farm around.

Hash rate is not the only thing you should consider when choosing a GPU. Energy efficiency and cooling are also very important. Miners would still prefer 7950s, despite there being faster GPUs. Alas, 7950s are nowhere to be found at the moment. The R9 280X and R9 290X are acceptable alternatives, as is the older 7970. The 7990 is a dual-GPU card, and tends to produce a lot of heat, so you need to make sure you have an adequate cooling solution if you want to use it for mining.

You are probably right. I will lower the minimum thresholds to 0.1 LTC for instant payments and to 0.05 LTC for automatic payments for the moment. If this turns out to be sustainable, I may lower the thresholds further.

Thank you!

I'll think about it, but for the moment you can simply tell your friends to send an application as described on the website. I have already accepted a lot of new users this way.

The prefix socks5h:// is intended for remote name resolving. socks5:// should resolve locally.

I've just tested it with three different SOCKS proxies (a public proxy, Tor and SSH) and it seems to be working fine. Have you made sure that in the argument to the --url/-o option the protocol prefix matches the type of server (Stratum or HTTP)?

Wrong thread. This miner only supports algorithms SHA-256d and scrypt.

Not sure what you are referring to. The filename is just a name. As they say, a rose by any other name would smell as sweet.

Anyway, I have briefly tested the 64-bit package with wine64, and as expected it doesn't work if I remove pthreadGC2.dll or if I replace it with the one from the 32-bit package. That pretty much proves that the file is 64-bit, to me. I'm not a Windows expert, but I do know that function calling conventions are different for 32-bit and 64-bit programs, so I very much doubt that a 64-bit program can use 32-bit libraries.

That file should be 64-bit just like the rest. What makes you think it isn't? Just the filename?

It isn't clear to me why you'd want to update the DLLs, if those provided with the binary package work. If you are trying to make the miner faster, you are definitely looking in the wrong place.

The registration page was updated just yesterday to include the following:

Please read the FAQ before posting questions.

Everything is back up. Very sorry for the 70 minutes of website downtime, from 19:14 to 20:24 UTC. I still have to investigate what caused this, but at first glance it looks like a database issue.
Tomorrow I will analyze the logs to see if any submitted share hasn't been paid, and adjust balances if need be.