Don't have recommendations for a clipboard. I don't use my phone for any meaningful transfers. And when I do, I don't work with the clipboard, only the built-in QR code scanner of my lightning wallet, or that of a companion app I need for local payments.
Obviously, the best option will always be to verify, character by character, the addresses we're copying and pasting before paying.
Focus on the checksum at the end, typically the last 6 characters, and the first 1-4.
Legacy (1...) and P2SH (3...) addresses use Base58Check leading to a variable checksum at the end, about 5-6 characters long.
SegWit (bc1q...) and taproot (bc1p...) addresses use Bech32/Bech32m with a 6 character long checksum at the end.
To produce a collision, in other words another address having the same checksum, you need well over a billion attempts, so it's very hard to get that done on the fly.
For normal use, I'm happy to check those alone. If I feel paranoid, I will check other additional random sets of characters in other positions of the address before signing.
Don't have recommendations for a clipboard. I don't use my phone for any meaningful transfers. And when I do, I don't work with the clipboard, only the built-in QR code scanner of my lightning wallet, or that of a companion app I need for local payments.
Focus on the checksum at the end, typically the last 6 characters, and the first 1-4.
Legacy (
1...) and P2SH (3...) addresses use Base58Check leading to a variable checksum at the end, about 5-6 characters long.SegWit (
bc1q...) and taproot (bc1p...) addresses use Bech32/Bech32m with a 6 character long checksum at the end.To produce a collision, in other words another address having the same checksum, you need well over a billion attempts, so it's very hard to get that done on the fly.
For normal use, I'm happy to check those alone. If I feel paranoid, I will check other additional random sets of characters in other positions of the address before signing.