{"version":1,"id":"americanfortress","title":"AmericanFortress","summary":"AmericanFortress is a privacy-focused company that provides human-readable FortressName identities and a ZK-powered SafeSend privacy layer to resolve names to fresh stealth addresses across supported networks.","content":"**AmericanFortress** is a privacy infrastructure company that develops a name-based transaction system for [blockchain](https://iq.wiki/wiki/blockchain) networks, binding human-readable identity names to one-time stealth addresses so that assets can be sent and received without exposing a user's wallet address.[\\[1\\]](#cite-id-79m3h7q7xq)​[\\[2\\]](#cite-id-6r2sty4sa3) \n\n## Overview\n\nAmericanFortress markets its system under the slogan \"Your money. Your . Nobody else's business,\" and frames its purpose around what it describes as the privacy risks of transacting on public [blockchains](https://iq.wiki/wiki/blockchain).[\\[3\\]](#cite-id-e654kjateh) The company presents several figures to illustrate those risks: a \"$33T\" figure labelled \"Your wallet address is your dox\" (attributed on the site to Bloomberg and TRM); \"88%\" tied to the claim that salaries paid on-chain are publicly visible (labelled Q1 2025); \"820M+\" with the caption that visible holdings make holders a target online and off (labelled 2025); and \"1.1M BTC\" describing Satoshi-era [Bitcoin](https://iq.wiki/wiki/bitcoin) with exposed [public keys](https://iq.wiki/wiki/public-key) said to be vulnerable to advancing quantum computing.[\\[3\\]](#cite-id-e654kjateh)​\n\nThe company identifies three problems it aims to solve with current wallets: addresses are \"vulnerable\" because an exposed address can reveal transaction history, amounts, and balance activity; they are \"hard to use\" because long strings are easy to mistype and a wrong destination can make a transfer irreversible; and many existing privacy methods are \"non-compliant\" because pooling funds or obscuring trails can create compliance concerns.[\\[4\\]](#cite-id-zr7ch4u86x) Its stated core mechanisms are decentralised KYC/AML compliance options, a post-quantum-secure hierarchical deterministic wallet architecture, and cross-chain compatibility.[\\[2\\]](#cite-id-6r2sty4sa3)​\n\n## Products\n\n### FortressName\n\nFortressName is a reusable, human-readable identity name that resolves to fresh addresses across supported integrations. The company's stated flow is that a user chooses \"@yourname\" once and then uses the same identity across supported networks; custom names are reserved through checkout.[\\[3\\]](#cite-id-e654kjateh)​[\\[4\\]](#cite-id-zr7ch4u86x) A FortressName can be shared publicly — on social media, a website, or an invoice — and supported integrations can derive a unique stealth address for a given transaction without mixing, tumbling, or pooling funds.[\\[3\\]](#cite-id-e654kjateh) The company states that a supported recipient wallet will always show the sender's name, while on-chain observers see only the receiving address rather than a public name directory.[\\[3\\]](#cite-id-e654kjateh).[\\[4\\]](#cite-id-zr7ch4u86x)​\n\n### SafeSend and Send-to-Name\n\nSafeSend (SafeSend) is described as a \"ZK-powered transaction privacy layer\" — a reference to [zero-knowledge proofs](https://iq.wiki/wiki/zero-knowledge-proofs-zkps), a cryptographic technique for proving a statement true without revealing underlying data — that is designed to reduce public exposure \"without mixing, tumbling, or pooling funds.\"[\\[3\\]](#cite-id-e654kjateh) The company repeatedly differentiates it from a mixer, tumbler, or pooled-funds service, and states it is \"entirely non-custodial\" with \"no viewing keys, no back doors to your privacy.\"[\\[3\\]](#cite-id-e654kjateh) The product includes a one-click toggle labelled \"Untracable Quantum Send.\"[\\[3\\]](#cite-id-e654kjateh)​\n\nThe underlying send-by-name feature is called Send-to-Name (Send-to-Name™) and follows a four-step flow summarized by the slogan \"You type a name. We handle the rest.\" A user types an \"@name\" instead of a hex string or QR code; the sender's wallet generates a unique stealth address in the background that is computable only by sender and recipient; the transaction is sent on-chain to a one-time receiving address computed for that payment, with the recipient retaining control of the funds without placing their name on-chain; and a supported recipient wallet can then display the sender's name while on-chain observers see only the receiving address.[\\[4\\]](#cite-id-zr7ch4u86x)​[\\[3\\]](#cite-id-e654kjateh)​\n\n### SDK and Integrations\n\nThe company offers its technology through a single software development kit (SDK) marketed as \"One SDK. Multiple networks,\" designed to let developers integrate Send-to-Name functionality into applications and [AI agents](https://iq.wiki/wiki/ai-agents) with stealth addresses across multiple chains.[\\[3\\]](#cite-id-e654kjateh)​[\\[1\\]](#cite-id-79m3h7q7xq) As of June 2025 the company stated that Send-to-Name supported [Ethereum](https://iq.wiki/wiki/ethereum), [Bitcoin (BTC)](https://iq.wiki/wiki/bitcoin-btc), [Bitcoin Cash](https://iq.wiki/wiki/bitcoin-cash), [eCash](https://iq.wiki/wiki/ecash), [Litecoin](https://iq.wiki/wiki/litecoin), [CSPR](https://iq.wiki/wiki/cspr), and [ERC-20](https://iq.wiki/wiki/erc-20) tokens, with more planned.[\\[1\\]](#cite-id-79m3h7q7xq) Chain and feature availability depend on the participating wallet and integration.[\\[4\\]](#cite-id-zr7ch4u86x)​\n\n## Tokenomics\n\nAmericanFortress proposes a [utility token](https://iq.wiki/wiki/utility-token), $AF, planned for name-registry and privacy-layer operations; the company describes the token as securing \"all of crypto for humans and [AI agents](https://iq.wiki/wiki/ai-agents).\"[\\[3\\]](#cite-id-e654kjateh)​[\\[1\\]](#cite-id-79m3h7q7xq) The company states that the token's utility, network availability, and launch timing remain subject to final technical and legal review.[\\[3\\]](#cite-id-e654kjateh)​\n\nThe proposed [tokenomics](https://iq.wiki/wiki/tokenomics) would use a portion of eligible FortressName revenue and certain protocol fees for token buybacks. The company states that final percentages and burn mechanics will be published only after approval.[\\[3\\]](#cite-id-e654kjateh)​\n\n## Leadership and Team\n\n* **Michal \"Mehow\" Pospieszalski** — Co-Founder, CEO and CTO, described as a technologist with expertise in cryptography, [blockchain](https://iq.wiki/wiki/blockchain) security, and fintech infrastructure.[\\[3\\]](#cite-id-e654kjateh) The company states he has spent more than 20 years finding security flaws, including work hacking electronic voting machines for the U.S. government.[\\[1\\]](#cite-id-79m3h7q7xq)\n* **Chris Odom** — Technical Co-Founder, described as an open-source advocate building secure financial infrastructure.[\\[3\\]](#cite-id-e654kjateh)\n* **Emanuele Ragnoli, PhD** — Chief Cryptographer, a mathematician and cryptographer specializing in multi-party computation, hardware acceleration, and security.[\\[3\\]](#cite-id-e654kjateh)\n* **Vincenzo Botta, PhD** — Cryptography Engineer, developing privacy-preserving protocols and zero-knowledge proof systems.[\\[3\\]](#cite-id-e654kjateh)\n* **Seb Audy** — COO and Head of Finance, described as a Deloitte and [World](https://iq.wiki/wiki/world) Bank alumnus who builds the finance and operating systems the company needs to scale.[\\[3\\]](#cite-id-e654kjateh)\n* **Jakub Żurawiński** — Chief Business Development Officer, connecting the company with enterprise partners and commercial opportunities.[\\[3\\]](#cite-id-e654kjateh)\n* **Jakub Rojek** — Senior Software Developer, a core platform engineer focused on product delivery and privacy infrastructure.[\\[3\\]](#cite-id-e654kjateh)\n","categories":[{"id":"organizations","title":"organizations"}],"tags":[{"id":"DataPlatform"},{"id":"Bitcoin"},{"id":"Ethereum"}],"images":[{"id":"QmcRfZdUDnpL3EhkUPqhpo1jUrGNes68DPdUW5JejouwSH","type":"image/jpeg, image/png"}],"media":[],"metadata":[{"id":"references","value":"[{\"id\":\"79m3h7q7xq\",\"url\":\"https://www.linkedin.com/company/americanfort/home/\",\"description\":\"Company profile, headquarters and aliases\",\"timestamp\":1791693239528},{\"id\":\"6r2sty4sa3\",\"url\":\"https://www.rootdata.com/projects/detail/AmericanFortress?k=MjM1Mzc%3D\",\"description\":\"Name-based privacy transaction layer\",\"timestamp\":1791693239528},{\"id\":\"e654kjateh\",\"url\":\"https://americanfortress.io/#af-token\",\"description\":\"Slogan and framing of privacy risks\",\"timestamp\":1791693239528},{\"id\":\"zr7ch4u86x\",\"url\":\"https://americanfortress.io/how-it-works\",\"description\":\"Three stated problems with current wallets\",\"timestamp\":1791693239528},{\"id\":\"f85bmwcwbo\",\"url\":\"https://thenextweb.com/news/americanfortress-zkp-crypto-wallet-ownership-provenance-proofs\",\"description\":\"Provenance Proofs paper authors and date\",\"timestamp\":1791693239528}]"},{"id":"rootdata_profile","value":"https://www.rootdata.com/Projects/detail/AmericanFortress?k=MjM1Mzc="},{"id":"website","value":"https://americanfortress.io/"},{"id":"twitter_profile","value":"https://x.com/Americanfort_io"},{"id":"linkedin_profile","value":"https://www.linkedin.com/company/americanfort"},{"id":"main-image-origin","value":"{\"imageId\":\"QmcRfZdUDnpL3EhkUPqhpo1jUrGNes68DPdUW5JejouwSH\",\"originalId\":\"QmcRfZdUDnpL3EhkUPqhpo1jUrGNes68DPdUW5JejouwSH\"}"},{"id":"commit-message","value":"Create AmericanFortress wiki"}],"events":[],"linkedWikis":{"founders":[],"blockchains":[],"speakers":[]},"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x4a2bC97afBF41a2Cbf4b4628F63420682Ff4CF2a"},"language":"en","operator":{"id":"0x4a2bC97afBF41a2Cbf4b4628F63420682Ff4CF2a"}}