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.

Open Source Litecoin is fully decentralized in the fact any one person could submit code into the network and as long as a majority of miners agree to that fork it will be implimented. This is similar to bitcoin.

Progress continues with the integration of Litecoin code changes into the v24 Bitcoin codebase. The month of May saw a major milestone with the resolution of all remaining functional tests for the pre-MWEB merge task. The code has been submitted for review here.

git clone https://github.com/litecoin-project/litecoin.git

"If upgrading to 0.21.2 after MWEB has activated, you must resync to download MWEB blocks." https://github.com/litecoin-project/litecoin/releases

I tried following this tutorial: https://github.com/litecoin-project/litecoin/blob/master/doc/build-osx.md

However, this serialization format seems to contradict with BIP 0144, which states: "if the witness is empty, the old serialization format must be used." also contradict the comments in the litecoin source code at https://github.com/litecoin-project/litecoin/blob/master/src/primitives/transaction.h

In order to add MWEB support to PSBTs, I first had to merge in PSBTv2 (BIP-0370), which can be seen here. I then defined the MWEB fields we needed to add, and added them to the PSBT data structures along with serialization and deserialization here.

A pull request has also been submitted for downloading and verifying HogEx transactions, MWEB headers, and the UTXO leafset bitmap. This covers steps 2 and 3 of the light client sync process.