Monero GUI

Monero GUI is the official reference desktop wallet — distributed by the Monero Project at getmonero.org, packaged with the `monerod` daemon, and the canonical implementation that other Monero wallets (Cake, Monerujo, Feather) variously fork from, extend, or interoperate with. Listed at Grade A · editor's pick because it is the canonical reference: when you want to verify "is this how Monero is supposed to work?", the GUI is the answer. Best for desktop users who want the most-conservative wallet posture — run your own node, store keys locally, sign transactions offline if needed, no convenience layer between you and the protocol.

Background. Monero GUI has been maintained by the Monero Project since the early days of the Monero codebase (2014-onward). Built on the same C++ core that powers `monerod` and the CLI wallet — the GUI is essentially a Qt-based frontend over the same wallet RPC interface. Distributed exclusively via getmonero.org with signed releases (PGP signatures from named Monero contributors, hash file with developer signatures, reproducible builds documented). Available for macOS, Windows, Linux — packaged as installable binaries or standalone .tar archives. The GUI bundles `monerod` so a fresh install can sync the entire blockchain locally (200+ GB and growing); for users who don't want the full-node sync, the GUI also supports remote node mode where you connect to a community-run public node or your own remote `monerod`. Open source under the BSD 3-clause license; source code at github.com/monero-project/monero-gui (the GUI specifically) and github.com/monero-project/monero (the core daemon + CLI).

What you trust. Reference implementation — the Monero Project's contributors who maintain the GUI are the same people who maintain `monerod`, the core protocol, and the cryptographic primitives; there's no "wallet team vs. protocol team" disconnect. Reproducible builds — official binaries are reproducible from source, meaning anyone with the source can verify that a downloaded binary matches what the published source compiles to. Signed releases — every release is signed by named contributors with PGP keys published on getmonero.org and on the Monero Project's well-known release-signing workflow. Local node by default — the wallet's most-conservative mode runs your own `monerod` locally so wallet queries don't leak your address graph to any third-party node. Remote node fallback — when running your own `monerod` isn't practical (Android, low-storage devices, fresh install before the chain syncs), the wallet supports community-run public nodes; the node sees query timing and IP but cannot see the wallet's keys or amounts. Cold wallet support — the GUI has first-class support for air-gapped signing workflows: create the wallet on an offline machine, export view-only data, sign transactions offline, broadcast via a separate online machine.

Operational specs. Platforms: macOS (Intel + Apple Silicon), Windows (x86_64), Linux (multiple distros). Wallet modes: full-node (bundles `monerod`, syncs ~200 GB chain locally), remote-node (connects to public or self-hosted `monerod`), watch-only (view-only wallet that can see balance + history but cannot sign), cold-signing (air-gapped offline-signing workflow). Key derivation: 25-word mnemonic seed (the canonical Monero seed format) or polyseed (newer 16-word format). Subaddresses: full support — generate unlimited subaddresses per account, label them, and use them for incoming payment isolation. Transaction features: ring signature size = 16 (Monero protocol default), automatic fee selection with manual override, optional payment IDs (legacy, deprecated for new transactions), transaction proof generation for receipts. Integrated exchange: the GUI ships with Lihui/Cake Wallet partner integrations for in-wallet swap (XMR↔BTC, etc.) — optional, disabled by default; routes through Cake Wallet's swap aggregator. Hardware wallet support: Ledger Nano S/X/Plus and Trezor Model T integration for keys-on-hardware operation. Tor/I2P proxy: configurable SOCKS proxy in settings; pair with a local Tor or I2P proxy for network-layer privacy. Languages: 30+ UI translations from the Monero translation working group.

Philosophy. Monero GUI's editorial differentiator is the most-conservative-canonical-posture — it's not the prettiest UI in the Monero ecosystem (Cake and Feather are more polished), it's not the lightest (Cake on mobile is the convenience pick), it's not the most feature-rich third-party (Monerujo has Android-specific features). What the GUI *is*: the reference implementation, with no third-party operator in the trust path, no integrated services you didn't opt into, no telemetry, no convenience layer making decisions for you. For users who want "verify everything yourself, full-node optional, air-gapped signing supported, every release signed by named protocol contributors," the GUI is the canonical pick. The trade-off: UX is functional rather than polished; first-time users coming from polished commercial wallets may find the experience more "engineering-aesthetic" than "consumer product."

Grade rationale. Grade A and editor's pick reflect: maintained by the Monero Project itself (the canonical operator); open-source BSD-3 codebase; reproducible builds documented; signed releases with PGP keys from named contributors; full-node + remote-node + cold-signing wallet modes; first-class hardware wallet support (Ledger, Trezor); subaddresses, view-only, watch-only feature parity with the protocol; no telemetry, no analytics SDK; 30+ language UI translations; over a decade of operational continuity; cross-listed in essentially every Monero wallet reference. Last verified 2026-05-13.

Useful when. You want the canonical Monero wallet — the reference implementation, no third-party operator in the trust path. You want to run your own `monerod` and the GUI's full-node mode handles bundle-and-sync. You're doing cold-signing (air-gapped offline-signing) — the GUI's first-class workflow is the canonical option in the Monero ecosystem. You're using a hardware wallet (Ledger or Trezor) for keys-on-hardware operation. You want to verify the binary against reproducible builds before installing — the GUI's release workflow supports this end-to-end. You're a Monero developer or contributor and want the same wallet the protocol team uses. You want a wallet that's reasonably feature-rich on macOS / Windows / Linux desktop without the convenience-layer additions of Cake.

Caveats. Desktop only — no first-party iOS or Android build; mobile users should use Cake Wallet (iOS + Android) or Monerujo (Android). Full-node mode requires 200+ GB of disk — growing with the chain; remote-node mode is the practical alternative for laptops or low-storage machines, but trades local-node privacy for remote-node convenience. Initial sync is slow — first-time full-node sync can take a day or more depending on hardware and network; the GUI shows progress but doesn't make it faster. UX is functional-not-polished — coming from a consumer-finance polish (Cake, Exodus), the GUI feels more like an engineering tool. This is on purpose, but it's a real friction for non-technical users. Integrated swap is via Cake Wallet's aggregator — optional and opt-in, but if enabled it routes through a third-party operator; for the most conservative posture, disable the integrated swap and use this directory's aggregator UI separately. Remote-node trust — when not running your own `monerod`, the public node sees query timing + IP (not keys or amounts), so high-threat users should run their own node or route the wallet through Tor. Hardware wallet UX has Monero-specific quirks — Monero's ring-signature signing flow is more complex on hardware than Bitcoin's; first-time hardware wallet users should expect a learning curve and verify hardware-wallet firmware compatibility against the GUI version. Tor/I2P routing requires manual setup — the GUI supports SOCKS proxy configuration but doesn't bundle Tor; you run Tor or i2pd separately and point the GUI at it. For the most-private setup, this is the canonical recipe; for users who want one-click Tor like Feather offers, the GUI is more involved.