I keep a list, as json, but I also make sure that they're all listed on the NIP repo ReadMe (scroll down to Events).
https://github.com/nostr-protocol/nips/blob/master/README.md
Sorry, not quite. That’s the NIPs, which are also numbered.
Each “event” in Nostr has a numeric “kind” field. Regular text notes like these have kind=1. Reactions (likes) have kind=7, etc.
When people make Nostr-based apps, often they’ll use new, previously unclaimed kind numbers to have specific meanings for their apps.
I seem to recall someone making a registry of these kind number meanings. Maybe nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl ?
I keep a list, as json, but I also make sure that they're all listed on the NIP repo ReadMe (scroll down to Events).
https://github.com/nostr-protocol/nips/blob/master/README.md
Thank you! Yeah, I’m working on an app, and need to pick a kind number.
My algo is:
1. concatenate the project name and purpose as a string.
2. SHA256 hash the name-purpose
3. Take the first 4 bytes as int 32.
4. Modulo this number and add basis for specific kind range.
So for example, if you need a parameterized replaceable event, you mod 10000 and add 10000.
Has anyone already written guidance of this sort for picking kind numbers for app purposes?
Here's the wiki page with two json registers