I swear the launch is on Thursday right !? Please make it as late as possible ! Thank you !
I have no control over the launch time. Only the poll does, so go vote.
Topic: [ANN] Litecoin - a lite version of Bitcoin. Launched! - page 411. (Read 1466308 times)
I have no control over the launch time. Only the poll does, so go vote.
Looks like the launch will be in 29 hours and a bit. The actual time will be announce in about 9 hours. Stay tuned.
Question for technical people. Would it be a bad idea if I told people to add "addnode=" to their litecoin.conf file so that they will immediately talk to my client for the genesis block? Would that overwhelm my client and take my client down? Or does bitcoin handle that well?
Question for technical people. Would it be a bad idea if I told people to add "addnode=
I swear the launch is on Thursday right !? Please make it as late as possible ! Thank you !
Looks like the launch will be in 29 hours and a bit. The actual time will be announce in about 9 hours. Stay tuned.
Question for technical people. Would it be a bad idea if I told people to add "addnode=" to their litecoin.conf file so that they will immediately talk to my client for the genesis block? Would that overwhelm my client and take my client down? Or does bitcoin handle that well?
Question for technical people. Would it be a bad idea if I told people to add "addnode=
If you'd like to snag some Testnet coins to test that your client is working without mining, you can get 10 coins over at my Testnet Faucet. I originally made this for us over at IRC, but seeing as everyone over there is a testnet millionaire... yeah.. you get the point.
Starting the windows client without a litecoin.conf file and testnet=1 in it results into a nasty Visual C++ crash something about assertion.
if you read the assertion it'd tell you that you need to put "testnet=1" into your litecoin.conf in the right directory! just to be clear, any coins mined from testnet are in a way worthless, yes?
Yes, they are only meant to get you setup and prepared for mainnet, or if you're developing an application and don't want to risk real Litecoins while testing.thanks guys
just to be clear, any coins mined from testnet are in a way worthless, yes?
Worth is demanded by market. Since there will not be a market for them, they will be practically worthless ... but keep them, no reason not to.
just to be clear, any coins mined from testnet are in a way worthless, yes?
Yes, they are only meant to get you setup and prepared for mainnet, or if you're developing an application and don't want to risk real Litecoins while testing.
just to be clear, any coins mined from testnet are in a way worthless, yes?
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
Starting the windows client without a litecoin.conf file and testnet=1 in it results into a nasty Visual C++ crash something about assertion.
Well of my list, the highest is
Intel Core i5 760 2.80GHz - avg 2.16 per thread
which is 6.48MH/s using 3 out of 4
(which would imply a max of 8.64 using 4 - comparatively high for a slower CPU)
Intel Core i5 760 2.80GHz - avg 2.16 per thread
which is 6.48MH/s using 3 out of 4
(which would imply a max of 8.64 using 4 - comparatively high for a slower CPU)
Hmm - seems low.
...
Maybe your CPU only has 4? so you are actually getting double those figures? Not sure.
...
Maybe your CPU only has 4? so you are actually getting double those figures? Not sure.
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.
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?
Those speed be comparable to What speed are your getting CPU mining TENEBRIX, right?
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?
Quote
[2011-10-11 10:04:29] thread 6: 5080 hashes, 1.04 khash/sec
[2011-10-11 10:04:30] thread 0: 5123 hashes, 1.04 khash/sec
[2011-10-11 10:04:31] thread 4: 5162 hashes, 1.03 khash/sec
[2011-10-11 10:04:31] thread 1: 5140 hashes, 1.06 khash/sec
[2011-10-11 10:04:32] thread 5: 5080 hashes, 1.06 khash/sec
[2011-10-11 10:04:33] thread 3: 5265 hashes, 1.04 khash/sec
[2011-10-11 10:04:33] thread 2: 5265 hashes, 1.04 khash/sec
[2011-10-11 10:04:34] thread 6: 5080 hashes, 1.05 khash/sec
[2011-10-11 10:04:30] thread 0: 5123 hashes, 1.04 khash/sec
[2011-10-11 10:04:31] thread 4: 5162 hashes, 1.03 khash/sec
[2011-10-11 10:04:31] thread 1: 5140 hashes, 1.06 khash/sec
[2011-10-11 10:04:32] thread 5: 5080 hashes, 1.06 khash/sec
[2011-10-11 10:04:33] thread 3: 5265 hashes, 1.04 khash/sec
[2011-10-11 10:04:33] thread 2: 5265 hashes, 1.04 khash/sec
[2011-10-11 10:04:34] thread 6: 5080 hashes, 1.05 khash/sec
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.
Thanks for the tip.
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.
better safe than sorry indeed. Thanks for the tip.
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 
))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.
Thanks for the tip.
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 )) !!! 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/coblee/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!
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/coblee/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!
Please update the main post with this information or we'll certainly see many forking clients and angry miners!
Thanks for the tip.
!!! 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/coblee/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!
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/coblee/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!
Please update the main post with this information or we'll certainly see many forking clients and angry miners!
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?
Those speed be comparable to What speed are your getting CPU mining TENEBRIX, right?
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?
Quote
[2011-10-11 10:04:29] thread 6: 5080 hashes, 1.04 khash/sec
[2011-10-11 10:04:30] thread 0: 5123 hashes, 1.04 khash/sec
[2011-10-11 10:04:31] thread 4: 5162 hashes, 1.03 khash/sec
[2011-10-11 10:04:31] thread 1: 5140 hashes, 1.06 khash/sec
[2011-10-11 10:04:32] thread 5: 5080 hashes, 1.06 khash/sec
[2011-10-11 10:04:33] thread 3: 5265 hashes, 1.04 khash/sec
[2011-10-11 10:04:33] thread 2: 5265 hashes, 1.04 khash/sec
[2011-10-11 10:04:34] thread 6: 5080 hashes, 1.05 khash/sec
[2011-10-11 10:04:30] thread 0: 5123 hashes, 1.04 khash/sec
[2011-10-11 10:04:31] thread 4: 5162 hashes, 1.03 khash/sec
[2011-10-11 10:04:31] thread 1: 5140 hashes, 1.06 khash/sec
[2011-10-11 10:04:32] thread 5: 5080 hashes, 1.06 khash/sec
[2011-10-11 10:04:33] thread 3: 5265 hashes, 1.04 khash/sec
[2011-10-11 10:04:33] thread 2: 5265 hashes, 1.04 khash/sec
[2011-10-11 10:04:34] thread 6: 5080 hashes, 1.05 khash/sec
Jump to: