Add comments / make infohash indexed like NIP94

1 files changed, 13 insertions, 4 deletions

diff --git a/35.md b/35.md
index 33ed2be..4e80e3e 100644
--- a/35.md
+++ b/35.md
@@ -6,13 +6,14 @@ Torrents
 
 `draft` `optional`
 
-This NIP defined a new `kind 2003` which is Torrent. 
+This NIP defined a new `kind 2003` which is a Torrent. 
 
 `kind 2003` is a simple torrent index where there is enough information to search for content and construct the magnet link. No torrent files exist on nostr.
 
 ## Tags
-- `btih`: V1 BitTorrent Info Hash, as seen in the [magnet link](https://www.bittorrent.org/beps/bep_0053.html) `magnet:?xt=urn:btih:HASH`
+- `i`: V1 BitTorrent Info Hash, as seen in the [magnet link](https://www.bittorrent.org/beps/bep_0053.html) `magnet:?xt=urn:btih:HASH`
 - `file`: A file entry inside the torrent, including the full path ie. `info/example.txt`
+- `tracker`: (Optional) A tracker to use for this torrent
 
 In order to make torrents searchable by general category, you SHOULD include a few tags like `movie`, `tv`, `HD`, `UHD` etc.
 
@@ -36,15 +37,17 @@ A second level prefix should be included where the database supports multiple me
 
 In some cases the url mapping isnt direct, mapping the url in general is out of scope for this NIP, the section above is only a guide so that implementers have enough information to succsesfully map the url if they wish.
 
-```json
+```jsonc
 {
   "kind": 2003,
   "content": "<long-description-pre-formatted>",
   "tags": [
     ["title", "<torrent-title>"],
-    ["btih", "<bittorrent-info-hash>"],
+    ["i", "<bittorrent-info-hash>"],
     ["file", "<file-name>", "<file-size-in-bytes>"],
     ["file", "<file-name>", "<file-size-in-bytes>"],
+    ["tracker", "udp://mytacker.com:1337"],
+    ["tracker", "http://1337-tracker.net/announce"],
     ["t", "tcat:video,movie,4k"],
     ["t", "newznab:2045"],
     ["t", "imdb:tt15239678"],
@@ -56,6 +59,12 @@ In some cases the url mapping isnt direct, mapping the url in general is out of
 }
 ```
 
+## Torrent Comments
+
+A torrent comment is a `kind 2004` event which is used to reply to a torrent event.
+
+This event works exactly like a `kind 1` and should follow `NIP-10` for tagging.
+
 ## Implementations
 1. [dtan.xyz](https://git.v0l.io/Kieran/dtan)
 2. [nostrudel.ninja](https://github.com/hzrd149/nostrudel/tree/next/src/views/torrents)
\ No newline at end of file