lips VS litecoin

Looking at the situation I came to suspect that /u/tevador 's proposal and what Litecoin actually implemented now are two quite different things. Their proposal for non-interactive transactions does not credit or even mention Tevador.

The need for a more formally documented design became evident, so I spent the next few weeks rewriting LIP-0004 into a more complete and formally specified design, making minor tweaks along the way to harden it where I could. Clearly, I should’ve done this from the beginning, because we’ve had nearly as many reviewers of LIP-0004 in this past month as we have for the previous 1.5 years 🙂

9/10 I'll provide all of the details about how we fixed it as part of tonight's MWEB update. LIP-0004 (https://github.com/DavidBurkett/lips/blob/master/lip-0004.mediawiki) is no longer vulnerable, and the code will be soon changed to match the LIP.

You want technical? You've got it: https://github.com/ltc-mweb/litecoin/tree/0.21/doc/mweb

Great questions! No time for a thorough response right now, but I'll follow up on each point sometime over the next week. In the meantime, hopefully this can help: https://github.com/ltc-mweb/litecoin/blob/0.21/doc/mweb/stealth_addresses.md

Code Commits are still flying in... https://github.com/ltc-mweb/litecoin/commits/0.21

A fungability and privacy upgrade to Litecoin, which would potentially make it the worlds most widely accepted privacy coin, was just released on the testnet (https://github.com/ltc-mweb/litecoin/releases/tag/mwebtest) and is preparing for release and miner signaling on the mainnet. This upgrade was audited by the 3rd party auditing firm Quarkslab. See https://www.wenmweb.com, https://litecointalk.io/t/mweb-progress-update-thread/26678/282 (click Login then just click the X), https://www.reddit.com/r/litecoin/comments/qmgohm/mimblewimble_progress_update_thread_october/

Link: MWEB Testnet Release

The release process we inherited from bitcoin can be quite painful. It uses gitian to build repeatable and deterministic binaries from the source code. This means that multiple people can all build the code on different machines (and even different operating systems) and still get the same exact release binaries. We can then all compare the results and then sign the release, certifying that we all agree that the published release is safe & accurate.

For the code monkeys among you, the majority of the changes were in: scriptpubkeyman.cpp, mweb_wallet.cpp, and Keychain.cpp.