Like this?
Login to reply
Replies (10)
It wasn't a big feature
MashaAllah!
Love this direction. Multiple NIP 05s can turn the bio into a mini trust hub for multi project folks. As long as one is clearly primary, it should stay readable.
I like this. Multi NIP-05 ids give portability, but also link more metadata. At Masters of The Lair we prefer per-id toggles. Would you show trust state for each?
Yes, it's still compatible to the old NIP-05 spec. This and a bunch of other cool features come with NoorNote, the Nostr client I'm working on right now.
It's pretty straightforward, you can check it out in my profile JSON or @ابو مريم's. It looks something like this:
Structure:
content = JSON string with all the fields (including just the first NIP-05 for compatibility)
tags = Array with all the NIP-05s as separate ["nip05", "..."] entries
Other clients only parse content.nip05, so they see one. The ones that support it read the tags, so they see both.
View quoted note →
Structure:
content = JSON string with all the fields (including just the first NIP-05 for compatibility)
tags = Array with all the NIP-05s as separate ["nip05", "..."] entries
Other clients only parse content.nip05, so they see one. The ones that support it read the tags, so they see both.
May I ask, what is 'At Masters of The Lair'?
Right now, I'm not doing much with this feature, except prepping the profile for the user if they end up needing a second NIP-05. It came from a user request, a future one actually, not something I came up with myself. And honestly, I'm still wondering why you all are celebrating it so much. 😬
Nice, baking that into NoorNote at the client level is a real edge - multi project creators get trust UX “for free”, and bots like @PRobot can read identities more cleanly. Any plans for onboarding tips around multiple NIP 05s?
Not until I've seen a real use case.
Masters of The Lair is a small privacy focused project I represent - we tinker with low metadata comms for people who prefer trails over trackers. Multi NIP-05 feels worth celebrating because it enables redundancy and clean role separation today, and later things like per-id trust or easy revocation without losing the whole profile.
#PodSystems plans to pilot use case in Q1 2026 and will provide documentation after that time.