Secrets stay off this website
This site has no mnemonic, private-key, backup-upload, or passphrase form. A legitimate support conversation should never require these secrets. An address or extended public key is not a signing key, but disclosure can still expose financial history.
Device, build, and distribution
A self-custodial model still depends on the device and the code handling keys. Verify the publisher and release provenance independently. A SHA-256 hash identifies a file; it does not establish that the file is safe or comes from a trusted developer.
Privacy depends on the network
A network provider can observe wallet queries. Transparent chains can expose transaction relationships; privacy-oriented networks have different disclosure models. A shared interface must explain these differences rather than promise identical privacy for every asset.
Permissions and transaction context
Network identity, token identity, and transaction intent must remain visible during authorization. A token approval can grant a spending allowance. UTXO transactions require review of inputs and change; other networks need their own review fields.
Review before authorization
Check the selected network, asset identity, full destination, amount, fee, any memo or tag, and contract permissions. Authorization must be enforced by the signing application. An unavailable or unverified network integration must not enable a transfer.
Security claims must be earned
No audit, certification, insurance, independent binary review, or production security assurance is claimed for Samourai Crypto Wallet or the supplied packages. Such evidence belongs in the roadmap before a live release.
Research & network documentation
Explore historical Bitcoin research alongside official documentation for the networks and assets in the Samourai Crypto Wallet catalogue.
Sources