Grin is an open-source, proof-of-work implementation of Mimblewimble, a protocol design for confidential transactions and compact blockchain data. The project began in 2016 after an initial Mimblewimble proposal circulated under the pseudonym Tom Elvis Jedusor; Grin mainnet launched on January 15, 2019. The project’s own history traces the path from that proposal to the live network. (Grin Docs: project history)
Source note: this page is a technical overview based on Grin’s documentation and the original Mimblewimble proposal. It is not a reproduction of a separate, Grin-authored document titled “Grin Whitepaper.” The original protocol proposal and Grin’s implementation are related, but they are not the same work.
How Mimblewimble structures transactions
Mimblewimble uses Pedersen commitments to hide output amounts and range proofs to show that those amounts fall within valid bounds without revealing their values. Transactions also include kernels with signatures and validation data. This lets nodes check the protocol’s value rules without seeing the amounts being transferred. (Grin Docs: Mimblewimble introduction; Grin Docs: transaction structure)
Inputs refer to outputs that are being spent. Through cut-through, an output and its corresponding input can cancel when transactions are combined. Nodes can also prune old spent-output data while retaining what is needed to validate the chain. This reduces the historical data nodes need to store; it does not mean the entire history disappears or consensus checks are skipped. (Grin Docs: scalability and cut-through; Grin Docs: chain state and pruning)
Addresses and transaction exchange
Grin does not use fixed recipient addresses recorded on the blockchain in the way many networks do. Participants construct a transaction interactively using transaction data called a slate. “Interactive” does not mean both parties must remain online at the same time: Slatepack allows transaction data to be passed asynchronously, for example as text copied or sent through another channel. Wallets and user devices still matter to privacy. (Grin Docs: transactions; Grin RFC 0015: Slatepack)
Proof of work and GRIN issuance
Grin uses Cuckoo Cycle proof of work. Its mining rules have changed since launch: Grin’s consensus code describes Cuckatoo32+ as the primary proof of work after Hard Fork 4. Older explanations that describe Cuckaroo and Cuckatoo as two active mining paths may not describe the current consensus rules. (Grin consensus code: proof-of-work rules)
Grin’s issuance is linear: roughly 1 new GRIN per second, without scheduled halvings. With a one-minute block target, that corresponds to a base subsidy of 60 GRIN per block before transaction fees. Issuance does not stop, but Grin’s documentation says relative dilution falls below 10% after 10 years and below 5% after 20 years. Those dilution figures describe new issuance relative to accumulated supply; they should not be treated as a measure of price inflation or investment return. (Grin Docs: emission policy; Grin consensus code: block interval and subsidy)
Privacy and its limits
Commitments and transaction aggregation hide amounts and reduce some visible input-output relationships on-chain. They do not guarantee absolute anonymity. Network information when transactions are relayed, wallet-use patterns, compromised devices, or external services can reveal context beyond blockchain data. Grin uses Dandelion++ to help obscure a transaction’s network origin, but users still need to consider privacy at the network and device levels. (Grin Docs: privacy model)
Related Terms
See Also
- Bulletproofs: Short Proofs for Confidential Transactions and More — a compact range-proof construction relevant to hidden values.
- CryptoNote v2.0 — an earlier privacy design based on ring signatures and one-time stealth addresses.
- Ring Confidential Transactions — a separate design for concealing transaction amounts in Monero.
Last reviewed: October 28, 2026.
Sources
- Grin Docs. “The Story of Grin” — project history.
- Grin project. Documentation table of contents — the project’s technical documentation structure.
- Tom Elvis Jedusor. (2016). “Mimblewimble” — original proposal reproduced in the Grin project wiki.
- Grin Docs. “Mimblewimble” — commitments, range proofs, kernels, and cut-through.
- Grin Docs. “Transactions” — transaction construction and exchange.
- Grin RFC 0015. “Slatepack” — asynchronous transaction data exchange.
- Grin project. Consensus code — block interval, subsidy, and proof-of-work rules.
- Grin Docs. “Emission” — linear issuance and relative dilution.
- Grin Docs. “Privacy” — protections and privacy limits.
- Grin Docs. “State and Pruning” — data retained by nodes.