Install grin with Homebrew, dnf, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• grin

Project history

Grin traces its origin to the Mimblewimble paper posted anonymously to the `#bitcoin-wizards` IRC channel on August 1, 2016 under the name Tom Elvis Jedusor. Andrew Poelstra published a follow-up paper on October 10, 2016, filling in technical details and refinements.

On October 20, 2016, the pseudonymous developer Ignotus Peverell announced a minimal Mimblewimble implementation named Grin in the same IRC community. The name continued the project's literary joke: Gringotts is the wizarding bank in the Harry Potter books, and Grin became the project name for an implementation focused on privacy and compact chain state.

The genesis block was mined on January 15, 2019. The project documented itself as young and experimental at launch, with scheduled hard forks during the first two years. Development remained open and donation-funded after Ignotus Peverell disappeared from the project.

Adoption history

Grin attracted attention in cryptocurrency circles because it was one of the first substantial open-source implementations of Mimblewimble. The official repository emphasizes hidden amounts, scaling advantages, Cuckoo Cycle proof of work variants, one-minute blocks, fixed block rewards, and fee calculation based on outputs and transaction size.

Package adoption followed the needs of node operators, miners, wallet users, and protocol researchers. Homebrew, Nix, and Linux distribution packaging made the node easy to install without cloning and building the Rust workspace by hand.

The Grin RFC process became the project's main coordination mechanism for protocol and operational changes. Accepted RFCs cover governance, security processes, wallet lifecycle, node APIs, transaction formats, sync improvements, fee changes, and other changes that package maintainers and node operators need to track.

How it is used

The `grin` executable runs the node: it manages chain state, peer-to-peer networking, mining-related interfaces, node APIs, and configuration under the Grin home directory. CLI users pair it with `grin-wallet` for wallet operations.

For package-manager users, the important operational detail is that the package is not only a command but also a long-running network daemon with consensus compatibility requirements. Upgrades can matter when protocol hard forks, API changes, or sync changes are deployed.

Why package nerds care

Grin is a tidy example of a cryptocurrency package where language ecosystem, consensus protocol, and user configuration all meet. It brought a Rust-heavy codebase, privacy-focused cryptography, and scheduled consensus changes into ordinary Unix package workflows.

Its minimalism made it appealing to people who like small, inspectable command-line systems, but the node still carries the usual packaging headaches of crypto software: deterministic builds, native dependencies, network compatibility, and careful separation from wallet secrets.

Timeline

• 2016-08-01: The Mimblewimble paper was posted anonymously to `#bitcoin-wizards`.
• 2016-10-10: Andrew Poelstra published a follow-up Mimblewimble paper.
• 2016-10-20: Ignotus Peverell announced the first minimal Grin implementation.
• 2019-01-15: Grin genesis block was mined.
• 2019-2021: The project used scheduled hard forks during its first two years.
• 2020: Grin RFCs formalized project processes and technical changes across node, wallet, and governance work.

Related projects

• Mimblewimble is the protocol family Grin implements.
• grin-wallet is the reference CLI wallet for Grin users.
• grin-rfcs records accepted standards and process decisions for the project.
• Cuckoo Cycle is the proof-of-work family credited by the Grin project.

Sources

• https://docs.grin.mw/
• https://docs.grin.mw/about-grin/story/
• https://github.com/mimblewimble/grin
• https://github.com/mimblewimble/grin-rfcs