Understand what you trust.
The app, contracts, proving artifacts, device, and network all affect the safety of a payment.
Software and proof assumptions
Correctness depends on the pool contracts, circuits, verifier configuration, and cryptographic setup. A valid proof enforces the circuit as written; it does not demonstrate that all software is bug-free. Mirk has not received an external audit.
Device and storage
Use a browser that supports IndexedDB and secure browser cryptography. Private browsing or restrictive storage policies can prevent the store from opening. Clearing site data removes local records. Keep your browser and wallet secure, and maintain an encrypted backup.
Availability and settlement
RPC providers, the relay, and chain confirmation can fail or be delayed. Keep the app open during proof generation and confirmation. Check transaction hashes before retrying; rescan to reconcile local state after an interruption.
Current scope
Trade and Marketplace are unavailable. Mirk does not offer a hosted recovery service, guaranteed anonymity, or automatic migration from a legacy pool. Private balance data cannot be recovered by support without the required secrets.
When reporting an issue
Record the screen, error text, network, and public transaction hash when available. Never include a wallet seed phrase, private key, complete claim link, decrypted note, backup file, or backup passphrase in an issue report.