SWIRL β Privacy for Bitcoin & EVM. Wallet architecture, privacy boundaries, infrastructure and recovery.
SWIRL β Privacy for Bitcoin & EVM. SWIRL is non-custodial privacy infrastructure designed to give users a consistent wallet and transaction experience across different blockchain ecosystems.
SWIRL is not a new blockchain, a custodial account or a requirement to buy a project token. Users keep control of their credentials and approve their own transactions. Each ecosystem uses architecture appropriate to its chain; the shared brand does not imply identical cryptography or identical trust assumptions.
Self-custody. Users control the secrets required to spend or withdraw. A website interface is not the owner of those secrets.
Explicit approval. Connections, signatures and transactions should be presented for user review, with supported costs and route information visible before submission.
Honest privacy boundaries. Public chain records, network metadata, timing, amounts, endpoint behavior and the available privacy set still matter. SWIRL reduces exposure; it does not promise invisibility.
Recovery without the website. A usable recovery path requires the user's credentials, compatible software and the relevant chain data or infrastructure. A hosted interface is never a substitute for backups.
| Privacy & Threat Model | What SWIRL protects, what remains visible and where trust remains |
| EVM Overview | Public and private balances, encrypted notes and network deployments |
| Wallet & Recovery | Local encryption, recovery phrases and disaster planning |
| Relayer & PPOI | Submission routes, gas, screening and their trust boundaries |
| Bitcoin Overview | How Bitcoin-specific components fit into the shared product direction |
| Testing & Verification | How to reproduce technical checks and evaluate a release |