Probably still managed to code and release a new micro app while you were sleeping. Check your git logs...

Suddenly realizing that I need to build in some #[2] Easter eggs...

And sometimes the irl nips take a break from us. 😭

The NIPs are getting kind of overwhelming to follow. I think a lot of these app-level NIPs are almost more akin to an open API that could just be discussed and documented in their own repo/site.

Keep a master listing of reserved kind IDs, but then point elsewhere for the details.

Meanwhile the more protocol-level NIPs remain as NIPs but with less clutter to sort through.

Also, given where we hope this all will go, it's not really reasonable to think that every possible use case can or should be defined in one place.

NAP + reserve its kind IDs.

(Nostr Application Proposal)

Not something that needs protocol-wide support / implementation.

#[2] #[3]

You are correct.

One should NOT use their Nostr BIP-39/NIP-06 mnemonic phrase as a Bitcoin wallet, even though they are perfectly compatible.

Nor should someone use their existing Bitcoin BIP-39 mnemonic to derive their NIP-06 Nostr key.

Damn, that failed "@" ref is #[4] 's fault!

(now that we're friends, Martti's gonna get even more bug reports and feature requests from me!)

Woot! Snort/@npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 / #[3] always on the cutting edge!

Caveat: existing Nostr keys cannot* go back in time and generate a BIP-39 mnemonic backup phrase.

These BIP-39 mnemonic backups only work for new Nostr keys being generated with this specifically in mind.

---

*(caveat to the caveat: akshually... you could generate a BIP-39 mnemonic from an existing key, BUT it would not be NIP-06 compliant)

I totally forgot to mention in my talks at #[0] that you can derive a Nostr key from a BIP-39 mnemonic backup phrase.

* You (or more likely your Nostr client app) generates a new mnemonic backup.

* Write it down and protect it just like a Bitcoin seed.

* Client app derives your Nostr key from that seed.

#[1], #[2], #[3], #[4] for app-generated Nostr keys, it'd be nice to go through NIP-06 derivation (`m/44'/1237'/0'/0/0`) and provide the mnemonic as their backup.

Eventually when we get keys out of browsers, we'll want more robust backup solutions. May as well piggy back on what's already out there (e.g. steel plates) for Bitcoin.

Can generate BIP-39 -> NIP-06 keys via https://nostrtool.com

I had never used Rust before but it was almost shockingly ease to get things running.

https://github.com/grunch/rana

Community-donated #[0] Edition #[1] #10 was given to:

#[2] Fighting for decentralization via words, action, and millions of sats; Nostr official greeter; funded the #Nostrica conference; cool dude who's been on this ride before.

ps - it occurred to me that I should have explained what a SeedSigner is when I gave it to you. It's a DIY air-gapped bitcoin signing device with some unique twists (build it yourself from off-the-shelf parts, does NOT store your PK onboard at rest). Completely FOSS. My Nostrica edition of the code includes air-gapped event signing & NIP-26 delegation. Can try it out via nostrtool.com (once I push my updates that add QR support).

Community-donated #[0] Edition #[1] #8 went to:

#[2] one of the key #Nostrica organizers and Nostr community builder.

The conference being small enough that by the second and third day, you just about recognize everyone and get the second, third, fourth encounters you need really feel like you're getting to know someone.

Gm #[0]

Number 10!

Ready to pay to subscribe to #[0] #[1]

Ready to pay to subscribe to Snort #[0]

Ready to subscribe to Damus #[0]

#[3] rocking the #[1] dogtag onstage!