The problem XELIS Wallet solves
Bitcoin and Ethereum are radically transparent ledgers. Every balance, every transfer, every contract interaction is public forever — and increasingly, professional chain-analysis firms make their living mapping those flows into real-world identities. The result is that, in practice, holding crypto on a transparent chain means publishing your salary, your savings, your business relationships, and your spending habits to anyone who cares to look. That's a privacy failure of a kind that no traditional financial system would ever tolerate.
"Privacy" wallets on transparent chains are mostly UI illusions. They hide information inside the app, but the underlying ledger still publishes everything. XELIS Wallet takes a different approach: it's the reference client for a blockchain that was designed from day one to encrypt balances and amounts at the protocol level. The privacy is in the cryptography, not the user interface.
What an observer actually sees on the XELIS chain
On Bitcoin, anyone with a block explorer can see exactly how much you have, who you paid, and how much you paid them. On Ethereum, they can also see every contract you interacted with and every token in your wallet. On the XELIS chain, the same observer sees:
- That a transaction happened between two addresses.
- A cryptographic proof that the amounts are valid and the math balances.
- Nothing about the amounts themselves.
- Nothing about how much either address holds.
- Nothing about your spending pattern, salary, or wealth.
The chain is still fully auditable — anyone can verify that no XEL has been created out of thin air, that every transaction balances, that the consensus rules hold. They just can't read the values. That's the property homomorphic encryption gives you: verifiability without visibility.
How homomorphic encryption works (in plain English)
Traditional encryption is binary — you have the key, you read the data; you don't, you don't. Homomorphic encryption is different: you can perform arithmetic on the encrypted values without decrypting them, and the result is the encrypted answer to that arithmetic. If Enc(a) and Enc(b) are encrypted balances, the network can compute Enc(a) + Enc(b) and get Enc(a + b) — without ever knowing what a or b are.
XELIS uses this property to let the network verify that a transaction's inputs cover its outputs purely by manipulating encrypted balance values. The math holds; the values stay private. Zero-knowledge range proofs handle the remaining "is this amount within the legitimate range" check without revealing the amount.
You don't have to understand the cryptography to use XELIS Wallet — the wallet handles all of it transparently. But the property is worth understanding because it's what differentiates XELIS from every "privacy mode" toggle in a transparent-chain wallet: the privacy is provably mathematical, not policy.
Where ledger-level privacy ends
Privacy at the chain level hides transaction amounts and balances. It does not, by itself, hide your IP address, your device fingerprint, or your physical location. If you broadcast a transaction from your home internet connection, a sufficiently motivated observer with access to the right ISP logs could correlate the transaction to your IP at the network layer.
For maximum anonymity, combine XELIS Wallet with a VPN or — better — Tor. The wallet supports SOCKS5 proxying for RPC, so you can route all node traffic through Tor with a single config change. Layering network-level privacy on top of chain-level privacy gets you to a place where neither your activity nor your identity is exposed by any single observer.
Ledger privacy also doesn't protect you from the people you transact with. If you send XEL to a counterparty who later turns malicious or gets compromised, they know the address you sent from. Use stealth addresses, use fresh receive addresses, and treat any address that becomes public as a one-time pad — these are the same OPSEC habits that apply to any privacy-focused crypto.
How XELIS compares to other privacy approaches
Monero (ring signatures + RingCT + stealth addresses)
Monero's privacy model mixes your real input with sixteen decoys and uses RingCT to hide amounts. It's been around since 2014, has been audited extensively, and is the battle-tested choice. The key architectural difference: Monero's privacy is per-transaction, while XELIS encrypts the underlying balance state itself.
Zcash (zk-SNARKs, opt-in shielded pools)
Zcash pioneered zk-SNARK shielded transactions, but historically most Zcash transactions have been transparent because shielded usage is opt-in. The anonymity set of "users who chose to shield" is smaller than "everyone on the chain", which weakens the privacy guarantee in practice.
Mixers and tumblers (CoinJoin, Wasabi, Samourai)
On transparent chains, mixers attempt to break the link between your old and new addresses by pooling transactions. They work to varying degrees, but they're an opt-in patch on a fundamentally transparent ledger — and increasingly, they trigger compliance flags at exchanges.
XELIS (homomorphic encryption + ZK proofs, by default)
Confidential by default, with the anonymity set being the entire chain — every user gets the same privacy guarantee whether they care about privacy or not. No opt-in pools to weaken the set, no "tainted" private transactions for chain-analysis firms to flag.
Read more in our beginner explainer at Privacy Wallets 101, or compare XELIS to Monero head-to-head on the vs Monero page.
The threat model XELIS Wallet was designed against
XELIS Wallet protects against a specific set of realistic threats. Knowing the threat model up front means you can decide whether the wallet fits your situation:
- Chain-analysis firms. Encrypted balances and amounts mean there's nothing for them to graph. Your wallet activity does not show up in their dashboards.
- Compromised RPC nodes. The wallet treats every node as untrusted by design. Block headers and balance proofs are verified locally; a malicious node can refuse to answer but can't lie.
- Local malware reading your screen or keylogging. Partially mitigated — the wallet uses a shuffled on-screen keypad for password entry, and your encrypted seed is never written to disk in plaintext. A determined attacker with persistent local access still wins; this is true for every wallet ever made.
- Server compromise of the project's infrastructure. There is no server infrastructure to compromise. The wallet is a desktop binary that talks to the XELIS network. There's no user database, no recovery service, no centralised anything.
- Subpoena or legal order against the project. The project has no data on you to hand over. No account, no email, no IP log.
What XELIS Wallet does not protect against
- You losing your seed phrase. If you lose the 25 words and forget the password, the funds are gone. Period. This is true of every self-custody wallet.
- You typing the seed into a phishing site. No software wallet can save you from voluntarily handing over the keys. Treat any prompt to enter your seed outside the wallet as a scam.
- Hardware-level attacks. Until hardware-wallet integration ships, the keys live in software on your laptop. That's a stronger threat surface than a Ledger or Trezor signing transactions in a separate device.
- Coercion. Cryptography doesn't help against someone with a wrench.
Open, auditable, no claims you can't verify
The cryptography described here is implemented in the open-source XELIS codebase. You can read the code on GitHub, audit the crypto, build the wallet from source, or fork the whole project. Privacy claims that can't be verified independently are just marketing — XELIS publishes the math, the code, and the reasoning, and welcomes scrutiny.
If you want hands-on assurance, the full source is on GitHub and the download page includes instructions for building from source. If you want to understand the threat model and OPSEC implications before you put real value into the wallet, the security guide is the right next read.