Built around what a Ravencoin desktop user actually needs.
Self-custody first. Assets as first-class objects. Hardware-device pairing. A short, opinionated feature set instead of a wall of toggles.
Self-custody
Your seed phrase is generated locally and never leaves the machine.
Native assets
Issue, send, and inspect RVN assets, sub-assets, and unique tokens.
Hardware signing
Pair Ledger and Trezor for cold transaction signing.
Light-client speed
Connect to trusted nodes — no full chain download required.
Multi-signature
Create m-of-n multisig wallets for treasuries and cold storage.
Mainnet / testnet
One-click network switch for development and rehearsal.
KAWPOW aware
Built against the current Ravencoin protocol, not a generic Bitcoin fork.
Open source
Read the code, build it yourself, ship a patch.
A short feature list, on purpose.
Most wallet feature lists exist to fill a marketing page. This one exists because every item on it solves a problem a Ravencoin desktop user actually has. The wallet does not try to be a trading app, a swap aggregator, a portfolio tracker, or a newsfeed — it is a wallet, and that is the entire job.
The first decision behind every feature is whether it keeps you in control of your keys. If it does not, it does not ship.
There is no account. There is no remote backup. There is no "social recovery" that introduces a third party between you and the wallet. The seed is generated locally, encrypted at rest, and decrypted only in memory and only when signing. A hardware-wallet pairing keeps the seed off the host entirely. Every feature above this line in the wallet is built on top of that one constraint.
Assets as a first-class surface
Ravencoin's asset layer is the chain's defining feature, and the wallet treats it that way. You can issue a named asset, mint sub-assets under it, create unique items, and handle restricted-and-qualifier patterns from the same UI you use to send RVN. Asset balances live in a separate column; transfers, reissues, and burns are first-class actions, not buried in a developer-tools menu. Read the assets deep-dive for the full feature list.
- Issue named assets, sub-assets, and unique items from the UI.
- Reissue when the rules allow it; burn when they don't.
- Pin IPFS metadata on issuance.
- Sign every asset transaction on a hardware device if desired.
- No smart-contract wrappers; assets are protocol-native UTXOs.
Ledger and Trezor both support Ravencoin through Electrum RVN. The desktop wallet builds the transaction; the device displays the destination and amount on its own screen; you approve the spend on the device, not on the computer. That isolation is the single biggest practical security upgrade available to a Ravencoin holder.
The wallet does not download the Ravencoin blockchain. It connects to a configurable set of Electrum-protocol servers, asks them for the data your addresses care about, and verifies the relevant proofs. It is usable within seconds of installation. If you prefer maximum trust minimisation, you can run Ravencoin Core on your own machine, point Electrum RVN at it, and validate everything yourself — both paths are first-class.
Multi-signature for treasuries and cold storage
The wallet supports standard m-of-n multi-signature setups — 2-of-3, 3-of-5, and other configurations — with PSBT (Partially Signed Bitcoin Transaction) for offline coordination between signers. Pair each cosigner with a hardware device and the resulting wallet is suitable for shared treasuries, DAO operational accounts, family cold-storage setups, or any other situation where one-key control is not enough.
No in-app swap aggregator (those add an attack surface and a spread). No fiat on-ramp (that requires KYC integration we do not want to inherit). No portfolio chart with USD prices (that is what a block explorer or a portfolio tracker is for). No newsfeed. No social features. No auto-updater. The wallet is intentionally small, and every feature missing from it is missing on purpose.
Every feature is an attack surface. The wallet ships the primitives that genuinely matter for Ravencoin — non-custodial keys, asset support, hardware pairing, multi-sig, verifiable builds — and deliberately omits convenience features (in-app swaps, fiat on-ramps, push notifications, social discovery) that increase risk without changing what the wallet actually does. The result is a smaller binary, a shorter audit, and a longer useful life.
How features map to use cases
Hold RVN long-term: hardware-signer pairing + cold storage workflow. Issue or transfer assets: native asset tab with full metadata, sub-asset, and unique-asset support. Run a shared treasury: native multi-sig coordination. Build on top of the wallet: documented xpub-based watch-only mode and standard descriptor support. The features aren't a checklist of marketing items; they're a toolkit for specific real-world jobs.
A handful of features are present for advanced users and invisible to everyone else: descriptor-based wallet import and export, custom server selection, coin-control for manual UTXO selection, custom fee bumping, and signed message tools for proof-of-ownership. None of these clutter the default UI; all of them are one menu away when you need them. That balance — useful defaults, real depth on demand — ships in every Electrum RVN build for Windows, macOS, and Linux.
Explore by capability.
Continue with Electrum RVN
- manage Ravencoin assets — native asset issuance and transfers
- Ledger Ravencoin setup — pair a Ledger hardware signer
- Electrum RVN download — get the signed desktop build
Run your own Ravencoin wallet.
Open-source, lightweight, and built for the desktop user who wants real control over keys and assets. Download the wallet directly from our download page — signed installers for every operating system.