Litecoin MWEB (Mimblewimble Extension Blocks) Hub
Verified MWEB wallet compatibility, peg-in and peg-out mechanics, ltcmweb1 stealth address structure, and Core release updates based strictly on reviewed documentation and reproducible tests.
MWEB
In brief Litecoin's optional layer that conceals amounts inside it, while base-chain and boundary activity can still reveal information.
Mimblewimble Extension Blocks, activated on Litecoin in May 2022. MWEB conceals amounts inside the extension layer; the base chain and boundary transfers can reveal information. Use maintained software and review the 2026 security postmortem.
For example An MWEB transfer uses compatible software and a different address format from an ordinary transparent Litecoin transfer.
Common mistake Assuming every LTC wallet or exchange accepts MWEB addresses, or that optional privacy removes all possible information leaks.
Full glossary entryOptional: what would make this clearer?
Choose one reason, or leave without answering.
Address
In brief An encoded payment destination whose network, owner and wallet compatibility still need checking.
An encoded destination for a payment. Common transparent Litecoin addresses begin with L, M or ltc1; MWEB uses a different address format. An address is not a bank account or proof of identity. Check network and wallet compatibility before sending.
For example To receive LTC, copy a Litecoin receiving address from your wallet and check it against the address shown to the sender.
Common mistake A valid-looking address does not prove that it belongs to the intended person or uses the network the sender selected.
Full glossary entryOptional: what would make this clearer?
Choose one reason, or leave without answering.
Bech32
In brief An error-detecting address format for Litecoin's version-0 SegWit addresses, distinct from Bech32m for later versions.
An address encoding with an error-detecting checksum. Litecoin's native witness-version-0 addresses use Bech32 and begin ltc1q on mainnet. Later witness versions use the related Bech32m encoding. A valid checksum does not identify the owner or guarantee wallet support.
For example A wallet can recognize an ltc1q address while an older sending service still refuses that format.
Common mistake Treating every ltc1 address as the same script type or assuming a valid address guarantees that a service will credit the payment.
Full glossary entryOptional: what would make this clearer?
Choose one reason, or leave without answering.
Node
In brief A participant running network software; a full node checks rules but need not keep all old block files.
A participant running network software. A full node independently validates rules; a pruned full node can discard older block files after validation. Not every node stores the complete historical blockchain.
For example A pruned full node checks the chain but later discards old block files to reduce disk use.
Common mistake Assuming every node is a miner, or that pruning means it skipped consensus validation.
Full glossary entryOptional: what would make this clearer?
Choose one reason, or leave without answering.
Wallet
In brief Software or a device for managing wallet keys and payments, though a watch-only setup cannot sign on its own.
Software or a device that manages keys and helps you receive and send Litecoin. Coins are recorded on the blockchain. A watch-only wallet can show addresses and transactions without holding the keys needed to spend.
For example One wallet can generate several receiving addresses and still show them as a single combined balance.
Common mistake Thinking coins live inside the app, or that seeing a balance proves that the wallet can sign a spend.
Full glossary entryOptional: what would make this clearer?
Choose one reason, or leave without answering.
What MWEB changes — and what it does not
Mimblewimble Extension Blocks (MWEB) operate as an optional parallel layer linked to every Litecoin block since activation in May 2022. Coins moved into MWEB via a peg-in conceal transaction amounts and hide linkable input-output graphs using Confidential Transactions, Pedersen commitments, and one-time stealth keys (ltcmweb1... addresses).
Standard transparent addresses (L..., M..., 3..., ltc1q..., ltc1p...) remain completely public on the main chain. Sending between standard transparent addresses does not automatically use MWEB privacy.
L, M, ltc1q). Depositing directly from an MWEB balance or attempting to withdraw straight to a ltcmweb1... address often fails validation unless the counterparty explicitly documents MWEB support. Peg-out to a transparent self-custody address first when depositing to a transparent-only service.
Latest observed Litecoin Core release
v0.21.5.8 · Published 12 Sep 2026
Release metadata retrieved 15 Nov 2026, 21:15 UTC. MWEB node and relay validation behavior is governed by Litecoin Core release notes; see our Core updates tracker.
Reviewed MWEB wallet support matrix
Rows below are sourced directly from our wallet evidence ledger without extrapolating unverified claims across platforms or app builds:
| Wallet | MWEB status | Documented MWEB platforms | Reviewed | Important scope caveat |
|---|---|---|---|---|
| Litecoin CoreDesktop full node | Documented | Desktop | 2026-09-24 | Published experiments cover eight 2-of-3 signing combinations and 14 checks of encrypted wallet-file recovery, receiving and spending across three standard address types. MWEB, mnemonic migration, GUI and hardware recovery are not tested. |
| Cake WalletMobile and desktop software wallet | Documented on iOS and Android only | Mobile | 2026-09-24 | The Litecoin documentation explicitly excludes MWEB addresses and peg-in/out on desktop. A desktop Litecoin balance is not evidence of desktop MWEB support. |
| Electrum-LTCDesktop software wallet | Not verified in the cited documentation | None verified | 2026-09-27 | Signed 4.2.2.1 Windows executable tested offline: native-seed and watch-only restores, account-key imports and message signing. No GUI BIP39 wizard, mobile app, balance discovery or mainnet spend tested. The pinned release is not a security recommendation. |
| Nexus WalletMobile Litecoin wallet | Private balance and ltcmweb1 addresses documented | Mobile | 2026-09-24 | The official help center distinguishes regular and private balances. Check the current app and both ends of the payment route; a standard receiving address is not a private MWEB address. |
| Trezor + Trezor SuiteHardware wallet with companion software | Not verified for Litecoin in this review | None verified | 2026-09-24 | Trezor lists native Litecoin support in Suite. That alone does not establish support for MWEB or every advanced Litecoin feature. The documented litecoin: URI handler is desktop-only. |
Three distinct MWEB transaction paths
| Flow | Source → Destination | Public blockchain visibility |
|---|---|---|
| Peg-in | Transparent (L/M/ltc1) → ltcmweb1... | The peg-in amount entering MWEB is visible on the canonical base chain; subsequent MWEB hops are confidential. |
| Pure MWEB | ltcmweb1... → ltcmweb1... | Amounts, sender inputs, and stealth recipients stay concealed inside extension blocks; mainchain explorers cannot decode outputs. |
| Peg-out | ltcmweb1... → Transparent (L/M/ltc1) | The amount exiting MWEB to the transparent destination address becomes visible at the peg-out output. |
Frequently asked questions
Are MWEB transfers enabled by default in all Litecoin wallets?
Can exchanges withdraw directly to an ltcmweb1 address?
L, M or ltc1q address in your own wallet before sending to transparent-only platforms.