How to send and receive XEL with XELIS Wallet

In XELIS Wallet, click the Receive tab. You'll see your wallet address (a long string starting with xel) and a QR code.

You can safely share this address with anyone who wants to send you XEL. Because of the on-chain privacy features, sharing your address does not expose your balance, your transaction history, or your seed phrase.

Give the sender your address (copy/paste or share the QR code). When they send, you'll see the incoming transaction appear in your transaction list — usually within a minute.

Your balance updates after the transaction reaches enough confirmations. For most amounts, one confirmation is enough; for larger amounts, wait for 6 or more.

Click the Send tab. Paste the recipient's address and the amount of XEL to send.

Always double-check the address — clipboard malware on compromised machines silently swaps addresses on copy. Check the first 6 and last 6 characters at minimum.

XELIS Wallet calculates a network fee for you. Fees on XELIS are small (fractions of a cent in most cases) and are paid in XEL.

You can usually accept the default fee. Higher fees do not buy faster confirmation on XELIS the way they do on Bitcoin — XELIS targets fast, fixed-fee transactions.

Enter your password to authorise the transaction. The wallet signs it locally and broadcasts it to the network. You'll see the transaction in your history with a "Pending" badge until it's confirmed.

Every transaction has a unique transaction ID. You can give this to the recipient as proof of payment, or paste it into a XELIS block explorer to see its status independently.

Once it has at least one confirmation, the receiver can spend the funds.

XELIS addresses are bech32-encoded, prefixed with xel on mainnet and xet on testnet. The prefix is your first sanity check — never send mainnet XEL to an address that starts with xet, and vice versa. The remainder encodes the recipient's public spend key plus a checksum, which is why even a one-character typo causes the wallet to reject the address outright rather than sending to nowhere.

Because XELIS balances are encrypted on-chain, the address itself does not leak anything about how much the recipient holds or how active they are. You can safely publish a static donation address; observers can see that payments arrived but not the amounts, and they cannot tie those payments to anything else you've ever done.

For privacy-sensitive scenarios — payroll, recurring vendor payments, donations from sources you'd rather not link — generate a fresh receive address per relationship from the Receive tab. The wallet derives an unlimited number of them from the same seed at no cost.

XELIS uses a BlockDAG (a directed-acyclic graph of blocks) rather than a single linear chain, so confirmation semantics differ slightly from Bitcoin. A transaction is included the moment a miner adds it to a block; that block then accumulates "weight" as later blocks reference it. Once enough later blocks have built on top, the transaction is irreversible for practical purposes.

Block targets on XELIS are aggressive — roughly fifteen seconds — so what feels like "one confirmation" arrives much faster than on most chains. For everyday amounts (coffee, small transfers between your own wallets, online purchases), a single confirmation is fine. For amounts you'd be unhappy to lose, give it five to ten confirmations — about two minutes — before considering it settled.

Exchanges and merchants set their own confirmation thresholds, sometimes much higher than necessary. That's their risk policy, not a XELIS network requirement.

Network fees on XELIS are paid in XEL and deducted from the sending wallet, not subtracted from the amount you sent. If you send 10 XEL with a fee of 0.0001 XEL, the recipient gets 10 XEL and your balance drops by 10.0001 XEL.

When you click "Max" or try to send your entire balance, the wallet automatically reserves enough XEL to pay the fee — but if you've calculated the amount manually, leave a small buffer. Trying to send your last 0.00005 XEL will fail because there's nothing left to pay the fee with.

"Dust" — amounts so small that the fee approaches the value transferred — is rarely worth moving. Consolidate small balances into a single sweep transaction periodically rather than fighting fee-to-value ratios on every transfer.

If you want maximum cold-storage discipline, you can receive XEL on a wallet whose private key never touches the internet. Generate the wallet on an offline machine, copy out only the public address, and use that address for inbound payments. The receiving side requires no signature — anyone can pay into any valid XELIS address — so cold receiving works perfectly out of the box.

Spending from the same address later requires the private key, which is the point: funds sit at an address whose key has never been exposed to any networked machine. When you finally need to spend, restore the seed into a one-time wallet on an air-gapped device, sign the transaction there, and broadcast the signed payload from a connected machine. Treat the air-gapped device as untrusted afterwards.

This is overkill for everyday use but the right pattern for long-term savings, treasury balances, or holdings you do not plan to touch for years.