A crypto address, also known as a public key, is a sequence of letters and numbers where cryptocurrencies can be sent to and from. Each address has a corresponding private key that controls spending the funds stored at that address.
​
For a guide on how to find your address in Exodus, please visit: How do I receive Bitcoin and crypto in Exodus?

A crypto address is a unique string of characters, usually a combination of letters and numbers, used to identify a specific wallet or destination on a blockchain. This is similar to how a bank account number identifies a specific bank account.

In this article, you can learn about how crypto addresses are generated, what makes a valid address, and why it's crucial to enter the correct address when sending crypto.

To learn how to find your address, visit: How do I receive Bitcoin and crypto in Exodus?

Your wallet generates private keys through cryptographic algorithms.

The process only works in one direction. So, while it is possible to generate an address from a private key, it is not possible to generate a private key from an address. This one-way mechanism ensures that your private keys are kept secret.

Anyone with access to your private keys can spend your funds, so it's crucial not to share them with anyone.

QR codes, similar to barcodes, store information. When you scan a QR code with your mobile device, it displays the stored information.

In crypto, addresses can be converted to QR codes, making it easier to send funds. Instead of manually entering or copying the address, the sender can scan the QR code.

Always verify the address after scanning, as crypto transactions are permanent.

It's good to be aware that scammers can pre-fill amounts in QR codes, so double-check before sending.

In Exodus, your address is shown both as text and as a QR code.

Exodus Mobile and Exodus Desktop both support scanning QR codes when sending. To learn more, visit: How do I send Bitcoin and other crypto out of Exodus?

Some assets support multiple addresses to enhance privacy. Exodus Mobile supports multiple addresses for Bitcoin (BTC), and Exodus Desktop supports multiple addresses for Bitcoin and other UTXO-based assets.

Using a new address for each transaction helps protect your privacy. If you reuse the same address, anyone you share it with can view the balance and transaction history tied to that address. However, if you use different addresses each time you receive crypto, they would need access to your xpub or zpub to see your full transaction history and balance.

For UTXO-based assets, your xpub or zpub lets you view all addresses generated from your private key. Be cautious when sharing this, as it reveals your complete wallet history. To learn more, visit: What does the xpub/zpub do?

In Mobile, only Bitcoin (BTC) supports multiple addresses.

In Exodus Desktop, you can enable multiple addresses for the following UTXO-based assets:

For a guide on how to enable multiple addresses, visit:

Answers to common questions about crypto addresses.

In general, it's safe to share your address with anyone sending you crypto.

Though keep in mind that anyone with your address can search for it on a block explorer. They will be able to view the transaction history and balance of that address.

If you enter an incorrect address, your funds will be sent to the wrong address and lost. Crypto transactions cannot be reversed, so recovering crypto sent to a wrong address is most likely impossible.

Only the owner of a private key can access the funds at an address. If you send crypto to the wrong address, you'd need to contact the owner to recover it, but block explorers don’t provide identifying info.

If you enter an address incorrectly, the crypto may be sent to an unowned address, making it impossible to recover the funds.

For tips to ensure you enter addresses correctly, see: How do I avoid mistakes when entering an address?

Case-sensitive addresses require the correct use of upper and lower case letters to distinguish them. Whether an address is case-sensitive depends on the network. For example, Solana addresses are case-sensitive, making correct capitalization crucial

On networks like Ethereum, capitalization is used for checksums to verify address accuracy.

To avoid errors, it's best to copy and paste addresses, ensuring an exact match.
​

Here are some good practices to follow to avoid sending your crypto to the wrong address:

You may receive a warning or error if the address you enter is invalid. If this happens, check the following:

Ethereum addresses use the "0x" prefix, indicating a hexadecimal format. This format is also used by EVM-compatible blockchains like Arbitrum, Base, BNB Smart Chain, Optimism, and Polygon. However, VeChain uses 0x addresses but is not EVM-compatible.

In Exodus, your Ethereum and EVM-compatible addresses are the same because they share the same private key.

Bitcoin originally had one address format, now called Legacy. Over time, Nested SegWit, Native SegWit, and Taproot formats were introduced, offering improved functionality and lower fees.

All Bitcoin address formats are compatible with each other, meaning Bitcoin can be sent to and from any format. However, not all wallets and exchanges support every format, so compatibility may vary when sending or receiving Bitcoin.

To learn more about Bitcoin in Exodus, the different address formats, and how to enable other Bitcoin addresses in Exodus, visit: Bitcoin FAQs - Learn more about BTC.

Exodus does not support manually creating new addresses.

However, you can create up to 3 new Exodus portfolios that will generate a different address for each.

Your new portfolios will remain tied to the same 12-word secret key. For more on multiple portfolios, visit: How do I manage multiple portfolios in the same wallet?

Exodus Mobile supports multiple addresses for Bitcoin, and Exodus Desktop supports it for Bitcoin and some UXTO-based assets. Once enabled, your wallet will generate a new address every time you receive a transaction. To learn more, visit: How do I enable multiple addresses?

If a TON address in your transaction history looks different, it may be the same address but shown in a different format.

On the TON network, the same address can be shown in the following formats:

It's possible to show the same TON address in any of these formats, and addresses may appear differently across platforms depending on which is used.

In Exodus, you can use any of these TON address formats when sending and receiving. However, Exodus displays your own TON address and the addresses in your transaction history using the non-bounceable format, which starts with UQ.

If you send or receive using a different format, your Exodus transaction history will still display the address in the non-bounceable format. It may look different, but it is the same address.

An address is only valid on a blockchain if it follows the network's formatting standards. Different blockchains have unique formats, and some can be identified just by looking at the address.

EVM-compatible networks use the same address format, which can lead to accidentally sending unsupported crypto to a wallet on the wrong network.

Always verify that the receiving wallet supports both the network and asset before sending crypto.

Crypto addresses are complex, with various formats. Understanding how addresses are structured can help prevent errors when sending funds.

In this section, we will go over the basic elements of an address, including length, characters, prefixes, checksums, and capitalization.

The length of addresses can vary, even on the same network. For example, Bitcoin addresses are 26-35 characters long.

Some networks have a set length. For example, Ethereum addresses are always 42 characters long.

Crypto addresses are usually quite long to ensure that networks can generate an almost endless amount.

Crypto addresses typically use a mix of letters and numbers, but the characters vary by network.

Ethereum addresses are written in hexadecimal, using only 0-9 and A-F.

Some networks, like Bitcoin, follow Base58 and omit certain characters (e.g., uppercase O, zero, uppercase I, lowercase l) to avoid confusion due to their similar appearance

Some networks use prefixes for crypto addresses, which are characters placed at the beginning of an address to indicate specific formats.

For example, Bitcoin has multiple address formats identified by prefixes: Legacy addresses start with "1," and Nested SegWit with "bc1q.

Ethereum addresses always begin with "0x," indicating the use of hexadecimal characters. All EVM-compatible networks also use this prefix.

A checksum is a method used to verify that information hasn't been altered. It’s a value generated from data, and if the data changes, the checksum will too.

For example, Bitcoin addresses have built-in checksums. The address is processed through a formula to generate a value attached to the end. If the checksum doesn’t match, the address is invalid.

Checksums help ensure crypto addresses are entered correctly, preventing errors when sending funds.

Ethereum and EVM-compatible networks use checksums encoded in addresses through the use of upper and lowercase letters.

Originally, Ethereum didn't have checksums. Instead, they were added later. As such, they aren't required, meaning an Ethereum address can appear in two ways:

Some wallets can verify checksummed addresses for accuracy, but not all do. Therefore, using a checksummed address doesn’t guarantee that funds will be sent to the correct address.

To avoid errors when sending to an Ethereum address, always enter the address exactly as shown, whether it’s checksummed or not.

Ethereum and EVM-compatible addresses use capitalization for checksums, meaning the address is valid regardless of capitalization.

However, networks like Solana are case-sensitive. Entering incorrect capitalization on these networks can send funds to the wrong address.

To stay safe, always ensure the capitalization is correct. In Exodus, when sending to a Solana address, a notice will appear on the confirmation screen reminding you that Solana addresses are case-sensitive. Double-check the address and capitalization before confirming the transaction: