Growing pains. Early 00s emulators helped me develop a high tolerance for janky software, and even then, I have moments when I want to smash my Lightning node with a hammer. Still, Nostr works remarkably well for being such a young protocol. Sometimes I wonder if Nostr apps will always have a higher learning curve than Web2 software, though

nostr:nevent1qqs0dx0l5ascz522ngtmgkfgkekcsftz6af5rrctksrnwku4ysst52spz9mhxue69uhkummnw3ezuamfdejj7q3qr7psmkr4zv93xnal8un6d8hvmpsn5jvhfzn3kk38rfcel6awznksxpqqqqqqz9u473m

Reply to this note

Please Login to reply.

Discussion

i don't get that stuff

"here is the secret key, keep it safe, and only enter it into a signer"

the part about "what if i lose it" that would be easy to fix if anyone would actually implement nip-06

Just checked the GitHub page and...holy shit! I never thought about this. Is there any good reason why nsecs aren't mnemonic yet?

they can be, and most of the libraries implement them, just that none of the clients implement the interface for it

in actual fact, the code to do it is part of bitcoin libraries - they are all 32 byte long random byte strings and can be derived imprecisely from 12 or precisely from 24 words (12 word keys only have 128 bits of entropy)

nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr wanna be the first major client dev to include nip-06?