That error seems clear enough to me. You have no program called "miner_proxy" in the directory. How is the executable you've got called? If you downloaded it from the pool the filename is probably mining_proxy.exe.

I'll stop you right there. For Litecoin you need to use the fork of the proxy linked on the help page.

The proxy handles all communication with the pool. The miners will only talk with the proxy.

Example. Let's say you run the proxy on a machine whose local address is 192.168.1.42. Then you will start cpuminer with something like the following:
The username and password are the same you were using when minerd was connecting directly to the pool.

The instructions on the help page seem pretty specific to me...


If you have any specific question, feel free to ask.

In order to encourage miners to adopt the new Stratum protocol, which allows for very low stale rates, we are not paying for stale shares anymore. To compensate for this, the PPS fee has been lowered to 4%.

• If you are using a recent version of cgminer, you are already taking advantage of Stratum.
• If you are using reaper, you are strongly encouraged to use cgminer instead.
• If you are using cpuminer, you can lower your stale rate by running the Stratum proxy. You only need to run one proxy for all of your miners, as long as they are all within the same local network. More information about setting it up is available on the help page.

Send me a private message or email with the details, or contact me on IRC.

The PPS rate currently shown on the site is what you get paid if you solve one share at the lowest difficulty that can be served by the pool. Most other pools use a much higher, fixed share difficulty, so the PPS rate they report is higher.
This doesn't mean that you will earn less, because if you mine at our pool you will be credited many more shares.

Regarding adaptive difficulty: if you find a share that has a difficulty which is 4 times that of the minimum share difficulty, it will be counted as 4 shares. This allows to measure workers' speed more precisely while keeping bandwidth usage optimal.

As always, there can be many "reasons" why one would want to attack pools. Because they hate altcoins, or because they want to manipulate network difficulty... who knows.

While I'm here, I'd like to announce that the pool now officially supports Stratum mining.
http://www.litecoinpool.org/news?id=39

Most cgminer users have already switched to Stratum automatically, and need not change their configuration. If you're running a version older than 2.10.3, you are strongly encouraged to upgrade.
Miners using cpuminer and/or Reaper are encouraged to use a proxy if running multiple miners in a LAN (instructions are available on the help page).

I suppose you mean "cpuminer".

Recent versions of cgminer already support Stratum natively. Using a proxy would still reduce bandwidth usage and server load, but if you don't have that many miners it's easier to just connect directly to pools, especially since this allows you to easily set backup pools.

I've been thinking about it lately, but right now I am busy with more urgent projects.
I have just finished adding Stratum support to my pool, and now I am working on the new release of the Litecoin client.

By the way, if you have more than one miner it is still better to use a proxy for Stratum mining, because it minimizes bandwidth usage and reduces the load on pool servers.

Just remember that for Litecoin mining you have to use this fork of Slush's original proxy:
https://github.com/CryptoManiac/stratum-mining-proxy
Binary for Windows here (thanks to Balthazar).
You run the proxy with
and then connect your miners to local port 8332 with your usual worker credentials.

What distro are you using? If Debian or Ubuntu (or some other derivative that uses APT), have you installed build-essential and automake?

You got the tarball from Github, not from the Github repo. You only need autogen.sh if you cloned the repository using git.

There's your problem. It should be "-O3", not "-03" (big O, not zero), otherwise gcc won't recognize the flag.



As seen above, the problem you encountered is not a bug, and you would get the same behavior with jgarzik's original version.
My fork just adds support for the algorithm used for Litecoin mining, introduces a lot of optimizations and adds a few extra functionalities.

You can connect as many miners as you please using the credentials of a single worker. It causes no harm.

What you may notice is that your miners will find fewer shares, because the share difficulty will adapt to your hashrate. However, this will not affect your earnings, as higher-difficulty shares are worth more.

Just wanted to confirm that this is indeed a scam.

I'm not going to open up registrations for the time being because performance-wise I'm happy with the current hash rate of the pool, but (as I've already stated before) people who really, really want to mine at litecoinpool.org just need to contact me and provide some kind of justification as to why they don't want to use another pool.

burside, thank you very much for letting me know. I must have uploaded the wrong binary for the 64-bit Windows version of the miner. That version was compiled for internal use only, and never intended for public distribution. On the up side, that default address would never have worked from the outside of the private network it referred to, and when mining in a pool people notice immediately if shares don't show up in their account, so the only problem this could have caused is that getting the binary to work was trickier because you had to use the --userpass option instead of --user and --pass.

Unfortunately I'm currently away, so I'm unable to recompile the binary, but luckily there's not much difference between 2.2.2 and 2.2.3 apart from the benchmark feature, so for the moment people can just download version 2.2.2, which on Windows should not be any slower.

Miners who are currently using the "wrong" 64-bit 2.2.3 binary with no issues need not downgrade. There is no risk that your shares go to the wrong server or account, it's just that when you first set the miner up it may be a bit trickier to get your credentials to work, as in that binary not all of the command-line options for setting the credentials work as expected.

I'd like to implement it, but I can't say when I'll be able to. I'm pretty busy in this period.

As far as I know you can't specify an address to mine to when using litecoind directly. You need to use the username and password in your litecoin.conf file.

For the miner to work with other pools, some effort would be required on the pool owners' part; and it doesn't look like the other pools have shown much interest in this kind of mining. Anyway, I have written a miner and adapted the pool I run to work with it. If some other pool owner wants to provide the same service, they're welcome. But I'm not going to work on this miner at present, as I don't have much spare time.

Regarding registrations at the pool: as I think I've stated before in another thread, webmasters should feel free to contact me directly if they want to try the webminer out, provided their site gets a decent amount of traffic.

Just for reference:


More explicitly, it should be enough to change
to

Litecoin pools don't all use the same share difficulty. And of course if the share difficulty is lower shares are "easier" to find, and their value is lower.