[ANN] Litecoin - a lite version of Bitcoin. Launched!

[coblee]

Can we find out who is doing this at least ?

How do you propose we do that? No one has step forward and admitted doing this.

But my fixes seem to be working. See this last block: http://blockexplorer.sytes.net/block/046ed8ad984dd05e62807eedde8de1706b753f8f0e1b35463c48214882d17b73
The guy has started doing transactions with random amounts. Only of of those were include for free. And there were 3 that's costing him 0.1 LTC each. It's not much, but at least he's being charged for being a menace. And more profit for miners.

Everyone, please upgrade to the latest code and things will get much better. Thanks.

[1714932352]

1714932352

[1714932352]

1714932352

[1714932352]

1714932352

[BeeCee1]

But my fixes seem to be working. See this last block: http://blockexplorer.sytes.net/block/046ed8ad984dd05e62807eedde8de1706b753f8f0e1b35463c48214882d17b73
The guy has started doing transactions with random amounts. Only of of those were include for free. And there were 3 that's costing him 0.1 LTC each. It's not much, but at least he's being charged for being a menace. And more profit for miners.

He is probably going to figure out what types of transactions get in the block chain for free then try to send a bunch of those, pushing out genuine free transactions.  This will make litecoin less inviting to newbies which is bad.

I think we should come up with several algorithms for deciding which transactions are free and let miners decide which one to use (via a config file option)

It would also be good to let miners configure a blacklist of addresses that they don't want included in blocks.  I wouldn't want it populated by default, but if a user wanted to they could add addresses to it themselves and those wouldn't go in blocks or be broadcast to other connecting clients.

[coblee]

But my fixes seem to be working. See this last block: http://blockexplorer.sytes.net/block/046ed8ad984dd05e62807eedde8de1706b753f8f0e1b35463c48214882d17b73
The guy has started doing transactions with random amounts. Only of of those were include for free. And there were 3 that's costing him 0.1 LTC each. It's not much, but at least he's being charged for being a menace. And more profit for miners.

He is probably going to figure out what types of transactions get in the block chain for free then try to send a bunch of those, pushing out genuine free transactions.  This will make litecoin less inviting to newbies which is bad.

I think we should come up with several algorithms for deciding which transactions are free and let miners decide which one to use (via a config file option)

It would also be good to let miners configure a blacklist of addresses that they don't want included in blocks.  I wouldn't want it populated by default, but if a user wanted to they could add addresses to it themselves and those wouldn't go in blocks or be broadcast to other connecting clients.

This is all handled pretty well by the priority of transactions. The attacker will be resending newer coins so the priority will be lower than normal genuine transactions. So normal genuine free transactions will likely be include first before the spam transactions.

[mrx]

How to dump all private keys from a wallet without the mess of txes?

I need to dump some private keys from my spammed wallet but pywallet's dump also "take care" of those txes. Then my server nearly dead because pywallet ate up almost all ram and swap.

the reason I wanted the private keys is my vanity address (below). I didn't save the private keys to another place but i still want to keep the address (took 12hr to generate that.)

[Graet]

I've released Litecoin 0.5.0.6:
- Has the fix to reduce transaction spamming by allowing only 500 bytes of exempted transactions as oppose to 3000 bytes (in Bitcoin)
- Change the priority cutoff of free transaction to 1 litecoin day per 250 bytes.
- Disabled encrypt wallet feature since it's currently broken. encrypted wallets might still have private keys in the clear so be careful if you've already encrypted your wallet.

https://github.com/downloads/coblee/litecoin/litecoin-windows-client-0.5.0.6.zip

I've tested this on testnet. You can see that we now only exempt 3 low priority transactions per block:
http://blockexplorer.sytes.net/chain/LTCtestnet?hi=7447

Everyone, please update to the latest code and this will reduce the transaction spam and slow down the chain growth.

Updated Ozcoin - cheers coblee

[localhost]

It's not much, but at least he's being charged for being a menace. And more profit for miners.

Well, at this stage he's rather being helpful. I mean, it would have been much worse if Litecoin had kept this weakness and he or someone else then started exploited it when LTC is more established and/or when the LTC developers are less reactive. Now it's fixed for good, with not really much harm done.

[Schwede65]

I've released Litecoin 0.5.0.6:
- Has the fix to reduce transaction spamming by allowing only 500 bytes of exempted transactions as oppose to 3000 bytes (in Bitcoin)
- Change the priority cutoff of free transaction to 1 litecoin day per 250 bytes.
- Disabled encrypt wallet feature since it's currently broken. encrypted wallets might still have private keys in the clear so be careful if you've already encrypted your wallet.

https://github.com/downloads/coblee/litecoin/litecoin-windows-client-0.5.0.6.zip

I've tested this on testnet. You can see that we now only exempt 3 low priority transactions per block:
http://blockexplorer.sytes.net/chain/LTCtestnet?hi=7447

Everyone, please update to the latest code and this will reduce the transaction spam and slow down the chain growth.

excellent work again - some LTCs are on the way

[coblee]

excellent work again - some LTCs are on the way

Thanks!

[fivebells]

Well, at this stage he's rather being helpful. I mean, it would have been much worse if Litecoin had kept this weakness and he or someone else then started exploited it when LTC is more established and/or when the LTC developers are less reactive. Now it's fixed for good, with not really much harm done.

  On that note, I would like to survey all the attacks to date on bitcoin-related cryptocurrencies (litecoin, tenebrix, soildcoin and of course bitcoin itself.)   Is there a list of attacks so far somewhere?  I am aware of the "weaknesses" page on the wiki.

[terrytibbs]

Well, at this stage he's rather being helpful. I mean, it would have been much worse if Litecoin had kept this weakness and he or someone else then started exploited it when LTC is more established and/or when the LTC developers are less reactive. Now it's fixed for good, with not really much harm done.

  On that note, I would like to survey all the attacks to date on bitcoin-related cryptocurrencies (litecoin, tenebrix, soildcoin and of course bitcoin itself.)   Is there a list of attacks so far somewhere?  I am aware of the "weaknesses" page on the wiki.

There is some very basic info on the recent spam on the forum.

[fivebells]

Thanks, Terry.

[BeeCee1]

Well, at this stage he's rather being helpful. I mean, it would have been much worse if Litecoin had kept this weakness and he or someone else then started exploited it when LTC is more established and/or when the LTC developers are less reactive. Now it's fixed for good, with not really much harm done.

  On that note, I would like to survey all the attacks to date on bitcoin-related cryptocurrencies (litecoin, tenebrix, soildcoin and of course bitcoin itself.)   Is there a list of attacks so far somewhere?  I am aware of the "weaknesses" page on the wiki.

for bitcoin there is the list of Incidents  but it would be nice to have a cross-coin list.

[fivebells]

Thanks, BeeCee1.

[K.A.T]

 Hello,

Is there a list for processor (M hashes/s)  for Litecoin?? Similar to what we have in Bitcoin: https://en.bitcoin.it/wiki/Mining_hardware_comparison


 
What brings this is available types of processors Intel i3/i5/i7/Xeon and AMD X6, Opteron and FX .......

Also a person can get a cheap Opetron (possibly old) from ebay to mine for Litecoin......

Regards,,,,,

[mrx]

 Hello,

Is there a list for processor (M hashes/s)  for Litecoin?? Similar to what we have in Bitcoin: https://en.bitcoin.it/wiki/Mining_hardware_comparison


 
What brings this is available types of processors Intel i3/i5/i7/Xeon and AMD X6, Opteron and FX .......

Also a person can get a cheap Opetron (possibly old) from ebay to mine for Litecoin......

Regards,,,,,

There is a list on litecoin wiki:

https://github.com/coblee/litecoin/wiki/Mining-hardware-comparison

However there are not so much info.

[terrytibbs]

 Hello,

Is there a list for processor (M hashes/s)  for Litecoin?? Similar to what we have in Bitcoin: https://en.bitcoin.it/wiki/Mining_hardware_comparison


 
What brings this is available types of processors Intel i3/i5/i7/Xeon and AMD X6, Opteron and FX .......

Also a person can get a cheap Opetron (possibly old) from ebay to mine for Litecoin......

Regards,,,,,

There's some more detailed info on the forum.

http://liteco.in/threads/the-hardware-and-hashrate-thread.21/

[K.A.T]

 Thanks guys.

[bulanula]

Any more news on optimizations for 2600K ?

[rahl]

Anyone know what happened to the p2pool ... or my p2pool client?

Code:

21:17:05.361000     ...inserting 44356 verified shares...
21:17:06.991000     ...done loading 47501 shares!
21:17:06.992000
21:17:06.993000 Initializing work...
21:17:11.307000 Fatal error:
21:17:11.307000 Traceback (most recent call last):
21:17:11.308000   File "twisted\internet\defer.pyc", line 455, in _startRunCallbacks
21:17:11.309000
21:17:11.310000   File "twisted\internet\defer.pyc", line 542, in _runCallbacks
21:17:11.310000
21:17:11.311000   File "twisted\internet\defer.pyc", line 1076, in gotResult
21:17:11.312000
21:17:11.312000   File "twisted\internet\defer.pyc", line 1020, in _inlineCallbacks
21:17:11.313000
21:17:11.314000 --- <exception caught here> ---
21:17:11.314000   File "p2pool\main.pyc", line 222, in main
21:17:11.315000
21:17:11.316000   File "p2pool\main.pyc", line 186, in set_real_work2
21:17:11.316000
21:17:11.317000   File "p2pool\data.pyc", line 357, in think
21:17:11.317000
21:17:11.318000 exceptions.KeyError: 57603117827485759881969428621640341927497383179965498894350262008763184L

C:\Program Files (x86)\Bitcoin\Litecoin\litecoin-windows-miner-10-10-2011>

[coblee]

This spammer is quite annoying. He's started to spam 577 ltc transactions now. Due to the way we calculate priority, sending 577 coins (even with just 1 confirmation) makes it high priority enough that it can be done for free. And he's able to cram about 13 of these into each block for free: http://blockexplorer.sytes.net/block/6a73e81f628fbd612c6c1359f7c7ef06dce074d1946608b51756d08ce7e95178

There's only so much we can do about this since we can't really tell that these are spam transactions. The way to stop this is to require a transaction fee on all transactions, but I don't think we want to go that route. If you send a free transaction with higher priority, it will be include in the block before these spam transactions. Or if you want your transaction to always be include, just add a fee.

If this guy keeps sending 13 of these spam transactions per block, he will bloat the chain about 1.7mb/day. This might be something we just have to accept. This is the same way that Bitcoin works. If you have free transactions, there will be ways for malicious person to take advantage of it.

Though there is one solution I can think of. Which is to require a transaction fee on all coins sent that are not a day old. So if you try to send coins that are not a day old (i.e. don't have 576 confirmations), you need to pay 0.1 ltc fee. What do people think about that?