Author

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

legendary
Activity: 1064
Merit: 1001
So I got my first block I'm a happy camper.  Cheesy

wobber: what's up with you? first you post a screenshot of a 30k+ gox account, then a thread about "when will we have new highs" 3 days ago and now you want to buy up these litecoins for a few BTC?
canttelliftrollingorjustverystupid.jpg

Don't really follow you. Would you invest more in litecoin?Huh
legendary
Activity: 1666
Merit: 1057
Marketing manager - GO MP
So I got my first block I'm a happy camper.  Cheesy

wobber: what's up with you? first you post a screenshot of a 30k+ gox account, then a thread about "when will we have new highs" 3 days ago and now you want to buy up these litecoins for a few BTC?
canttelliftrollingorjustverystupid.jpg
legendary
Activity: 1064
Merit: 1001
25b73458d438fa7b22befaa2c11a09d2256ce26549fe544d0f769554eedc2623

send litecoins to: LTKcRybcn3tTENPgLvk2fdghMZgXBQHBpd
newbie
Activity: 15
Merit: 0
I managed to mine a block so all is well.  Though Time Warner picked today for my internet service to go out so I'm stealing my neighbor's wi-fi for the time being...
legendary
Activity: 1064
Merit: 1001
Ok. I want 5000.

LE: Daaamn! 500! Five hundred!
full member
Activity: 154
Merit: 100
Actual trade offer:

Offering .4 btc for 400 LTC
legendary
Activity: 1064
Merit: 1001
I want to buy Litecoins! I will offer 1 bitcoin for 5000 coins. Let's be the first to trade!

Was 2000 before you edited, I'll offer 1000 @.01 BTC each.

Yes, but even 1 bitcoin for 2000 was overevaluated. Sorry, first transaction 1 btc = 5000  ltc
legendary
Activity: 1666
Merit: 1057
Marketing manager - GO MP


Well, I have but I only got one connection so far  Huh
probably phelix which I added with connect=

also I got 16 orphans and no blocks  Sad

Sounds like a network problem. Check cabling, reset switches/routers, do some traceroutes to US IP addresses (BTC pools e.g.) and pings as well (to check for packet loss). This kind of results says that something's wrong.
I fixed the one connection problem,(was the manual connection in the conf) but no blocks yet.
Get a ping of 27ms to bitclockers with 15 hops. strange
sr. member
Activity: 313
Merit: 251
Third score
How long should it take me to mine a block using the Windows client on a 2500k?  Need to see if my miner is working...

Currently you need to complete on average 4.2 Mhashes. Divide by your KH/s and you get the average number of seconds to find a block.
newbie
Activity: 15
Merit: 0
How long should it take me to mine a block using the Windows client on a 2500k?  Need to see if my miner is working...
legendary
Activity: 1064
Merit: 1001
I want to buy Litecoins! I will offer 1 bitcoin for 5000 coins. Let's be the first to trade!
sr. member
Activity: 313
Merit: 251
Third score


Well, I have but I only got one connection so far  Huh
probably phelix which I added with connect=

also I got 16 orphans and no blocks  Sad

Sounds like a network problem. Check cabling, reset switches/routers, do some traceroutes to US IP addresses (BTC pools e.g.) and pings as well (to check for packet loss). This kind of results says that something's wrong.
donator
Activity: 1654
Merit: 1351
Creator of Litecoin. Cryptocurrency enthusiast.
I am mining very smoothly , do I need to update?

I just checked in code to lock in block 4032 after diff change.
Please grab latest source. Windows client coming soon.

Windows client here: https://github.com/downloads/coblee/litecoin/litecoin-windows-client-40101.zip

Everyone please update.

Unfortunately twobits is asleep and can't help me build a windows daemon. And I only trust him to do that right now.
So for those running on the daemon, you can stay with your current binary. As long as enough people are running the new build, we should be good against an attack. Thanks.

To check to see if you are running latest client, getinfo should return version 40101.

If you don't want to get wiped out by a 51% attack, you should update. Just stop and the start the new client. You will be down just a few seconds.


Coblee,

Not meaning to be picky but you cannot update against a 51% attack. You can hard code the lock in, but that is it. The only thing that protects against a 51% attack is hash power, that's it. With your lock in you can back to a restore point basically after the 51% attack has concluded or enough miners update with a client that recognizes the proper fork only.

~BCX~

Yes, I know that. But updating to the latest lock will deter an attack that was starting on a block before the lock. So it does help. And when that happens, the chain will fork. So if enough miners get the latest code with the lock, they will be on the proper fork. And I expect eventually pools and exchanges to be on the proper fork, so there's no reason for a miner to not update their client and stay on the attacker's fork.

Since we know that hash power protects against 51% attacks, right now there's way too many orphans due to the difficulty being low. So if an attacker is building their own chain, they only need ~900mhash/s to succeed even though our current network hash rate is much higher than that. So that's why I will keep doing the locks until the difficulty catches up.
hero member
Activity: 756
Merit: 500
Thanks will do Smiley I don't want my 7 blocks wipe out Smiley

I am mining very smoothly , do I need to update?

I just checked in code to lock in block 4032 after diff change.
Please grab latest source. Windows client coming soon.

Windows client here: https://github.com/downloads/coblee/litecoin/litecoin-windows-client-40101.zip

Everyone please update.

Unfortunately twobits is asleep and can't help me build a windows daemon. And I only trust him to do that right now.
So for those running on the daemon, you can stay with your current binary. As long as enough people are running the new build, we should be good against an attack. Thanks.

To check to see if you are running latest client, getinfo should return version 40101.

If you don't want to get wiped out by a 51% attack, you should update. Just stop and the start the new client. You will be down just a few seconds.
legendary
Activity: 1666
Merit: 1057
Marketing manager - GO MP
I am mining very smoothly , do I need to update?

I just checked in code to lock in block 4032 after diff change.
Please grab latest source. Windows client coming soon.

Windows client here: https://github.com/downloads/coblee/litecoin/litecoin-windows-client-40101.zip

Everyone please update.

Unfortunately twobits is asleep and can't help me build a windows daemon. And I only trust him to do that right now.
So for those running on the daemon, you can stay with your current binary. As long as enough people are running the new build, we should be good against an attack. Thanks.

To check to see if you are running latest client, getinfo should return version 40101.

If you don't want to get wiped out by a 51% attack, you should update. Just stop and the start the new client. You will be down just a few seconds.

Well, I have but I only got one connection so far  Huh
probably phelix which I added with connect=

also I got 16 orphans and no blocks  Sad
donator
Activity: 1654
Merit: 1351
Creator of Litecoin. Cryptocurrency enthusiast.
So how often are you going to lock in blocks?  Every retarget will get a bit out of control I'm thinking.


I will lock in the next retarget 6048 and then I will go to sleep and maybe another lock in when I wake up. We'll see. Once the difficulty catches up to the network, it would be harder for us to get attacked.
full member
Activity: 154
Merit: 100
So how often are you going to lock in blocks?  Every retarget will get a bit out of control I'm thinking.
legendary
Activity: 1708
Merit: 1020
does it help to play with the -s factor? I tried lower values but did not notice a difference.

what happened to the idea of a super node for everybody to connect to? my ip is 85.181.140.125:9333 in case anyone would like to connect.  Grin



Tell eme if you notice a slow down LOL  Grin Grin Grin

hehe my connections almost doubled Wink

You like that huh? Cool....watch it drop now.

well, connections hopped arround between 26 and 32  was that everything?  Tongue



Yep, I don't wanna mess you up too bad. That's one of my pool killers, that was a single thread from 1 EC2 jumping across various ports.
that's the spirit

hope it is not you messing with deepbit and slush?
donator
Activity: 1654
Merit: 1351
Creator of Litecoin. Cryptocurrency enthusiast.
I am mining very smoothly , do I need to update?

I just checked in code to lock in block 4032 after diff change.
Please grab latest source. Windows client coming soon.

Windows client here: https://github.com/downloads/coblee/litecoin/litecoin-windows-client-40101.zip

Everyone please update.

Unfortunately twobits is asleep and can't help me build a windows daemon. And I only trust him to do that right now.
So for those running on the daemon, you can stay with your current binary. As long as enough people are running the new build, we should be good against an attack. Thanks.

To check to see if you are running latest client, getinfo should return version 40101.

If you don't want to get wiped out by a 51% attack, you should update. Just stop and the start the new client. You will be down just a few seconds.
hero member
Activity: 756
Merit: 500
I am mining very smoothly , do I need to update?

I just checked in code to lock in block 4032 after diff change.
Please grab latest source. Windows client coming soon.

Windows client here: https://github.com/downloads/coblee/litecoin/litecoin-windows-client-40101.zip

Everyone please update.

Unfortunately twobits is asleep and can't help me build a windows daemon. And I only trust him to do that right now.
So for those running on the daemon, you can stay with your current binary. As long as enough people are running the new build, we should be good against an attack. Thanks.

To check to see if you are running latest client, getinfo should return version 40101.
Jump to: