Reading a wallet address out loud over a phone call
2026-09-25
This post contains affiliate links. As an Amazon Associate, ZAGO.TO earns from qualifying purchases.
Someone is on the phone. They need your wallet address. You are looking at 42 characters of base-16 nonsense and they have a pen.
People really do this. It happens between family members, between a customer and a support line, between two colleagues where one of them is driving. It is not a stupid thing to attempt, because sometimes the phone call is the only channel you both have open.
It is, however, a terrible thing to attempt, and it is worth knowing exactly why before you try it.
What goes wrong, character by character
The alphabet is the problem. Wallet addresses are built out of exactly the characters that sound alike or look alike.
Zero and the letter O are indistinguishable when spoken. So are lowercase l, uppercase I, and the digit 1, which is why some address formats deliberately exclude them. Reading "B" and "D" and "E" and "P" and "T" and "V" down a phone line is the reason radio operators invented a phonetic alphabet.
Then there is case. Ethereum addresses use mixed case as a checksum, so "A" and "a" are not interchangeable, and now every single character needs "capital" or "small" attached to it. That doubles the length of what you are saying.
Forty-two characters, each needing disambiguation, read to someone writing by hand. Realistically that is two to four minutes and at least one restart. Most people give up halfway and say "I'll just text it to you."
Why "I'll just text it" is where the real risk starts
The moment the call turns into a message, the address stops being ephemeral and becomes a record.
It sits in that conversation. It syncs to the desktop app on the other person's work laptop. It goes into whatever backup their phone makes. It is searchable, by them and by anyone who ever gets into that account. For a personal address that is a privacy leak; for a business receiving address it is a small map of who pays you.
None of that is catastrophic on its own. Addresses are public information in the sense that they appear on-chain. But "public in principle" and "sitting in forty chat threads" are different situations, and the second one is the one people sleepwalk into.
There is also the transcription risk that does not go away just because you switched to text. If they retype rather than copy, you are back to the character problem, except now nobody is checking.
What the phone call is actually for
Step back and ask why the address is being read aloud at all. Almost always it is because the two of you have a voice channel open and no shared app, and one of you wants the other to have something now rather than after a round of setup.
That is a real situation and it deserves a real answer. The answer is not to read faster or to spell more carefully. It is to stop using the voice channel to carry the address, and use it to carry a pointer to the address instead.
A pointer can be short. The address cannot. That is the whole trick, and it is why the length of what you say is the thing worth optimising.
Links are the obvious pointer and they fail here for the same reason the address does. A URL has slashes, case-sensitive characters and a random tail. Reading one aloud is barely easier than reading the address. A QR code is not sayable at all, and neither is a file.
Digits are the only thing that survives a voice channel cleanly.
Say four digits instead of forty-two characters
This is our own service, so read this with that in mind.
ZAGO.TO takes text and gives you four digits. `3342`. The other person opens the site, types those four digits, and the address is on their screen where they can copy it rather than write it. A minute after it is opened the text is deleted from the server. If nobody opens it, it goes after a minute anyway.
For a phone call, this is the part that matters: four digits is three seconds of speech and has no ambiguous characters. There is no capital-or-small, no zero-or-O. You say it, they repeat it back, and you are done. The address itself never travels through the call or through a message thread, so it does not end up living in either one.
Two limits matter enough to repeat even though we cover them elsewhere. This does not protect against clipboard malware, because the receiving side still pastes and an infected machine can still swap what it pastes. And a seed phrase never travels between devices by any method, ours included; anyone asking you to move one is running the scam.
The rest of the caveats, including what our server can see while the text is there, are in our longer piece on giving someone an address without retyping it.
So the claim is narrow: it removes the transcription and it does not leave the address behind. That is the whole of it.
If you must read it aloud anyway
Sometimes there is no second channel. If you genuinely have to do this, at least do it the way radio operators do.
Use a phonetic alphabet, the same word for the same letter every time. Say "capital" or "small" before every letter in a mixed-case address. Group the characters in blocks of four and pause between blocks, so a mistake is contained to one block instead of shifting everything after it. Have the other person read the whole thing back before either of you touches a wallet. Then send a small test amount, always.
And when the money actually matters, use a QR code shown on one screen and scanned by the other, if the two of you are ever in the same room. That remains the most reliable transfer there is, because there is no human in the loop to mishear anything.