# "address poisoning" — X 热门讨论 (2026-09-25 17:51 UTC)

## @sheikhakash69 (Akash.eth🌊) · 09-25 16:28 · ♥152 ↻0 💬151 Good evening everyone.

Crypto payments still have a privacy problem: one address can become a permanent record of everything sent to it.

@Americanfort_io approaches that differently with Send‑to‑Name™.

You can send to a FortressName like @name of pasting a long wallet address. The wallet generates a fresh one‑time address for that payment while settlement still happens on the chain.

The FortressName stays public. It does not point outsiders to a fixed wallet, balance or payment history.

There is a benefit too. Paying a FortressName removes the copy‑paste step that makes address‑poisoning attacks possible.

One FortressName currently works across 13 integrated networks and the system is designed to work inside wallets than forcing users into another app.

Send‑to‑Name™ is live. SafeSend™ is still, in development.

If you want to test the path you can claim a free FortressName:

https://t.co/N7pdRpGpiS https://x.com/sheikhakash69/status/2103522083989066142

## @DucCryptoX (Duc Crypto) · 09-25 16:57 · ♥56 ↻1 💬73 A payment sits on a screen as a 42-character string. The first four and last four look right. The middle does not.

That is the copy-paste surface address poisoning uses. A readable name removes the step of matching characters by eye. Send-to-Name computes a fresh one-time address for that payment. Only sender and recipient can derive it. Only the recipient can spend it. Settlement still happens on the native chain.

A FortressName is not described as a public pointer to one fixed wallet, balance, or history. One name is listed across 13 integrated networks.

Mechanism pages: https://t.co/eXdxFsFfPL Account: @Americanfort_io https://x.com/DucCryptoX/status/2103529222824423780

## @siraj_dev122 (Daniel) · 09-25 16:43 · ♥37 ↻1 💬44 I’ve been looking into @Americanfort_io , and one thing stood out:

Crypto payments still rely too much on copying long wallet addresses.

That creates room for address poisoning, where a fake address can look similar enough to the real one that a user sends funds to the wrong place.

Send-to-Name™ takes a different approach.

Instead of copying an address, you send to a human-readable name.

The wallet then generates a fresh one-time address for that payment. The recipient’s FortressName doesn’t publicly expose one permanent wallet, balance, or payment history.

So the idea isn’t just making payments easier.

It removes part of the copy-paste attack surface while keeping settlement on the native blockchain.

And one FortressName currently works across 13 integrated networks.

You can claim a free FortressName here: https://t.co/AYv2qKWBZr https://x.com/siraj_dev122/status/2103525713760719210