👋 I think this ultimately comes down to the question, "why not just allow seed export for the people who want it and know what they're doing?" I think this is very reasonable, and ethos-aligned with self custody. We fundamentally believe hardware devices should protect the key, not just sign with it. So our hardware is designed to never export its secret; the APIs simply don’t exist. That gives us a very powerful security posture: there is only one copy of the HW key in the world, and access to it is gated by a physical device with biometrics. I would hesitate to erode that property. But it’s clear that some customers, like yourself, would prefer to give up that property in exchange for having a direct copy of your key. One way to support that, without weakening Bitkey’s non-exportability posture, would be to let customers set a seed phrase into Bitkey instead of having the hardware generate its own. That would preserve the principle that Bitkey-generated hardware keys are never exported, while still giving power users a way to use the wallet with keys they have access to outside the wallet. Would something like that get at what you’re trying to achieve?

My dear front-end developers (and anyone who’s interested in the future of interfaces): I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept): Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow