OK, here is the testing I've done:
ClientDownloaded 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?
DaemonOn first startup:
The program can't start because of libgcc_s_dw2-1.dll is missing from your computer. Try reinstalling the program to fix this problem.
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.
