nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 00:45:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

update dns

Browse Source
This commit is contained in:
asmogo 2024-12-12 22:25:01 +01:00 committed by GitHub
parent 962d800d6e
commit 29c4ccd00a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
74.md
View File

@ -6,7 +6,7 @@ Nostr Web Services (NWS)
`draft` `optional`
This NIP defines a standard for facilitating TCP requests over NOSTR relays to a specified destination. The implementation is currently available at [https://github.com/asmogo/nws](https://github.com/asmogo/nws).
This NIP defines a standard for facilitating TCP requests over NOSTR relays to a specified destination. One basic implementation is currently available at [https://github.com/asmogo/nws](https://github.com/asmogo/nws).
### Motivation
@ -53,13 +53,16 @@ The `type` field specifies the type of message and is required. There are three
- Used for transmitting data to the upstream destination after a connection has been established.
- The `entryPublicAddress` parameter should only be provided when using `CONNECTR` message types.
Messages must be sent using events with `kind:28333`. The content must be encrypted using NIP-04 or NIP-44.
Messages must be sent using events with `kind:28333`. The content must be encrypted using NIP-44.
### Domain
### Domain Name System
The `.nostr` domain of an exit node is a [base32](https://datatracker.ietf.org/doc/html/rfc4648) encoded public key with the `.nostr` TLD suffix.
The `.nostr` domain of an exit node is a [base32](https://datatracker.ietf.org/doc/html/rfc4648) encoded public key with the `.nostr` TLD suffix.
Subdomains are also [base32](https://datatracker.ietf.org/doc/html/rfc4648) encoded and are used to specify relay servers.
The client can use this domain to resolve the relays and the recipient of the messages.
Base32 encodings are required to use the "Extended Hex Alpabeth" defined in RFC 4648 and should no contain any padding.
This domain name system essential, as exit nodes can inform clients of how they can be reached while creating a `kind:38333` event.
Clients can use this domain to resolve the relays and the recipient of the messages they want dispatch.
#### Example:
Sending a request to the following domain: