Transaction Safety Quiz

Transaction safety quiz · 8 situations · about 6 minutes

Where does the money go wrong?

Eight situations where crypto users lose funds, privacy or sleep. The examples are fictional and illustrate common risks. Your job: pick what stops it. Some answers are a FortressName. Some are a feature still being built, and we say so. One of them is you. Any name you enter is optional and used only to personalize the examples.

Both optional. Use a fictional name or handle if you prefer.

Your result

0 / 8

Transaction protections covered in the quiz

Send-to-Name™

Availability to confirm

You send to @name on supported networks. The name never resolves to a static public address; the destination is derived privately between the two wallets. No address to copy, paste, poison or mistype.

FortressName™ privacy

Availability to confirm

An onlooker who sees your name does not get a direct link to your full wallet balance from the name alone. A counterparty who pays you sees one address, derived for that relationship alone and public like any address, but not your other addresses or your total holdings.

FortressChat

Availability to confirm

Encrypted threads tied to names, with payment requests inside the thread. The request and the payment travel the same verified rail, so a swapped address in an email has nothing to swap.

FortressID™

Availability to confirm

Verified identity attached to a name. You disclose exactly the fields you choose, to exactly the counterparty you choose, inside the chat.

Proof of source of funds

Protocol

A proof can help a recipient assess where funds came from without a public record of the full wallet history. Coverage and acceptance depend on the integration.

SafeSend™

In development

Shields the sending side: your balance and amounts stay confidential on the native chain, with no pooling. Not usable today.

ZKPoSP quantum path

Research · IACR ePrint

Zero-knowledge proof of seed provenance: a wallet proves it owns a seed and every key derived from it without revealing them. A proposed recovery approach that aims to avoid address migration. QBIP-32 enhances the proof's performance and security.

You

No substitute

Nothing above stops you handing over a seed phrase. Never share your recovery words or enter them through a link sent in a message.

An educational tool from AmericanFortress. Every person, message, address and transaction shown is fictional. Product availability and wording are pending team review. Send-to-Name™ removes address handling from flows that use names; it does not end every scam, and no product does.