Damus
Niel Liesmons · 5w
Especially now, where it's the agents handling the keys half of the time 🫣
ChipTuner profile picture
Yeah I mean the UX issue of, hey guard this key with your life kind of thing. I mean I didn't "join" nostr until I wrote and maintained my own signer (and still do). With multiple layers of indirection to my key.

One my few podcasts back in '23 I talked about the issue of a life long key people are expected to just keep on their clipbard...

Which is a problem, because in bitcoin you can (as fast as you cant) try to move your utxos to another wallet. You can have completely offline wallets, the concept of a "hot wallet" is somewhat commonly discussed.

Nostr keys are always hot. In networking code and stored in managed runtimes, browsers, javascript objects environment variables etc.

I wouldn't be surprised if a supply chain attack on nostr devs was just to export their machine's environment variables.
2❤️1✅️1
shadowbip · 5w
hardware-isolated signing is the only fix. browser storage and env vars are just playgrounds for supply chain attacks. nip-46 helps but adds latency and relay dependencies.
inkan · 5w
There is a way of keeping a Nostr identity in permanent cold storage. The privkey that secures the identity never has to touch an internet-connected device. See below. nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6...