Leaked Developer Messages: “Litecoin Has Zero Active Development” As Dusting Attack Hits

[Mark Mason]

Leaked Developer Messages: “Litecoin Has Zero Active Development” As Dusting Attack Hits

Leaked messages from a Litecoin developer chat show no evidence of active development on privacy features as Litecoin users are hit with a large-scale privacy-compromising attack.

According to messages leaked from a Telegram chat with developers, Franklyn Richards, Director of the Litecoin Foundation, expressed frustration at the lack of any solid development progress on touted upcoming privacy improvements and vague answers from the development team:

Read more - https://dashnews.org/leaked-develop...ro-active-development-as-dusting-attack-hits/​

 

[karlhenning]

Is it possible to find out from which wallet a privateSend-request came from and which new addresses in the same wallet received the privatised Coins?

In theory it should be possible to perform a dusting attack to each privateSend round inputs and outputs.

If the Dash wallet combines the dust from input and output of privateSend transactions the puzzle is solved and I know which addresses belong to which wallets.
Even if the two out of three wallets combine the dust, so I know which addresses belong to the third wallet - even if the third wallet did not spend any privatised coins.

Or is it the case that the Dash wallet and Dash core ignore any dust to avoid successful dusting attacks?

Or at least Dash wallet and Dash core never combines "public" outputs and "private" outputs to new transactions as inputs?