Nostr Web Client

Unfortunately to post, you need a 'hot wallet'. Every nostr event is signed by your private key.

Currently the best way to manage your private key is by limiting the number of hot wallets that have access to it.

We still don't have an elegant solution to mitigating the loss of information from a private key breach. I suspect having delegated pubs for specific purposes might help spread our private eggs (notes) across more baskets (nsecs).

Brisket 2y ago

I guess what I'm trying to say it's that the bigger risk is not losing your key but losing exclusive access to it.

The frequency with which we need to sign events on Nostr does not lend itself to cold storage of private keys...

**Unless** we had a master npub & child npubs that sat underneath it.

Reply to this note

Please Login to reply.

Discussion

Glenn 2y ago

Couldn’t delegation be used for this? Authorize delegates for 6 months or something?

Brisket 2y ago

That's my hope.

Have you used them or know much about them?

I'm yet to have a play.

Glenn 2y ago

I have not but I think it’s a great idea. I’m in the conceptual phase of a Nostr project right now, and delegation could be an interesting element.

Obi-₿it Koinobi 2y ago

I guess the best practice for now, if you're going to be switching back and forth between clients and devices, is to have it stored in a secure location and just make sure you "log out" whenever you are done. Or at the very least if you're going to stay "logged in" to only be logged in on one device at a time.

That sound like a reasonable approach?

Brisket 2y ago

I wouldn't be pasting it into web clients when you can use Alby to sign your events/notes.

I would also try to limit the number of apps you're using it on.