Trust comes from what you can verify yourself.

The wallet's security posture in one page: how keys are generated, how they're stored, what the build process looks like, and what the threat model actually is.

§ walletRVN/desktop
Block time1 min
Reward2,500 RVN
Supply cap21,000,000,000
AlgorithmKAWPOW
balance
12,430.50 RVN

Local key generation

Seeds are produced from system entropy on your machine. Nothing is sent anywhere.

Encrypted wallet file

Seeds and private keys are stored encrypted with a password you choose.

Hardware signing

Ledger and Trezor pairing keeps the seed off the host entirely.

Reproducible builds

Build instructions are public — rebuild the binary from source and confirm it matches the release.

Open source

Source is public. Build the binary yourself and compare against the release if you want zero trust.

Honest about limits

A wallet cannot save you from a compromised OS, a malicious display, or a leaked seed phrase.

What Electrum RVN actually protects, and what it cannot.

A wallet is software; its security claims have to be specific. This section walks through what the wallet does for you, what assumptions it makes about your machine, and what kinds of attacks it cannot meaningfully defend against — so you can build the rest of your setup around the real limits.

For the wallet itself: yes — open source, light-client, non-custodial, and reproducibly built. The risk surface is overwhelmingly about where you got the binary and how you store the seed.

The most common way Ravencoin holders lose funds is not a "wallet hack". It is a search-ad or third-party-portal download of a modified clone that exfiltrates the seed on first use, or a seed phrase typed into a phishing page that looks like the wallet but isn't. Verify the binary, never type the seed into anything that isn't this wallet during recovery, and most of the realistic attack surface disappears.

How keys are generated and stored

On first run, the wallet asks the operating system's cryptographic random source for entropy and derives a standard BIP-39 12-word seed from it. The seed is shown once for backup, then encrypted at rest with the password you set. The wallet file lives in the per-OS application data directory; the seed and private keys are never written in plaintext, never sent over the network, and never copied to any cloud service.

  • Seed is generated locally from OS entropy — not from a server.
  • Wallet file is encrypted with a password you choose.
  • Private keys are decrypted only in memory and only when signing.
  • Hardware-wallet mode keeps the seed off the host entirely.
  • Nothing is sent to any analytics or telemetry endpoint.

The build process is reproducible — anyone with the source can rebuild the binaries and confirm they match the ones distributed on the download page. That is the only honest way to make "trust us" optional: verify the artefact yourself.

Compromised network nodes (Electrum RVN's SPV proofs catch invalid headers and missing outputs), passive network observers (signed transactions reveal addresses but not seed material), wallet-file theft without the password (the file is encrypted), and a host computer compromise when a hardware wallet is attached (keys remain on the device).

The threats the wallet cannot defend against

A keylogger on your machine when you type the password. A seed phrase you typed into a phishing site. A backup stored in a synced cloud folder. A "support" agent who asked for your seed in DMs. A malicious display that shows a different destination address than the one being signed without a hardware confirmation. These are not wallet bugs — they are social and operational failures, and the way to mitigate them is process, not software.

  • Never type the seed phrase into anything other than the wallet during recovery.
  • Never share the seed with anyone — there is no legitimate support request that asks for it.
  • Verify the destination address on a hardware-wallet screen for non-trivial sends.
  • Keep the wallet password separate from any password you use online.
  • Treat browser ads for 'wallet downloads' as hostile by default.
FAQ

Frequently asked

§ continue

Continue with Electrum RVN

ready

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.

Windows macOS Linux
Download wallet