Single-key wallet
Create, recover, receive, label, select coins, review, sign, broadcast, and rescan on regtest.
Development status
Built on regtest. Not ready for mainnet.
Much of the wallet is implemented through the real Rust and Tauri boundary. Physical certification, release provenance, platform hardening, and independent review still stand between this build and real funds.
Rust/Tauri implementationAutomated evidence trackedMainnet gate locked in CI
Working now
Implemented for test networks.
“Implemented” means the capability crosses the real native boundary. It does not mean every device, platform, or failure mode is certified.
Descriptor multisig
Standard BIP48 sortedmulti policies, persistent PSBT proposals, signature collection, and descriptor recovery drills.
Hardware boundary
HWI enumeration, fingerprint matching, signing, and device-address comparison are integration-ready.
Bitcoin Core
Per-wallet local, direct HTTPS, or Tor-onion Core configuration with no silent backend or fee fallback.
Interchange
Public BSMS descriptor records plus bounded PSBT file, text, and UR v2 exchange.
Multiple wallets
Isolated wallet profiles, databases, credentials, sessions, node configuration, and deletion.
Release blockers
Evidence before access.
Mainnet remains compile-time disabled until every required artifact is reviewed and the dedicated release gate is replaced deliberately.
Hardware matrix
Testnet4 evidence across Coldcard, Trezor, Ledger, BitBox02, and Jade with real devices and firmware records.
Platform hardening
Mobile lifecycle, physical camera flows, and Android and Windows secure-storage certification.
Recovery evidence
Large-history progress, extended-gap recovery, and independent descriptor-wallet round trips.
Network evidence
Real remote Bitcoin Core deployments over TLS and Tor, including failure and privacy tests.
Release evidence
Matching clean-build hashes, signed and notarized packages, SBOM and provenance, and independent review.
Source of truth
The ledger is public and specific.
Every capability is separated into browser fixture, Rust/Tauri implementation, automated evidence, and release status. Canonical records remain versioned with the repository.