Important

I have some bad news. Unfortunately, I need to make everyone download a new binary (or source code) again. I found a flaw in my logic that could lead to a potential attack against the chain. Technical details in the next paragraph. Basically, some people might have been able to start mining on the real chain ahead of time. So I need to patch up the code to prevent that. I will make another post when source and binaries are ready. Really sorry about this, but it's good that I caught this.

Here's the technical details for those of you that understand and care. I locked down the genesis block such that only the genesis hash is checked in and you need to provide the genesis time and genesis nonce in order for the client to run. But if you modify the code, you can easily bypass this check. So you can start working on the chain by building on the genesis hash. I previously thought about this, so I found one block and locked that block hash into the code. Even if you start building a chain against the genesis block, you won't be able to correctly find the first block that matches the block hash in the code. Your chain will be rejected by all the other clients because the block hash won't match. This is all good, EXCEPT I accidentally left a client running on the real chain in the open. So if someone modifies the code to run against the genesis block, their client can request block 1 from me. And once they do that, they can start building their chain against that in secret. I am not 100% sure that someone is doing this, but I checked the logs and noticed a connection from a few unknown IP addresses AND I saw a few getdata calls that were requesting for blocks. Since it's possible that the blocks have been sent out, I will need to patch the code to lock another block in. This time I will find the 2nd block in private, and lock that in. I figure it's better to be safe.

Voting has closed, Litecoin will be launched at Thursday Oct 13, 03:00 GMT
If you are in the US, that's 8pm pacific and 11pm eastern on Wednesday Oct 12. That's less than 24 hours away!
Make sure you have updated your binaries.

Oh great !

Sucks to be Europe. But well, that's still better than millions of premined coins and I had to get up at 5:45am UTC+2 anyway... might as well make it 5 I guess... Also, I hope that the starting difficulty won't be ridiculously low.

So far this looks the most uncontroversial of CPU coins....

No premining, no crazy inflation (although I must say something like a 1% inflation once "all coins" are mined would have gotten my vote), no tax, a scheduled launch (even though it's not really at an awesome time).
If the starting difficulty is high enough to prevent the few earliest miners from getting a massive stash and the chain from growing so fast that late miners won't even be able to mine because they spend their time waiting for the chain to download (cf SC2), then there won't be much negative stuff to say about it...

I'll try waking up early in the morning to upload the litecoin.conf to http://litecoin.org/downloads/litecoin.conf for you shell-script ninjas. I'm not promising anything, but I'll do my best to get it up as soon as coblee gives us all the genesis hash.

Please note that I will not be specifying an rpcuser or rpcpassword argument for you. It is up to you to pass this onto your daemon with the -rpcuser and -rpcpassword parameters. Also make sure you add -server and -daemon if you're running on a headless box.

Edit: I've decided to specify all the parameters, you can just wget the configuration file and be all set for mining.
Here's how the config will look once pushed to the server:

Is adding daemon=1 necessary? Mine runs perfectly fine with just server=1

I think daemon might have been deprecated by the looks of the bitcoin wiki

Edit: Nevermind, look at my post just above this.