### Problem: People without access to a hardware signer cannot use Bitcoin Safe. ### Mitigation Possibilities: - https://github.com/selfcustody/KruxMobileApp/releases - doesnt store seed, which is a UX problem, since the seed must be entered every time. - Krux UX is difficult, so it needs step by step guidance (screenshots) - Krux APK discourages usage on a phone for productive use... - https://github.com/cake-tech/cupcake/releases - [blog](https://blog.cakewallet.com/meet-cupcake-your-new-secret-weapon-for-crypto-security/) - Con: allows screenshot of seed https://github.com/cake-tech/cupcake/issues/47 - Con: Doesnt allow export of xpub (+ fingerprint + derivation path) via QR https://github.com/cake-tech/cupcake/issues/48 - Con: doesnt support multisig https://github.com/cake-tech/cupcake/issues/49 - Con: doesnt support testnet - But for segwit singlesig this would work. Bitcoin Safe would need to provide a restricted UX for this usecase - https://github.com/airgap-it/airgap-vault - Con: no multisig support - https://github.com/satsigner/satsigner - Con: Not dedicated only for private keeys - Pro: Compatible with Chat&Sync - no release yet While not as secure as a dedicated hardware signer, it is more secure than a seed on a desktop and might me good enough for many people. ### Steps - [ ] gather feedback
Problem:
People without access to a hardware signer cannot use Bitcoin Safe.
Mitigation
Possibilities:
While not as secure as a dedicated hardware signer, it is more secure than a seed on a desktop and might me good enough for many people.
Steps