2023-08-11 11:34:56 -04:00
NIP-59
======
Gift Wrap
---------
`optional`
2024-03-28 19:19:37 -04:00
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.
2023-08-11 11:34:56 -04:00
2024-01-09 16:39:58 -05:00
This NIP *does not* define any messaging protocol. Applications of this NIP should be defined separately.
2023-08-11 11:34:56 -04:00
This NIP relies on [NIP-44 ](./44.md )'s versioned encryption algorithms.
# Overview
2024-03-28 18:23:30 -04:00
This NIP uses three main primitives to protect the metadata of an event: `rumor` s, `seal` s, and `gift wrap` s.
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
- A `rumor` is any unsigned nostr event. If it is leaked, it cannot be verified.
2024-03-28 19:15:09 -04:00
- A `seal` signs the encrypted rumor in its `.content` , making the rumor verifiable without revealing it.
2024-03-28 18:23:30 -04:00
- A `gift wrap` encrypts any other signed event using random private keys to a known destination in its `tags` .
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
The rumor carries the content itself but if it leaks it will be rejected by relays and clients and can't be authenticated. This provides a measure of deniability.
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
The `seal` exposes the signer, but not the contents or the receiver. The `gift wrap` exposes the receiver, or an alias to the receiver, but not the signer.
2023-08-11 11:34:56 -04:00
2024-03-28 19:15:09 -04:00
The 3 primitives can be used together or separately depending on the application.
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
## The Seal Event Kind
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
A `seal` is a `kind:13` event that wraps a `rumor` and is signed with the sender's regular private key. The `seal` is **always** encrypted to a receiver's pubkey but there is no `p` tag to expose who can decrypt it. There is no way to know who the rumor is for without the receiver's or the sender's private key. The only public information in this event is who is signing it.
2023-08-11 11:34:56 -04:00
```js
{
"id": "< id > ",
"pubkey": "< real author ' s pubkey > ",
2024-03-28 19:21:55 -04:00
"created_at": "< now or random time up to 2 days in the past > ",
2023-08-11 11:34:56 -04:00
"kind": 13,
"tags": [],
2024-03-28 18:23:30 -04:00
"content": nip44Encrypt(rumor, "< recipient pubkey > ", "< author ' s private key > "),
2023-08-11 11:34:56 -04:00
"sig": "< real author ' s pubkey signature > "
}
```
2024-03-28 18:23:30 -04:00
`.content` contains the cyphertext of the [NIP-44 ](44.md ) encryption of the JSON-encoded rumor.
2024-03-28 19:19:37 -04:00
Tags MUST always be empty.
2024-03-28 18:23:30 -04:00
The inner event MUST always be unsigned.
2023-08-11 11:34:56 -04:00
2024-03-28 19:19:43 -04:00
To increase privacy, `.created_at` MAY not be accurate. The `extension` tag can be used to minimize the existence of the event after a certain date.
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
## The Gift Wrap Event Kind
A `gift wrap` event is a `kind:1059` event that wraps any other event. `tags` SHOULD include any information needed to route the inner event to its intended recipient, including the recipient's `p` tag or [NIP-13 ](13.md ) proof of work.
2023-08-11 11:34:56 -04:00
```js
{
"id": "< id > ",
"pubkey": "< random , one-time-use pubkey > ",
2024-03-28 19:21:55 -04:00
"created_at": "< now or random time up to 2 days in the past > ",
2023-08-11 11:34:56 -04:00
"kind": 1059,
2024-03-28 18:23:30 -04:00
"tags": [["p", "< recipient pubkey > ", "< relay > "]],
"content": nip44Encrypt(event, "< recipient pubkey > ", "< random private key > "),
2023-08-11 11:34:56 -04:00
"sig": "< random , one-time-use pubkey signature > "
}
```
2024-03-28 18:23:30 -04:00
`.content` contains the cyphertext of the [NIP-44 ](44.md ) encryption of the JSON-encoded event.
2023-08-11 11:34:56 -04:00
2024-03-28 19:19:43 -04:00
To increase privacy, `.created_at` MAY not be accurate. The `extension` tag can be used to minimize the existence of the event after a certain date.
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
Relays SHOULD only serve `kind 1059` events intended for the marked recipient based on user AUTH.
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
Clients SHOULD only send wrapped events to destination relays that offer this protection.
2023-08-11 11:34:56 -04:00
2024-03-28 19:15:09 -04:00
Relays MAY choose not to store gift-wrapped events due to them not being publicly useful. Clients MAY choose
2024-01-31 10:11:14 -05:00
to attach a certain amount of proof-of-work to the wrapper event per [NIP-13 ](13.md ) in a bid to demonstrate that
2023-08-11 11:34:56 -04:00
the event is not spam or a denial-of-service attack.
2024-03-28 18:36:10 -04:00
# Privacy-first Protocol
2024-03-28 18:23:30 -04:00
In cases of elevated privacy needs, the 3 primitives can be used together, one after another. In this scheme, even if all of the decrypted payloads leak, the sender and receiver are not publicly connected in a verifiable event and none of the inner event's information can be publicly verified.
To transfer an event from pubkey A to pubkey B, perform the following steps:
1. Turn an event into a Rumor by deleting the signature.
2. Seal the Rumor
3. Gift Wrap the Seal
4. Send the Gift Wrap to the relays of the receiver.
In pseudo-code:
```js
{
"id": "< id > ",
"pubkey": "< random-pubkey > ",
"created_at": randomTimeUpTo2DaysInThePast()
"kind": 1059,
"tags": [
["p", "< pubkey-B > "],
],
"content": nip44Encrypt({
"id": "< id > ",
"pubkey" "< pubkey-A > ",
"created_at": "created_at": randomTimeUpTo2DaysInThePast()
"kind": 13, // seal
"tags": [],
"content": nip44Encrypt(rumor, pubkeyB, privkeyA),
"sig": "< signed by pubkey-A > "
2024-03-28 18:36:10 -04:00
}, pubkeyB, privkeyRandom),
2024-03-28 18:23:30 -04:00
"sig": "< random , one-time-use pubkey signature > "
}
```
If the `rumor` is intended for more than one party, or if the author wants to retain an encrypted copy, a single `rumor` may be sealed, wrapped and addressed for each recipient and the author individually.
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.
2024-03-28 19:19:37 -04:00
# Gift Wrap as an onion-routing payload
2024-03-28 18:23:30 -04:00
2024-03-28 19:19:37 -04:00
Gift wraps can be used separately to hide any signed event from the public and routing relays/servers.
2024-03-28 18:23:30 -04:00
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.
```js
{
"id": "< id > ",
"pubkey": "< random-pubkey > ",
"created_at": randomTimeUpTo2DaysInThePast()
"kind": 1059,
"tags": [
2024-03-28 18:36:10 -04:00
["token", "< destination ' s push notification token > "],
2024-03-28 18:23:30 -04:00
],
"content": nip44Encrypt(notificationEvent, pubkeyB, privkeyRandom)
"sig": "< random , one-time-use pubkey signature > "
}
```
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
---
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
# A Walkthrough Example
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
Let's send a private `kind 1` note between two parties asking "Are you going to the party tonight?"
2023-08-11 11:34:56 -04:00
2024-03-28 18:23:30 -04:00
- Sender private key: `0beebd062ec8735f4243466049d7747ef5d6594ee838de147f8aab842b15e273`
2023-08-11 11:34:56 -04:00
- Recipient private key: `e108399bd8424357a710b606ae0c13166d853d327e47a6e5e038197346bdbf45`
- Ephemeral wrapper key: `4f02eac59266002db5801adc5270700ca69d5b8f761d8732fab2fbf233c90cbd`
2024-03-28 18:23:30 -04:00
## 1. Create a rumor
2024-01-09 16:39:58 -05:00
2024-03-28 18:23:30 -04:00
Create a `kind 1` event with the message, the receivers, and any other tags you want.
2023-08-11 11:34:56 -04:00
Do not sign the event.
```json
{
2024-03-28 18:23:30 -04:00
"id": "9dd003c6d3b73b74a85a9ab099469ce251653a7af76f523671ab828acd2a0ef9",
"pubkey": "611df01bfcf85c26ae65453b772d8f1dfd25c264621c0277e1fc1518686faef9",
2023-08-11 11:34:56 -04:00
"created_at": 1691518405,
"kind": 1,
2024-03-28 18:23:30 -04:00
"tags": [],
"content": "Are you going to the party tonight?",
"sig": ""
2023-08-11 11:34:56 -04:00
}
```
## 2. Seal the rumor
2024-03-28 18:23:30 -04:00
Encrypt the JSON-encoded `rumor` with a conversation key derived using the sender's private key and the recipient's public key. Place the result in the `.content` field of a `kind 13` `seal` event. Sign it with the sender's key.
2023-08-11 11:34:56 -04:00
```json
{
2024-03-28 18:23:30 -04:00
"id": "28a87d7c074d94a58e9e89bb3e9e4e813e2189f285d797b1c56069d36f59eaa7",
2023-08-11 11:34:56 -04:00
"pubkey": "611df01bfcf85c26ae65453b772d8f1dfd25c264621c0277e1fc1518686faef9",
2024-03-28 18:23:30 -04:00
"created_at": 1703015180,
"kind": 13,
2023-08-11 11:34:56 -04:00
"tags": [],
2024-03-28 18:23:30 -04:00
"content": "AqBCdwoS7/tPK+QGkPCadJTn8FxGkd24iApo3BR9/M0uw6n4RFAFSPAKKMgkzVMoRyR3ZS/aqATDFvoZJOkE9cPG/TAzmyZvr/WUIS8kLmuI1dCA+itFF6+ULZqbkWS0YcVU0j6UDvMBvVlGTzHz+UHzWYJLUq2LnlynJtFap5k8560+tBGtxi9Gx2NIycKgbOUv0gEqhfVzAwvg1IhTltfSwOeZXvDvd40rozONRxwq8hjKy+4DbfrO0iRtlT7G/eVEO9aJJnqagomFSkqCscttf/o6VeT2+A9JhcSxLmjcKFG3FEK3Try/WkarJa1jM3lMRQqVOZrzHAaLFW/5sXano6DqqC5ERD6CcVVsrny0tYN4iHHB8BHJ9zvjff0NjLGG/v5Wsy31+BwZA8cUlfAZ0f5EYRo9/vKSd8TV0wRb9DQ=",
2023-08-11 11:34:56 -04:00
"sig": "02fc3facf6621196c32912b1ef53bac8f8bfe9db51c0e7102c073103586b0d29c3f39bdaa1e62856c20e90b6c7cc5dc34ca8bb6a528872cf6e65e6284519ad73"
}
```
## 3. Wrap the seal
2024-03-28 18:23:30 -04:00
Encrypt the JSON-encoded `kind 13` event with your ephemeral, single-use random key. Place the result in the `content` field of a `kind 1059` . Add a single `p` tag containing the recipient's public key. Sign the `gift wrap` using the random key generated in the previous step.
2023-08-11 11:34:56 -04:00
```json
{
"id": "5c005f3ccf01950aa8d131203248544fb1e41a0d698e846bd419cec3890903ac",
2024-03-28 18:23:30 -04:00
"pubkey": "18b1a75918f1f2c90c23da616bce317d36e348bcf5f7ba55e75949319210c87c",
"created_at": 1703021488,
"kind": 1059,
2023-08-11 11:34:56 -04:00
"tags": [["p", "166bf3765ebd1fc55decfe395beff2ea3b2a4e0a8946e7eb578512b555737c99"]],
2024-03-28 18:23:30 -04:00
"content": "AhC3Qj/QsKJFWuf6xroiYip+2yK95qPwJjVvFujhzSguJWb/6TlPpBW0CGFwfufCs2Zyb0JeuLmZhNlnqecAAalC4ZCugB+I9ViA5pxLyFfQjs1lcE6KdX3euCHBLAnE9GL/+IzdV9vZnfJH6atVjvBkNPNzxU+OLCHO/DAPmzmMVx0SR63frRTCz6Cuth40D+VzluKu1/Fg2Q1LSst65DE7o2efTtZ4Z9j15rQAOZfE9jwMCQZt27rBBK3yVwqVEriFpg2mHXc1DDwHhDADO8eiyOTWF1ghDds/DxhMcjkIi/o+FS3gG1dG7gJHu3KkGK5UXpmgyFKt+421m5o++RMD/BylS3iazS1S93IzTLeGfMCk+7IKxuSCO06k1+DaasJJe8RE4/rmismUvwrHu/HDutZWkvOAhd4z4khZo7bJLtiCzZCZ74lZcjOB4CYtuAX2ZGpc4I1iOKkvwTuQy9BWYpkzGg3ZoSWRD6ty7U+KN+fTTmIS4CelhBTT15QVqD02JxfLF7nA6sg3UlYgtiGw61oH68lSbx16P3vwSeQQpEB5JbhofW7t9TLZIbIW/ODnI4hpwj8didtk7IMBI3Ra3uUP7ya6vptkd9TwQkd/7cOFaSJmU+BIsLpOXbirJACMn+URoDXhuEtiO6xirNtrPN8jYqpwvMUm5lMMVzGT3kMMVNBqgbj8Ln8VmqouK0DR+gRyNb8fHT0BFPwsHxDskFk5yhe5c/2VUUoKCGe0kfCcX/EsHbJLUUtlHXmTqaOJpmQnW1tZ/siPwKRl6oEsIJWTUYxPQmrM2fUpYZCuAo/29lTLHiHMlTbarFOd6J/ybIbICy2gRRH/LFSryty3Cnf6aae+A9uizFBUdCwTwffc3vCBae802+R92OL78bbqHKPbSZOXNC+6ybqziezwG+OPWHx1Qk39RYaF0aFsM4uZWrFic97WwVrH5i+/Nsf/OtwWiuH0gV/SqvN1hnkxCTF/+XNn/laWKmS3e7wFzBsG8+qwqwmO9aVbDVMhOmeUXRMkxcj4QreQkHxLkCx97euZpC7xhvYnCHarHTDeD6nVK+xzbPNtzeGzNpYoiMqxZ9bBJwMaHnEoI944Vxoodf51cMIIwpTmmRvAzI1QgrfnOLOUS7uUjQ/IZ1Qa3lY08Nqm9MAGxZ2Ou6R0/Z5z30ha/Q71q6meAs3uHQcpSuRaQeV29IASmye2A2Nif+lmbhV7w8hjFYoaLCRsdchiVyNjOEM4VmxUhX4VEvw6KoCAZ/XvO2eBF/SyNU3Of4SO",
"sig": "35fabdae4634eb630880a1896a886e40fd6ea8a60958e30b89b33a93e6235df750097b04f9e13053764251b8bc5dd7e8e0794a3426a90b6bcc7e5ff660f54259"
2023-08-11 11:34:56 -04:00
}
```
## 4. Broadcast Selectively
Broadcast the `kind 1059` event to the recipient's relays only. Delete all the other events.
# Code Samples
## JavaScript
```javascript
import {bytesToHex} from "@noble/hashes/utils"
import type {EventTemplate, UnsignedEvent, Event} from "nostr-tools"
import {getPublicKey, getEventHash, nip19, nip44, finalizeEvent, generateSecretKey} from "nostr-tools"
type Rumor = UnsignedEvent & {id: string}
const TWO_DAYS = 2 * 24 * 60 * 60
const now = () => Math.round(Date.now() / 1000)
const randomNow = () => Math.round(now() - (Math.random() * TWO_DAYS))
const nip44ConversationKey = (privateKey: Uint8Array, publicKey: string) =>
nip44.v2.utils.getConversationKey(bytesToHex(privateKey), publicKey)
const nip44Encrypt = (data: EventTemplate, privateKey: Uint8Array, publicKey: string) =>
nip44.v2.encrypt(JSON.stringify(data), nip44ConversationKey(privateKey, publicKey))
const nip44Decrypt = (data: Event, privateKey: Uint8Array) =>
JSON.parse(nip44.v2.decrypt(data.content, nip44ConversationKey(privateKey, data.pubkey)))
const createRumor = (event: Partial< UnsignedEvent > , privateKey: Uint8Array) => {
const rumor = {
created_at: now(),
content: "",
tags: [],
...event,
pubkey: getPublicKey(privateKey),
} as any
rumor.id = getEventHash(rumor)
return rumor as Rumor
}
const createSeal = (rumor: Rumor, privateKey: Uint8Array, recipientPublicKey: string) => {
return finalizeEvent(
{
kind: 13,
content: nip44Encrypt(rumor, privateKey, recipientPublicKey),
created_at: randomNow(),
tags: [],
},
privateKey
) as Event
}
const createWrap = (event: Event, recipientPublicKey: string) => {
const randomKey = generateSecretKey()
return finalizeEvent(
{
kind: 1059,
content: nip44Encrypt(event, randomKey, recipientPublicKey),
created_at: randomNow(),
tags: [["p", recipientPublicKey]],
},
randomKey
) as Event
}
// Test case using the above example
const senderPrivateKey = nip19.decode(`nsec1p0ht6p3wepe47sjrgesyn4m50m6avk2waqudu9rl324cg2c4ufesyp6rdg`).data
const recipientPrivateKey = nip19.decode(`nsec1uyyrnx7cgfp40fcskcr2urqnzekc20fj0er6de0q8qvhx34ahazsvs9p36`).data
const recipientPublicKey = getPublicKey(recipientPrivateKey)
const rumor = createRumor(
{
kind: 1,
content: "Are you going to the party tonight?",
},
senderPrivateKey
)
const seal = createSeal(rumor, senderPrivateKey, recipientPublicKey)
const wrap = createWrap(seal, recipientPublicKey)
2024-01-09 16:39:58 -05:00
// Recipient unwraps with his/her private key.
2023-08-11 11:34:56 -04:00
const unwrappedSeal = nip44Decrypt(wrap, recipientPrivateKey)
const unsealedRumor = nip44Decrypt(unwrappedSeal, recipientPrivateKey)
```