Mimblewimble is a design for a blockchain protocol that aims to make transactions private and keep the chain small. It hides transaction amounts, does without the public addresses found in Bitcoin, and lets nodes delete most data about spent coins while still being able to check that no money was created from nothing. It is used by the cryptocurrencies Grin and Beam and, as an optional extension, by Litecoin.
The design was first described in a text posted in 2016 under the pseudonym Tom Elvis Jedusor, the French name of the villain in the Harry Potter books; "mimblewimble" is a tongue-tying spell from the same series. The author was never identified. Mimblewimble belongs to the wider family of privacy coin technologies alongside Monero and Zcash, but it reaches privacy by a different route.
History
The original Jedusor text appeared in mid-2016 on a channel used by Bitcoin researchers. It drew on earlier work by Bitcoin developers, notably confidential transactions, a way of hiding amounts proposed by Gregory Maxwell, and the idea of merging transactions together. Later in 2016 the cryptographer Andrew Poelstra published a more formal paper that tightened the security arguments and filled gaps in the original.
Two independent projects launched mainnets in January 2019. Grin was a volunteer, community-run project with no premine and a fixed issuance of new coins per second. Beam was run by a company and added features such as optional auditability. Litecoin later adopted a version of the design: the Mimblewimble Extension Blocks (MWEB) upgrade activated on the Litecoin network in 2022, giving users an optional private side area next to the normal transparent chain.
How it works
A Mimblewimble chain still tracks coins as outputs, much like the unspent transaction outputs (UTXOs) of Bitcoin, but each output is stored as a cryptographic commitment instead of a plain amount and address. Several ideas combine:
- Confidential amounts. Each output is a Pedersen commitment, a number built from elliptic curve points that hides the amount but can still be added up. Nodes check that inputs minus outputs balance to zero without learning the values. A range proof shows that no output is negative.
- No addresses. Ownership is proved by knowing a secret "blinding factor" that works like a private key. Sender and receiver normally cooperate to build a transaction, so there is no address written on the chain.
- Kernels. Each transaction leaves a small signed record, the kernel, which proves it was authorised and carries the fee. Kernels are kept forever.
- Cut-through. When one transaction's output is spent by a later transaction in the same block, or later in history, the intermediate output can be removed, because only the overall balance matters.
Because of cut-through, a new full node does not need every past transaction. It downloads the current set of unspent outputs, the kernels and the block headers, and can still verify that total supply matches the issuance schedule.
Privacy and scalability
The design aims at two goals that usually pull against each other. On privacy, amounts are hidden by default and, since transactions in a block can be merged, an outside observer finds it harder to link a given input to a given output. This resembles a built-in form of CoinJoin. On scalability, deleting spent outputs keeps storage growth closer to the number of live coins than to the full history.
The privacy is not complete. Researchers showed in 2019 that a node watching the network closely could often see transactions before they were merged and so link inputs and outputs. Projects responded with techniques that delay and mix how transactions spread between nodes, but the weakness shows that merging alone does not guarantee anonymity in the way that Monero's ring signatures or Zcash's zk-SNARKs try to.
Limitations and regulatory issues
- Interactive transactions. In the basic design the receiver must take part in building a transaction, which makes simple one-way payments and exchange withdrawals more awkward. Later work added ways to reduce this.
- Limited scripting. Without addresses and with hidden amounts, the design supports far fewer programmable conditions than smart contracts on other chains.
- Exchange and compliance pressure. Privacy features make address screening and Travel Rule checks harder. After Litecoin adopted MWEB, some exchanges, particularly in South Korea, restricted or delisted LTC, citing rules on privacy-enhancing coins.
Mimblewimble therefore sits as a specialised design: a compact, amount-hiding ledger that trades programmability and some ease of use for privacy and smaller storage.
Ref 1070001222