relay tags in nip-60 on 17375 instead of 10019 #2080
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
They should probably be NIP-51 private, no? |
I hesitated about it like 6 times, ok, yes, I agree 😂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moving the authoritative
relaywere wallet events (kind:737{4,5,6}) are to be found.Recently we had changed this to be in 10019 but on closer inspection this doesn't make much sense, relays in 10019 is essentially like the nutzaps inbox whereas relays in
kind:17375are for the user's own sake. For example, a user might use ws://localhost:8888 to store their tokens events.cc @callebtc