Skip to content

Commit ceaf163

Browse files
benthecarmanbenthecarman
committed
NIP-88: Discreet Log Contracts over Nostr
1 parent c07f0ea commit ceaf163

File tree

1 file changed

+146
-0
lines changed

1 file changed

+146
-0
lines changed

‎88.md

+146
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,146 @@
1+
NIP-88
2+
======
3+
4+
Discreet Log Contracts over nostr
5+
-----------------
6+
7+
`draft` `optional`
8+
9+
This NIP describes a way to use Discreet Log Contracts (DLCs) over Nostr. This comes in four main
10+
components: `kind:8_888` for sending DLC messages between wallets. `kind:30088` for posting DLC offers to the global
11+
market. `kind:88` and `kind:89` for publishing DLC oracle announcements and attestations. And `kind:90` for a DLC
12+
"receipt" that can publish the result of a DLC for social interaction.
13+
14+
## DLC Messages
15+
16+
DLCs typically use [BOLT 8](https://github.com/lightning/bolts/blob/master/08-transport.md) for sending messages but
17+
this has various problems: it requires the ability to accept incoming connections and an always-on node. Nostr provides
18+
a unique opportunity to use a different transport layer for DLCs. This NIP proposes a new `kind:8_888` message that
19+
acts like a mailbox for DLC messages. The DLC messages are sent over nostr and available for the user the next time
20+
they open their wallet. This allows for a more mobile-friendly DLC experience.
21+
22+
### `kind:8_888`
23+
24+
Kind 8_888 is a simple message that contains a [NIP04](04.md) encrypted DLC message and it tagged with the recipient's
25+
public key with a `p` tag and if it is in reply to another event, that event should be tagged with an `e` tag.
26+
27+
A DLC wallet should only process messages that are tagged with their public key and that are in reply to a message they
28+
sent unless it is an offer. This is to prevent spam and to prevent a malicious actor from sending a message to a user
29+
that looks like it is from a different user.
30+
31+
```json
32+
{
33+
"kind": 8888,
34+
"content": "TJob1dQrf2ndsmdbeGU+05HT5GMnBSx3fx8QdDY/g3NvCa7klfzgaQCmRZuo1d3WQjHDOjzSY1+MgTK5WjewFFumCcOZniWtOMSga9tJk1ky00tLoUUzyLnb1v9x95h/iT/KpkICJyAwUZ+LoJBUzLrK52wNTMt8M5jSLvCkRx8C0BmEwA/00pjOp4eRndy19H4WUUehhjfV2/VV/k4hMAjJ7Bb5Hp9xdmzmCLX9+64+MyeIQQjQAHPj8dkSsRahP7KS3MgMpjaF8nL48Bg5suZMxJayXGVp3BLtgRZx5z5nOk9xyrYk+71e2tnP9IDvSMkiSe76BcMct+m7kGVrRcavDI4n62goNNh25IpghT+a1OjjkpXt9me5wmaL7fxffV1pchdm+A7KJKIUU3kLC7QbUifF22EucRA9xiEyxETusNludBXN24O3llTbOy4vYFsq35BeZl4v1Cse7n2htZicVkItMz3wjzj1q1I1VqbnorNXFgllkRZn4/YXfTG/RMnoK/bDogRapOV+XToZ+IvsN0BqwKSUDx+ydKpci6htDRF2WDRkU+VQMqwM0CoLzy2H6A2cqyMMMD9SLRRzBg==?iv=S3rFeFr1gsYqmQA7bNnNTQ==",
35+
"tags": [
36+
[
37+
"p",
38+
"04c915daefee38317fa734444acee390a8269fe5810b2241e5e6dd343dfbecc9"
39+
],
40+
[
41+
"e",
42+
"9ae37aa68f48645127299e9453eb5d908a0cbb6058ff340d528ed4d37c8994fb"
43+
]
44+
],
45+
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
46+
"created_at": 1679673265,
47+
"id": "30efed56a035b2549fcaeec0bf2c1595f9a9b3bb4b1a38abaf8ee9041c4b7d93",
48+
"sig": "f2cb581a84ed10e4dc84937bd98e27acac71ab057255f6aa8dfa561808c981fe8870f4a03c1e3666784d82a9c802d3704e174371aa13d63e2aeaf24ff5374d9d"
49+
}
50+
```
51+
52+
## DLC Offers
53+
54+
DLCs are done between two parties and Nostr provides a unique opportunity to create a global market for DLCs. This
55+
market can be constructed with a simple list of DLC offers that can be filtered by the user's wallet. The user can then
56+
select an offer and send a message to the offerer to begin the DLC process. `kind:30088` is an event that contains a DLC
57+
offer.
58+
59+
A parameterized replaceable event is used to allow the offerer to update the offer or remove it from the market. The `d`
60+
tag should be the Offer's id to allow replacement of the offer. If the user wishes to remove the offer from the market,
61+
they can replace the event with an expires tag that is in the past.
62+
63+
### `kind:30_088`
64+
65+
```jsonc
66+
{
67+
"kind": 30088,
68+
"content": "base64 contract details",
69+
"tags": [
70+
[
71+
"relays",
72+
"wss://nostr.mutinywallet.com",
73+
"wss://relay.damus.io"
74+
],
75+
[
76+
"expires",
77+
"1695327657"
78+
],
79+
[
80+
"d",
81+
"6423394a32f37a4f0590e74f9308f5aee06e59e14f50c4cd6d59365caed13cb7"
82+
],
83+
],
84+
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
85+
"created_at": 1679673265,
86+
"id": "30efed56a035b2549fcaeec0bf2c1595f9a9b3bb4b1a38abaf8ee9041c4b7d93",
87+
"sig": "f2cb581a84ed10e4dc84937bd98e27acac71ab057255f6aa8dfa561808c981fe8870f4a03c1e3666784d82a9c802d3704e174371aa13d63e2aeaf24ff5374d9d"
88+
}
89+
```
90+
91+
## DLC Oracle Gossip
92+
93+
DLCs require an oracle to attest to the outcome of real world events. This is done by the oracle signing a message
94+
containing the outcome of the event. Before they attest to the outcome, they must create an announcement where they
95+
publish the intent to sign the future event. This announcement is then used by the DLC participants to create the
96+
contract. Here we define two events, `kind:88` and `kind:89` that are used to publish the oracle's announcement and
97+
attestations respectively.
98+
99+
### `kind:88`
100+
101+
```jsonc
102+
{
103+
"kind": 88,
104+
"content": "base64 oracle annoucement",
105+
"tags": [
106+
[
107+
"relays", // the relays the oracle will publish attestations to
108+
"wss://nostr.mutinywallet.com",
109+
"wss://relay.damus.io"
110+
],
111+
],
112+
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
113+
"created_at": 1679673265,
114+
"id": "30efed56a035b2549fcaeec0bf2c1595f9a9b3bb4b1a38abaf8ee9041c4b7d93",
115+
"sig": "f2cb581a84ed10e4dc84937bd98e27acac71ab057255f6aa8dfa561808c981fe8870f4a03c1e3666784d82a9c802d3704e174371aa13d63e2aeaf24ff5374d9d"
116+
}
117+
```
118+
119+
### `kind:89`
120+
121+
```jsonc
122+
{
123+
"kind": 89,
124+
"content": "base64 oracle attestation",
125+
"tags": [
126+
[
127+
"e", // the event id of the announcement
128+
"30efed56a035b2549fcaeec0bf2c1595f9a9b3bb4b1a38abaf8ee9041c4b7d93",
129+
],
130+
],
131+
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
132+
"created_at": 1679673265,
133+
"id": "30efed56a035b2549fcaeec0bf2c1595f9a9b3bb4b1a38abaf8ee9041c4b7d93",
134+
"sig": "f2cb581a84ed10e4dc84937bd98e27acac71ab057255f6aa8dfa561808c981fe8870f4a03c1e3666784d82a9c802d3704e174371aa13d63e2aeaf24ff5374d9d"
135+
}
136+
```
137+
138+
## DLC Receipts
139+
140+
DLCs can be fun, social events. This NIP proposes a `kind:90` event that can be used to publish the result of a DLC
141+
contract. This event can be used to show off the result of a DLC to the user's followers, similar [Zaps](57.md) but for
142+
DLC bets.
143+
144+
### `kind:90`
145+
146+
todo I still need to think about this one

0 commit comments

Comments
 (0)