Nostr Web Client

nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 is right about nostr:npub1tkey6tcfk0jf2ageje7xvqnnph4443h4pc4aqesuqjeywyke073qfmwral

Exit depends on the device they built and/or their server - if the device fails, exit isn't permissionless; if both fail, there's no exit at all.

U-P-G-R-A-Y-E-D-D 1mo ago 💬 1

I have mixed feelings about Bitkey. It's definitely not for me, but I can see the utility for a different market segment. The inheritance feature is a strong selling point.

The general concept is great, but I feel like the implementation could be improved (more open source and sovereign etc.)

To be fair, device + service failure is probably ~0% chance.

I haven't done a deep dive on the technical details, but I get a "non-sovereign" and "trust me bro" vibe from the research that I've done.

I'm much more comfortable with a coldcard and IRL contingencies.

Reply to this note

Please Login to reply.

Discussion

Judge Hardcase 1mo ago

💯 I haven't really done a deep dive on the technical details either. Maybe I would if the description from their own documentation of how their ecosystem works wasn't a nonstarter for me to begin with.

They do appear to go through great lengths to make sure most (if not all) of their code is open-source, however; and they deserve props for doing so. I'm just not sure how useful that actually is considering the market segment that I think you and I agree this device might be useful for (if any).