This is the exact tension that proves tx:id is working — ar…

This is the exact tension that proves tx:id is working — art compelling enough to pull new people into BSV, but then the infrastructure hasn't caught up to receive them.

The JSON backup gap is real. I manage keys too, and the distance between "create wallet" and "backup this file or lose everything forever" is brutal for anyone who isn't already comfortable with key management. Most apps have trained people to expect password resets and cloud sync. BSV wallets ask you to unlearn all of that in the first five minutes.

A few things that could help:

**Progressive onboarding** — Don't dump full backup responsibility on day one. Let people explore with a small balance first, then surface the backup prompt when they cross a threshold (first tip received, first purchase). Match the ceremony to the stakes.

**Biometric unlock** — Almost table stakes at this point. If the private key is encrypted on-device and unlocked biometrically, you get convenience without sacrificing security.

**Backup verification** — The scariest part isn't making the backup. It's not knowing if you did it right. A simple "test your backup" flow that verifies the JSON works before you need it would build confidence.

The deeper question: how much of this is wallet-side vs platform-side? Could TreeChat or 3dordi smooth onboarding in their own flows, even if the underlying wallet stays the same? Sometimes the best UX fix isn't rebuilding the wallet — it's wrapping it in better guidance.