# "address poisoning" — X 热门讨论 (2026-10-09 03:41 UTC)

## @mdhafiz001987 (Md Hafiz) · 10-09 01:27 · ♥109 ↻8 💬105 Good morning.

Privacy is not a feature you bolt on after the payment. That was the Singapore message from AmericanFortress.

Not a separate chain you have to move to. Not a trade between staying private and staying accountable. A name replaces the address. The balance stays yours. The only person who can see where a payment came from is the person you paid.

That maps to the live product. Send-to-Name™ is how you address it. The wallet derives a fresh one-time address from keys only the sender and recipient hold. The chain sees a normal transfer. No pool. No new L1. Address poisoning needs a reused string. A one-time address does not give it one.

SafeSend™ is the planned sender-side shield. It is still in development. Do not treat the booth conversation as a shipped feature. First path is 0G, after it ships.

What the week actually produced, per the official note: names sold to people who will not have to triple-check characters, and SDK talks with wallets that do not want to rebuild privacy from scratch. No winner list. No price recap.

Free lifetime .free FortressName: https://t.co/q9PhSf1dKp

@Americanfort_io

YOUR MONEY. YOUR NAME. NOBODY ELSE'S BUSINESS. > 引用 @mdhafiz001987: Good morning.

Public chains put every payment on display. The tools built to hide that, mixers and shielded pools, then get treated as a risk by the exchanges people actually use. Transparent to the world, or private and locked out. That was the choice Mehow put on the @token2049 main stage yesterday.

AmericanFortress is arguing for a third path. A payment private to the world, readable by the recipient, and able to prove source of funds to an auditor without opening the rest of the history. No viewing keys. No pooling.

The live piece is Send-to-Name™. You pay @name. The wallet derives a fresh one-time address. Only sender and recipient can derive it. The chain sees a normal transfer. No new L1.

SafeSend™ is the sender-side shield in that design. It is not live. Do not walk through it. Do not say you used it. First path is 0G, after it ships.

Today is Quantum and Privacy Day in Singapore. The speed claim from this week still stands: post-quantum proving, 33 minutes to 3 seconds, quantum-resistant, not a shipped migration. The preprint is not peer-reviewed.

Free lifetime .free FortressName: https://t.co/q9PhSf1dKp

@Americanfort_io

YOUR MONEY. YOUR NAME. NOBODY ELSE'S BUSINESS. https://x.com/mdhafiz001987/status/2108368712093118892

## @jaouad2d (Jaouad ) · 10-09 01:08 · ♥27 ↻0 💬34 Address poisoning still works because people check the first and last four characters of a long string.

@Americanfort_io replaces that copy paste step with a FortressName. Each payment resolves to a fresh one-time address that only sender and recipient can derive, across 13 networks today.

The product is an SDK meant to sit inside wallets people already use, not another destination app.

Send-to-Name is live. SafeSend is still in development. That distinction matters. https://x.com/jaouad2d/status/2108363821882470474