Avoid Choosing a Recipient From Misleading Transaction History
Transaction history records activity; it is not a verified address book. Address poisoning exploits that distinction by placing a misleading lookalike address where a user might later copy a destination.
Recognize the planted reference
MetaMask documents scams that use small transactions and addresses resembling previously used recipients. A familiar prefix and suffix can make a history row look plausible when the middle differs. The practical issue is the source of your next copied address. Seeing a tiny incoming entry does not mean that its sender is your intended recipient, nor does a familiar token symbol turn the entry into an authenticated contact.
Choose a recipient through a separate channel
For a future payment, obtain the destination from the intended recipient through a channel you independently trust. Compare the entire address rather than only the shortened display. Also confirm the intended network and asset because matching address characters do not establish those details. If an address book entry exists, review how it was originally created; an old entry copied from unverified history does not become reliable simply by being saved.
Use a concrete comparison exercise
Without sending anything, compare a known recipient record with a suspicious history entry in a text view that shows every character. Mark the first difference and note where each value came from. This exercise tests your reference selection, not wallet execution. Do not visit websites embedded in token names or send funds back to an unknown sender to “verify” them. A read-only inspection is enough to identify why a source should not be reused.
Respond to uncertainty proportionately
If you have not submitted a transfer, keep it stopped until the intended recipient is clear. If a transaction was already included, preserve the hash and compare the actual destination with the independently confirmed one; do not assume a history label describes the recipient correctly. RunixCoin’s public Activity panel is not integrated transaction history, so use the appropriate chain explorer for evidence. No warning system or visual comparison guarantees detection of every misleading address.
References and verification
Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.