Excellent! Good job David Butkette and everyone!
3 Likes
Litecoin’s long-anticipated MWEB Upgrade is released
2 Likes
For those who don’t understand where exactly the code is released right now, go to the official github of litecoin, then click on releases, then click on tags and you will find it (v.0.21.2rc1)
very important disclaimer: code and binaries are not the same, more details on Charlie’s twitter
3 Likes
David Burkett, Hi, tnks!!
January Progress:
We did it, guys 
MWEB Release
The first MWEB release candidate is now available at https://dev.litecoin.org/. A “release candidate” (RC) is like a pre-release. It’s fully functional - miners can signal for activation, users can generate MWEB addresses, and (once activated) send to MWEB addresses - but it hasn’t been thoroughly tested for bugs yet. The more people who try out the RC and report any issues they find, the better off the final release will be. But please plan to upgrade to the full v0.21.2 release once it’s available.
Verifying the binaries
It’s recommended that you verify the release binaries, to ensure they have not been tampered with. It may be too difficult for some non-technical users, but for those capable, it’s worth trying before running the downloaded file. To do this:
- Download & install
gpgandsha256sum - Download SHA256SUMS.asc to the same directory as the downloaded release binary.
Then, from your terminal (Mac/Linux) or command prompt (Windows):
- Change directory to the location you downloaded the release binary and SHA256SUMS.asc to:
cd <insert path here> - Download my pubkey:
gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys D35621D53A1CC6A3456758D03620E9D387E55666 - Verify the signature in
SHA256SUMS.asc:
gpg --verify SHA256SUMS.asc
The response should include something like:Good signature from "David Burkett <davidburkett38@gmail.com>", telling you thatSHA256SUMS.aschas been signed by me, and has not been tampered with. - Now that we know
SHA256SUMS.ascis valid, we need to verify the release binary you downloaded matches the one inside ofSHA256SUMS.asc. As long as the release you downloaded is in the same directory asSHA256SUMs.asc, you can just run:
sha256sum --ignore-missing --check SHA256SUMS.asc
You should see your release binary listed, followed by an OK. So, if you downloaded the windows version, you’d see:
litecoin-0.21.2rc1-win64-setup.exe: OK
What’s Next?
I’ll spend the next month watching for bug reports, and fixing any issues found. Unfortunately due to the complexity of the change, bugs will exist. So far, this includes an issue that prevents some long-lived wallets from generating MWEB addresses, which I’m actively working to fix. Once we’re satisfied with the testing & fixes, we’ll likely release another release candidate (0.21.2rc2) and go from there.
Meanwhile, miners running v0.21.2rc1 can start signaling for activation at block 221760 (~Feb 25th). @losh11 is working on a website to monitor signaling and activation status, which I’ll share here once it’s available.
9 Likes
This RC version can be tested on testnet??
Testnet or mainnet
Oh. then ltcmweb address can be generated and make && send transaction?
I think make && send transaction isn’t available till the nov 2022?
Make and send MWEB tx will not available until activation, whenever that may be. Maybe this spring?
1 Like
I do not share the idea of the MWEB since so MONERO was delisted from several exchanges by UK regulations due to the privacy it has, that MWEB protocol can make the LTC die for life
Optional privacy works differently to Monero, coins cashed out on exchanges can be seen as the person has an account, the transaction is seen from one person paying another, but hides both parties’ balance. Charlie has talked to numerous exchanges and important people and all is OK
Vids on Youtube explain it better
Exchanges don’t need to support Extension Block and MWEB
(not required to continue working with the LTC network).
For the same reason there are no preconditions for changing the listing policy.
Interesting fact:
When you withdraw coins from most exchanges whey already hide you’r balance and address (from a third party), because whey withdraw from a single hot wallet, to reduce commissions and increase the security and fault tolerance of the system.
1 Like
Part about MWEB from Charlie interview to Rice Crypto Show
Final through was that people should read more about this update
2 Likes
Is the only address format change with MWEB that there will now be ltcmweb prefix addresses as well as the standard L , M or ltc1 ?
1 Like
Thanks @Lite_Diss 
I did see that thread so just wanted to check there hadn’t been any other changes.
Do you happen to know if there’s any address formatting changes for the taproot upgrade? When it came to bitcoin, we got the new bc1p prefix vs standard bech32 bc1q so keen to understand if we’re going to have anything similar when it comes to Litecoin
2 Likes
Litecoin will use ltcmweb1 for MWEB and ltc1p for Taproot.
10 Likes
Really? I’ve heard that Litecoin went down in a couple of years ago. I hope I’m not too late at investing in this amazing altcoin though.
100% uptime. Never failed. You’re thinking of the floppening Bitcoin thingy in 2010.
Or “Flappening” as some would say 
February Progress:
I’m even later than normal this month. 
Sorry about that!
Testnet Activation
After a slightly bumpy start, MWEB has successfully activated on testnet, and the chain is progressing forward. Thank you to Loshan and Charlie for driving this effort, and to the LTC community for really stepping up in a big way to help test and debug issues.
Speaking of which, there were a number of issues identified, mostly around:
1. Encrypted and non-HD wallets
Certain wallet setups were not able to generate stealth addresses with rc1, and during some flows would actually crash. Fortunately, those issues were found and reported right away, so we were able to get those fixed quickly.
2. Mining APIs
The code for solo mining was written and tested long ago, but of course, almost nobody solo mines these days. Mining is done through mining pools, which use a slightly different method for getting new mining jobs, and submitting new solutions. I didn’t have access to a mining pool at the time to test, so the stratum changes just went unimplemented. At least until last week.
Loshan and I worked together to code and test the mining API changes needed for pool mining, which he describes here. If you know any pool operators, please point them there so they can be ready for mainnet activation.
3. Wallet Transaction List
There were a few bugs around transaction building that seem to be fixed now, but most of the wallet issues are around how we display transactions. Between Mimblewimble’s pruning and coinjoining, and the way “pegging out” works with extension blocks, displaying the wallet history is one of the most complex changes we’ve had to make for MWEB.
Pegging out actually splits sends into 2 transactions, which can make for a very confusing history if we’re not careful. And I wasn’t very careful… Immediately after testnet activation, people were confused by the numbers of transactions and the amounts they were seeing. Fees displayed incorrectly, credits and debits were unreliable, and some really large or whacky numbers would appear at times. These were all just display issues, not actual problems with the amounts sent/received, but it didn’t make for a great user experience at all.
I’ve been doing my best to fix each of these issue as they’re identified, and it’s finally starting to act a little more predictably. We’ll continue to test and fix these issues until we’ve got a release candidate that we’re 100% comfortable with. Once that’s the case, we’ll create the full v0.21.2 release and start (gently) badgering node operators to upgrade and miners to start signaling.
12 Likes