What this choice changes
Both are native-network payment routes in PrivacyNodes, but the amount format, address, wallet requirements and public transaction data differ. Select the route your wallet can send exactly.
Compare the decision factors
| Factor | Monero (XMR / Monero) | Bitcoin (BTC / Bitcoin) |
|---|---|---|
| Network selection | Send native XMR on Monero mainnet. | Send native BTC on Bitcoin mainnet. |
| Quoted amount precision | PrivacyNodes calculates up to 12 decimal places, matching the piconero precision documented by Monero. | PrivacyNodes calculates up to 8 decimal places, matching satoshi precision. |
| Receiving address | Use the complete Monero address displayed for this route. | Use the complete, distinct Bitcoin address displayed for this route. |
| Public chain data | Monero documents ring signatures, stealth addresses and RingCT for sender, recipient and amount privacy. | Bitcoin transactions identify previous outputs by txid/vout and create amount-bearing outputs recorded on the blockchain. |
| Wallet check | Confirm the wallet supports native XMR, the full address and exact precision. | Confirm the wallet supports native BTC, the displayed address type and exact precision. |
| Network fee | Chosen by the wallet/network and separate from the quoted receiving amount; PrivacyNodes makes no fee guarantee. | Chosen by the wallet/network and separate from the quoted receiving amount; PrivacyNodes makes no fee guarantee. |
For both routes, PrivacyNodes uses the same Kraken public-rate workflow, one-hour expiry and address-only QR. The QR does not set the amount or network, and a local reference does not verify payment.
When each option earns its place
Choose only after the wallet displays the same asset, native network, full address and exact amount. Do not send one asset to the other route.