The standards work that gets users one identity across time and wallets: • Standard wallet DB formats — Hodos's DB is based on the @BSVAssociation TypeScript SDK designed by @ProjectBabbage, with some differences. DB and import/export standardization can facilitate portably across wallet. • Decentralized paymail — needed so handles aren't bound to operator domains; this is what makes paymail itself part of the identity that travels with you. Certificates attesting to ownership of accounts like x.com would be portable across wallets but still tie Web3 identity to domains. @deggen has been pushing thinking on this; we also touched on it in yesterday's reply to his URI scheme thread. • Standard token protocols — work in progress across the ecosystem; this is what lets tokens move with users without being locked to a specific wallet. Different teams, same goal: deliver one cohesive identity that travels with the user. Cross-device sync is the same fragmentation problem in a narrower scope, with a different fix. @ruthheasman raised this from the builder side on @GavinMehl's show last week — no BRC-100 wallets really sync across devices today. BRC-100 wallets derive counterparty keys via BRC-42, which has real upside (privacy, per-pairing isolation) but a recovery cost — counterparty-derived keys can't be re-derived from mnemonic alone; you need to know the counterparties invoice numbers. So BRC-100 wallets need active backup, not just a seed. Most handle this via cloud backup and this cloud backup could likely be be used to sync a single user wallet across multiple devices. Hodos uses an on-chain backup token instead — non-standard, something we developed and are still iterating. Discoverable from your keys, encrypted. The same mechanism could potentially enable cross-device sync without a central server, though we may move to a more standard cloud model if that proves cleaner. Open to others thinking about this with us. Sidebar back to the IPv6 thread earlier today: cross-device sync needs a central server precisely because devices can't talk peer-to-peer at consumer-wallet scale. Same root cause as the "P2P" framing problem — different symptom.

@paiybit — we tried the QR-scanner approach we discussed on @GavinMehl's space for unlocking content on your site, and it works. Unlocking the paywall this way was smooth and easy (one video I tested didn't, likely because we don't have a QR standard). This method is probably simpler for devs (and their AI assistants) to implement than BRC-100 HTTP requests right now, even with the SDKs but - the site UX still has friction. We think one-click account creation, one-click sign-in, and one-click payments via BRC-100 calls is the cleaner end-state. Going to break that down in our next video.