Topic: [ANN] Litecoin - a lite version of Bitcoin. Launched! - page 412. (Read 1467253 times)

Yeah, I meant 8 "virtual cores" (whatever the term is - hyperthreading cores).
Overall I got 7.42 with 7/8 "cores", the theoretical output for 8 cores should be about 8.5.

Hmm - seems low.

However, the only CPU I've mined more than one block of is Fairbrix.

All testing I've done I've used 3 threads (-t 3) out of 4 available on different versions of Linux
(and verified that it was only using 300% CPU out of 400% CPU)

Anyway, Fairbrix:
Intel i3 540 3.07GHz (xubuntu 11.04) I get avg 1.87 per thread
My desktop - old Intel Core2 Quad Q9300 2.50GHz (fc12) I get avg 1.55 per thread
(this computer )

I also time trialled it on a few other old CPUs (all 3 threads out of 4):
Intel Core i5 760 2.80GHz - avg 2.16 per thread
Intel Core2 Quad Q8200 2.33GHz - avg 1.39 per thread
Intel Core i3-2100 3.10GHz - avg 1.66 per thread
Intel Xeon E5335 2.00GHz - avg 1.53 per thread

Maybe your CPU only has 4? so you are actually getting double those figures? Not sure.

While you're at it, you might advise people to register for notifications on this thread using the notify button. If noobs find this thread, they won't have a clue they should subscribe.

Yeah. I check the thread daily but I'm not subscribed to it better safe than sorry indeed.

At first, I figured if you already read the thread, you probably subscribed to it, so you will get the message. If you just found the thread, you will just download the new code/binary anyways. But you're right, it's better to be safe.

No problem. I know a lot of people don't read this far into the thread and it'll probably get buried in it eventually. (the bitHopper thread is a perfect example of this.. (200+ pages ))

Thanks for the tip.

Please update the main post with this information or we'll certainly see many forking clients and angry miners!

About the speed - I just noted the hash rate of a single thread and multiplied by 7, assuming that each thread measures the speed independently.
Is this the case?

Miner works, mining on testnet at about 7.42 khash/sec on 7 out of 8 cores on my Intel Core i7-2600, 3.4 GHz.

Those speed be comparable to What speed are your getting CPU mining TENEBRIX, right?

Alright, wasn't sure if the earlier statement was a response to my post or not, I'll give it a try when I get the chance.

Try the new miner binary. It should work. It's based off the latest Tenebrix miner. I'm not sure how much of ArtForz's optimizations went into that miner.

Any word on my post? Instructions on how to use the Tenebrix miner on Windows for mining LTC?

Please vote in the poll: https://bitcointalksearch.org/topic/when-should-litecoin-be-launched-47418

Looks like the last 2 options are neck to neck. If you voted for the first or second option, you can change your vote if either 3rd or 4th options work better for you.

!!! IMPORTANT UPDATE !!!

In order to prevent what's known as the Zeitgeist2 51% attack where the attacker gets to change the difficulty at will and generate a ton of blocks at a low difficulty, I've released a mandatory update to the code and the clients. Please check the first post and download the new client. Or if you are building from source, do a "git pull" and recompile.

Here's the actual fix:
    https://github.com/litecoin-project/litecoin/commit/b1be77210970a6ceb3680412cc3d2f0dd4ca8fb9

Thanks to Lolcust and ArtForz for it.

If you do not update, your client will likely fork a new chain at the 2nd difficulty change (block 4032) due to a bad difficulty retarget. You don't want that! So please update your clients. And sorry again for this.

Also, I've fixed the miner binary for Windows. Please download the new miner binary. Thanks!

We don't need more of these scrypt based scam chains. Please stop. Thank you ! BCX pls attack this crap.

Litecoin was failing to build for me (on Windows Vista 32 bit).  QT compiler and was giving a load of errors:
 

I fixed it by adding -lgdi32 to one of the LIBS lines near the bottom of litecoin-qt.pro, so one of my lines now looks like
rather than just


Interestingly, for some reason it seems to matter where I put the  -lgdi32 .  If I try
...compilation fails again.  Strange!

Hope this helps.

OK, here is the testing I've done:

Client
Downloaded client for Windows, setup was easy, it seems to work.
With gen = 1, miner is 100% CPU on my 8 cores, solved a block on testnet within a few minutes.
How do you control the number of threads it's using to mine?
I assume there currently isn't a way to know the hash rate with the GUI client, right?

Encrypted wallet.
I like the Bitcoin UI with the progress bar when downloading blocks (a beta feature of Bitcoin, not invented for Litecoin).
Did a wallet backup/restore test, works well.

First bug (I don't think it was introduce in LiteCoin):
1. I mined my first two blocks.
2. Tried to transfer 10 LTC to my own address.
3. Failed because of not enough confirmation "Mined balanced will be available in 118 blocks"
4. Now, the bug: I see 3 as Number of Transactions in the overview tab, but I actually have only the 2 solved blocks.
5. This persisted even after a restart of the client ...
6. Another restart - now I see 4 as Number of Transactions, still only 2 actual transactions.

Where did the 3rd transaction come from? Is it a Bitcoin or LiteCoin bug? Should I report this on Bitcoin github?

Daemon
On first startup:
The daemon should be compiled with either -static-libgcc or -static flags. As a side note, you might want to take a look at How do I build Bitcoin source in Windows 7 (haven't looked it it myself, but it might be useful).

Downloaded lateset MinGW as a safe place to find said dll. This took some time.

Copied the dll to the daemon's folder, and now another dll was requested. Instead, added c:\MinGW to path. That did not help, so I ended up copying libstdc++-6.dll to Litecoin daemon folder as well. This seems to have worked. litecoind taking 99%, so I assume it's mining.

CTRL-C on the litecoind resulted in a crash.

I just noticed these lines in the config:
#Only uncomment this if you are running litecoind (not Litecoin QT)
#daemon=1

Not sure what are the consequences that I didn't. Tried it and it didn't resolve the crash.

Miner - seems to be the preferred way to go, as the above methods don't give any indication of hashrate.

Tenebrix - I downloaded the Windows pack a few days ago and mined TBX successfully. It's really packaged beautifully (+1 to Locust), and It Just Works™ for TBX. I have no idea, however, how to configure it to mine LTC (on testnet or realnet).
ArtForz/cpuminer was said to be faster by 20% on some machine, I would like to check it out, but would appreciate Windows binaries if those could be arranged.

Also, I understand that the builds compiled on linux might be somewhat less efficient than builds compiled on Windows, or with some other optimizations. Is there anyone who can provide optimized Windows binaries, with:
1. Reports of hashrate like Tenebrix's miner
2. Ability to configure # of threads (I guess this is included, I just haven't found it)
?

That's it for tonight. I would hope that the optimized Windows miner issue is settled before launch - we have a chance to make this a really fair coin, let's not screw it up.

@coblee - can you put the relevant information from my post in the first post in this thread?

To all, a good night, back to mining TBX for now, but can't wait to switch.

How do you plan to convince an exchange to open when you can't give them a stack of coins to start with?

Hmm OK, in 0.4.0 the scriptSig (coinbase) code has changed so they look different now.
My mistake.