If crypto transfers feel stressful, it is usually because four different destination formats get mixed together at the worst possible moment.
A wallet address is the base destination for a crypto transfer. ENS is a human-readable name that points to an address. A memo or destination tag is an extra identifier some services, especially exchanges, use to route funds to the right account. If you are sending to a private self-custody wallet, the address is usually enough.
TL;DR
Wallet address = the main destination. It is the thing you actually send crypto to.
ENS = a readable name, like
name.eth, that resolves to an address. It does not replace the address at the protocol level. It points to it.Memo or destination tag = an extra identifier used mostly when a platform receives funds into a shared address and needs to know which internal user should get credit.
Sending to self-custody usually needs only the address. Sending to some exchanges may need both the address and the memo or tag.
walllet fits this topic because it is a non-custodial wallet built around passkeys, on-device key control, and clearer transaction UX, which is exactly what helps people make fewer sending mistakes.
Most transfer mistakes come from a simple question asked too late: What exactly am I supposed to enter here? A long address? A .eth name? A memo? A tag? And if you get it wrong, the blockchain usually does not offer a polite undo button. walllet in its disclaimer policy says this plainly in its own legal docs: blockchain transactions are final and irreversible.
Here is the simple version before we go deeper:
Term | What it is | When you use it | Most common example | Main risk if you get it wrong |
Wallet address | The core destination for a transfer | Almost every crypto send or receive | A long public address string | Funds go to the wrong place |
ENS | A readable name that points to an address | When the recipient gives you a supported |
| You trust the name without checking what it resolves to |
Memo | An extra routing identifier | Often when sending to an exchange or pooled account | XLM, ATOM, HBAR deposits on some platforms | Funds arrive onchain but do not get credited to your account |
Destination tag | Same basic idea as a memo, but usually labeled differently | Most famously with XRP deposits | XRP tag | Same problem: funds may not be credited properly |
That framing matches how ENS documentation describes forward and reverse resolution explains shared-address memo routing, and how destination tags for multi-purpose addresses.
What is a wallet address in crypto?
A wallet address is the public destination other people use to send you crypto. It is shareable. It is not secret. In the simplest terms, it is the string of letters and numbers crypto can be sent to and from.
That sounds simple, but two details trip people up.
First, a wallet address is not your private key. Your address is public. Your private key is the thing that gives control over funds. In walllet.com’s model, those credentials stay under your control, and the company says it does not hold or store your private keys on your behalf.
Second, one wallet does not always mean one address in every situation. Depending on the asset and network, a user can have multiple addresses associated with a crypto asset, and some wallets or platforms can display historical addresses too.
Are wallet addresses unique?
They are unique enough to function as the destination for a transaction on their network, but the practical answer is this: treat every send as network-specific. The address is only “right” if it matches the chain, asset, and instructions the receiver expects. That is also why walllet’s ETH/ERC-20 guide puts so much emphasis on verifying network and address together, not separately.
Why do wallet addresses look different across chains?
Because blockchains are not one system pretending to be many. They are many systems with different address formats, rules, and transaction models. What matters for users is recognizing that a valid-looking address on one network does not automatically make it the right destination for the transfer you are making. That is a subtle difference, but it is where a lot of “my funds disappeared” stories begin.
Does one wallet have one address or many?
Usually, many. Or more precisely, it can. You may have different addresses for different networks or assets, and some platforms maintain multiple addresses for the same asset over time. So when someone says, “Send it to my wallet,” what they really mean is, “Send it to the correct address for the correct asset on the correct network.”
For beginners, this is where a calmer product experience matters. walllet’s whole pitch is that self-custody should feel more human, not more cryptic. That matters long before you ever touch DeFi. It matters the first time someone sends you an address and expects you to know what to do with it.
What is ENS and how is it different from a wallet address?
ENS, short for Ethereum Name Service, maps a human-readable name like alice.eth to machine-readable identifiers such as Ethereum addresses and other records. In plain English, it lets people use a name instead of pasting a long address every time.
That makes it tempting to think ENS replaces the address. It does not. ENS is a naming layer. The address is still the actual destination underneath.
Does ENS replace your address or just point to it?
It points to it. ENS support documentation describes forward resolution as the process that determines where your name points, based on the address record set on the ENS name.
So if somebody gives you a .eth name, what you are really doing is asking a naming system to resolve that name into an address. That is incredibly useful. It is also why it pays to pause for one second and confirm what the name resolves to before sending a meaningful amount.
What is forward resolution?
Forward resolution is name to address. You start with name.eth, and the resolver returns the address it points to. That is the part most users interact with directly when they type an ENS name into a wallet.
What is a primary name?
A primary name is the reverse-facing side of ENS. ENS docs describe it as a bi-directional relationship between an EVM address and a human-readable ENS name:
Name to address, which is forward resolution
Address to name, which is reverse resolution
Why does that matter? Because apps need to know whether it is safe to display a human-readable name for an address. ENS docs explicitly say clients should verify the reverse result by following it with a forward lookup, and if the address does not match, display the address instead of the reversed name.
That is a beautifully boring little safety detail, and boring is good when money is moving.
For a wallet like walllet, which already frames itself around human-readable approvals and clearer confirmation screens, ENS fits the product philosophy. A readable name is useful. A readable confirmation is even better.
What is a memo or destination tag in crypto?
A memo or destination tag is an extra identifier added on top of the wallet address. It exists because some services, especially exchanges, receive funds into a shared address and then need a second piece of information to know which internal customer account should get credit.
This is the part that confuses almost everyone once.
You see a receiving screen. It shows a wallet address. Then below it, a memo or destination tag. Your brain naturally assumes the address should be enough. But in these systems, the address gets the funds to the platform, while the memo or tag tells the platform which user those funds belong to.
Is memo the same as destination tag?
Functionally, yes in many user-facing situations. They do the same job: extra routing information. The label changes by network and platform. Some treats them together because they serve the same operational purpose, some use the label “destination tag,” while many other assets and platforms use “memo.”
Which coins commonly use memo or tag?
This depends on the platform, some lists XRP under destination tag and several other assets such as XLM, ATOM, HBAR, STX, and others under memo. XRP Ledger docs also describe destination tags as a way to indicate the beneficiary for payments sent to multi-purpose addresses.
Why exchanges use shared deposit addresses
Because it is operationally efficient. The extra field lets exchanges route deposits from one shared address to the correct customer account. Stellar’s documentation describes the same pooled-account idea from the infrastructure side: one account can serve many users, with additional routing logic layered on top.
There is a useful mental model here:
Wallet address = the building
Memo or destination tag = the apartment number
Without the apartment number, the package may arrive at the building, but nobody knows which door it belongs to.
When do you need only a wallet address, and when do you need address plus memo/tag?
This is the question most people actually have.
Self-custody wallet to self-custody wallet
Usually, just the address. Tags and memos generally are not needed when sending to a private or self-custody wallet because the address is unique to the recipient. That is the normal case for transfers into a wallet like walllet.
Sending to an exchange deposit address
Often, address plus memo or destination tag.
If the exchange shows both, both matter. Missing or incorrect tag/memo information can delay a transaction or cause loss of funds, and that funds may not be credited to the correct account if either the address or the memo/tag is wrong.
Sending to an ENS name
Use the ENS name only if your wallet supports it and you are comfortable verifying what it resolves to. ENS is designed exactly for that kind of human-readable sending flow, but the safest pattern is still the same one you would use anywhere else: verify the destination before the final tap.
A practical 4-step check before you send
If you are not sure what the destination field needs, use this order:
Identify the recipient type. Is it a private wallet, your own wallet, or an exchange deposit page?
Look for extra instructions. If the platform shows “memo,” “tag,” or “note,” treat that as mandatory unless the platform says otherwise.
Check the network. A correct address on the wrong network is still a bad transfer.
Send a small test amount first if it is a new destination or a meaningful sum.
This is where walllet’s positioning actually matters. A wallet makes crypto safer by reducing cognitive clutter at the exact moment users need to make a correct decision. That is why walllet’s emphasis on simpler flows, passkey-based access, and human-readable transaction approvals is more than branding. It is good transfer hygiene dressed as good product design.
Common mistakes that cause lost funds
Wrong network vs wrong address vs missing memo
These are not the same mistake.
A wrong address means the funds were sent to the wrong destination.
A wrong network means the destination may technically exist, but the funds were sent on a chain the recipient is not watching or cannot credit properly.
A missing memo or destination tag means the funds may have reached the platform’s shared address onchain, but the platform may not know which internal user account to credit. walllet’s own disclaimer is blunt about the broader reality here: blockchain transactions are final and irreversible.
What happens if you forget the tag?
Usually one of two things happens.
Best case, the receiving service has a recovery process and support can trace the payment using the transaction hash.
Worse case, the funds are not credited and recovery is slow, manual, costly, or not possible. Incorrectly entered or missing memo/tag details can lead to delay or loss, and that support may ask for the transaction hash if recovery is possible. XRP Ledger docs also note that systems using destination tags still need support processes for incorrectly tagged payments.
Why test transactions still matter
Because they shrink uncertainty before you move real money.
This advice sounds old-school because it is old-school. It keeps surviving because it works. We recommends a small test amount when a tag or memo is involved, and walllet’s own transfer-safety content repeats the same calm habit for ETH and ERC-20 sends.
Do not copy from history blindly
One more trap is worth naming here: address poisoning. walllet already has a dedicated piece on this, and the core lesson is simple. Transaction history can be manipulated to make fake lookalike addresses seem familiar. So even if you know the difference between address and memo, copying the wrong address from history can still wreck the transfer.
Related: Address Poisoning Scams: The Copy-Paste Trap That Drains Crypto Wallets (And How to Avoid It)
How walllet.com makes crypto transfers simpler
walllet is relevant to this topic because it removes a lot of unnecessary friction around them.
According to walllet’s terms, it is a non-custodial wallet. Users remain in control of their assets and credentials, while passkey-based authentication and on-device credential handling replace the old seed-phrase-heavy setup most people associate with self-custody.
That matters here for three reasons.
Human-readable confirmations matter
walllet’s own product content says it replaces blind signing with human-readable transaction approvals, showing a plain-language summary of what a transaction will do before you approve it. That is exactly the kind of UX improvement that helps people catch problems before they become onchain regrets.
Clearer send screens reduce mistakes
When users understand what field they are filling, and why, they make better decisions. A good wallet cannot magically know whether an exchange wants a memo unless the destination instructions are clear, but it can reduce the odds that a user approves something they barely understood. That is a very different kind of safety from “security theater.” It is practical clarity.
How passkey-based self-custody fits the story
This topic is about transfer clarity, but transfer clarity and account safety belong together. walllet.com says passkeys and biometrics are used to control access, and that private keys and passkeys are not stored on its servers. So the product pitch is not “crypto made less serious.” It is “crypto made less fragile.”
If you are new to crypto, that is a very useful distinction.
Related: Best Crypto Wallet for Beginners: What to Look for Before You Download Anything
Final checklist before you send crypto
Before you tap send, ask yourself these six questions:
Am I sending to a wallet address, an ENS name, or an exchange deposit page?
If it is an ENS name, did I verify what it resolves to?
If it is an exchange deposit, did the platform also give me a memo, tag, or note?
Am I on the correct network?
Have I checked the destination carefully enough not to fall for address poisoning?
Should I send a small test amount first?
The deepest truth here is behavioral. Crypto transfers feel hard when too many invisible rules pile up at once. Wallet address. ENS. Memo. Destination tag. Network. Contract. History. Approval.
A better wallet experience does not remove all of that complexity from the ecosystem. But it can remove a lot of it from your moment of action. That is why walllet.com is a natural fit for this conversation. It keeps the self-custody part, drops the seed phrase burden, and leans into the kind of readable, human-first experience that helps real people move assets with less friction and more confidence.
If you want to make your next transfer feel less like decoding a launch panel and more like using modern money, start with a small test transfer in walllet and build the habit while the stakes are tiny. Try your next small test transfer in walllet. You keep self-custody, skip the seed phrase friction, and get a clearer view of what you are approving before you send.
