nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-20 14:55:49 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

More typos

Browse Source
This commit is contained in:
Vitor Pamplona 2024-03-28 19:19:37 -04:00
parent b9c9a3409e
commit b88346caf4
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
59.md
View File

@ -6,7 +6,7 @@ Gift Wrap
`optional`
This NIP defines event kinds and procedures for encapsulating other nostr events with variying degrees of privacy. The goal is to provide tools to obscure the right amount of metadata for separate use cases.
This NIP defines event kinds and procedures for encapsulating other nostr events with varying degrees of privacy. The goal is to provide tools to obscure the right amount of metadata for separate use cases.
This NIP *does not* define any messaging protocol. Applications of this NIP should be defined separately.
@ -44,7 +44,7 @@ A `seal` is a `kind:13` event that wraps a `rumor` and is signed with the sender
`.content` contains the cyphertext of the [NIP-44](44.md) encryption of the JSON-encoded rumor.
Tags MUST must always be empty.
Tags MUST always be empty.
The inner event MUST always be unsigned.
@ -116,9 +116,9 @@ If the `rumor` is intended for more than one party, or if the author wants to re
The canonical `created_at` time belongs to the `rumor`. All other timestamps SHOULD be tweaked to thwart time-analysis attacks. Note that some relays don't serve events dated in the future, so all timestamps SHOULD be in the past.
# Gift Wrap as an onion routing payload
# Gift Wrap as an onion-routing payload
Gift wraps can be used separetedly to hide any signed event from the public and routing relays/servers.
Gift wraps can be used separately to hide any signed event from the public and routing relays/servers.
For instance, to send an event through a push notification stack without the stack knowing about the event or who is it for, simply wrap it on a `kind 1059` event. Since the stack already has a token, the `p` tag to the receiver (which would reveal who the receiver is) is not needed.