jwinterm
0d5d745311
Windows crash chain (exposed by the embedded-node default): - main.cpp: force the QtQuick software renderer. The Mining tab's QQuickWidget drove the default RHI/GL path and faulted (0xc0000005) on broken-GL hosts (VirtualBox VMSVGA), crashing the app and orphaning the embedded node. Real hardware was unaffected. - ChildProcessGuard + DaemonManager/TorManager: kernel-level die-with-parent (Windows Job Object KILL_ON_JOB_CLOSE / Linux PR_SET_PDEATHSIG) so the embedded wownerod and bundled tor never survive a wowlet exit or crash. - DaemonManager: verify-before-adopt via get_info (nettype/height) instead of trusting a bare open RPC port, so a stale/orphan node is never adopted. Node/Tor lifecycle + remote-node connectivity: - config: torPrivacyLevel default -> allTorExceptNode. NEVER sync blocks over Tor; the wallet's node connection is always clearnet. Tor is only for tx broadcast, so remote nodes work with or without Tor. - nodes: add Nodes::reconnect() (clear failure blocklist + force reconnect); node/Tor toggle handlers use it so a transient outage no longer strands the wallet at "Disconnected". - MainWindow/SettingsDialog: reconnect on node/Tor toggle and on the async daemonStateChanged (closes the start() race; a freshly-toggled local node connects immediately). - TorManager: reset retry/unpack state in init() so a system<->bundled Tor re-toggle can start again; quiesce on stop(). Linux unpackBins() rework (mkpath + presence-based unpack + graceful return-false), getVersion() arg fix, and a missing-binary start guard. - build.yml: derive TOR_VERSION from the embedded tor binary (a hardcoded bundle number made unpackBins rewrite Tor every launch). - depends/funcs.mk: confine cross-cmake find_package to the depends sysroot so host -dev libraries don't leak into the build.
Feather Wallet
Feather is a free Monero desktop wallet for Linux, Tails, macOS and Windows. It is written in C++ with the Qt framework.
- easy-to-use, small and fast - Feather runs well on any modern hardware, including virtual machines and live operating systems.
- beginner friendly, but also caters to advanced Monero users by providing a feature set that is on par with the official CLI.
- ships with sane defaults that suit most users, but can also be configured for high or uncommon threat models.
- serves as a testing grounds for experimental features that may later be adopted in the reference wallets.
Download
You can download Feather from featherwallet.org or GitHub.
If you need help installing Feather, check the installation documentation.
We recommend that you verify downloads with GPG. Releases are signed with our release signing key. The fingerprint is:
8185 E158 A333 30C7 FD61 BC0D 1F76 E155 CEFB A71C
Windows releases are code-signed for free by SignPath.io, certificate by SignPath Foundation.
Resources
- Official Site
- Documentation
- Git Repository
- Matrix
- IRC:
#featheron OFTC - Mail: dev@featherwallet.org
If you need help with your wallet, please contact us via Matrix or IRC. If you don't have an IRC client, you can join the room via webchat. If you don’t receive a response immediately please idle in the room.
Release Builds
To learn how to run a bootstrappable release build, see: contrib/guix/README.md
For release attestations, see the feather-sigs repo.
For release policy, see: RELEASE.md
Development
If you are looking to set up a development environment for Feather, see HACKING.md.
It is highly recommended that you join our Matrix or IRC channel if you are hacking on Feather. Idling in this channel is the best way to stay updated on best practices and new developments.
For information on how Feather is maintained, see: MAINTENANCE.md
To report a security vulnerability, see: SECURITY.md
License
Feather is free and open-source software, licensed under BSD-3.
Copyright (c) 2020-2025, The Monero Project