Skip to content

Define 56xx range#22

Draft
benthecarman wants to merge 2 commits into
nostr-protocol:masterfrom
benthecarman:56xx
Draft

Define 56xx range#22
benthecarman wants to merge 2 commits into
nostr-protocol:masterfrom
benthecarman:56xx

Conversation

@benthecarman

Copy link
Copy Markdown
Contributor

Still playing around if this is the correct input parameters but have one running here: npub1e222rh2n4eh4tf5900399mnpa06phl7zazvyng2cm95f57ja0alqg055t4

@dtdannen

Copy link
Copy Markdown

This is really cool. Reserving a block of 100 makes sense, and when we need more we can go beyond the current ranges of 5000-5999.

One thing to keep in mind is that a popular kind id right now is 6666, although I don't know much about them. They seem to mostly contain data regarding relays, apnTokens, and addresses. So maybe we should make a note that people should avoid 5666?

@EthnTuttle

Copy link
Copy Markdown

Recommend adding a checksum for the binary to ensure the correct binary is downloaded that is requested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants