Mimblewimble

The problem the paper names

Bitcoin keeps every spent output forever, and it keeps the script that spent it. Mimblewimble asks whether a chain whose only job is value transfer can commit to the current unspent set and a kernel of transactions, and drop the rest.

What the design proposes

• Values sit inside Pedersen commitments. The chain checks that inputs minus outputs sum to zero, plus the fee.
• Spent outputs can be cut through, because only the excess and the kernels need to stay.
• There is no script in the classic Bitcoin sense. The transaction is the proof of balance.

How the mechanism is specified

• Two parties build a transaction by contributing blinding factors so neither learns the other's value, and the combined commitment balances.
• A cut-through of intermediate outputs shrinks what a new node must download, if the kernels remain.
• The note is deliberately small. It does not specify a full peer-to-peer network.

What this page does not treat as proven

• Grin and Beam added consensus, wallets and policy that are not in the 2016 text.
• Removing scripts also removes the easy place to put application logic. That is a constraint, not a footnote.
• Confidentiality here is about amounts and the pruned graph, not a general smart-contract privacy claim.

Why a venture studio still reads it

Relevant when a venture only needs to move value and is about to inherit a general-purpose chain out of habit. Mimblewimble is the argument for storing the unspent set, not the autobiography of every coin.