add profile event for trusted oracle declarations

This commit is contained in:
conduition 2025-01-13 20:12:10 +00:00
parent c78872eec1
commit 16b2142fe7
No known key found for this signature in database
GPG Key ID: 78296CED84F6B3C5

16
88.md
View File

@ -74,3 +74,19 @@ The `content` field must be the base64-encoding of a binary-serialized [`oracle_
Note that the `e` tag is the _Nostr event identifier_ for the `kind:88` announcement event, which is distinct from the identifier embedded [in the announcement](https://github.com/discreetlogcontracts/dlcspecs/blob/master/Messaging.md#oracle_event) or [in the attestation itself](https://github.com/discreetlogcontracts/dlcspecs/blob/master/Messaging.md#oracle_attestation). The `e` tag is intended to be used to look up the corresponding announcement event.
Upon receiving an attestation, clients _should_ validate that the `event_id` field inside the `oracle_announcement` object matches the `event_id` field in the `oracle_attestation` object.
### `kind:10088`
Kind `10088` lists a user's trusted oracles, for the purpose of 3rd party protocols negotating DLCs or DLC-adjacent conditional payment contracts with the user. A kind `10088` event contains one or more `s` tags with a oracle's Nostr pubkey, and one or more relays where that oracle's announcement events (`kind:88`) may be found.
```jsonc
{
"kind": 10088,
"tags": [
["s", "4fd5e210530e4f6b2cb083795834bfe5108324f1ed9f00ab73b9e8fcfe5f12fe", "wss://bitagent.prices"],
// ...
],
//...
}
```