diff --git a/95.md b/95.md
index 8ff6fb74..6b240591 100644
--- a/95.md
+++ b/95.md
@@ -8,8 +8,7 @@ The intention is to combine the ease of NOSTR, with many clients being developed
 
 Nostr event
 ------------------
-This NIP specifies the use of the `30064` event type (parameterized replaceable event), having in `content` the binary data that you want to be stored in Base64 format.
-* `d` containing the name of the shared file to allow it to be overwritten in the future.
+This NIP specifies the use of the `1064` event type (parameterized replaceable event), having in `content` the binary data that you want to be stored in Base64 format.
 * `type` a string indicating the data type of the file. The MIME types format must be used (https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types)
 * `decrypt` (optional) If the file is encrypted, you must indicate in the first value the algorithm used to encrypt the file and in the second value the parameters that allow the decryption of the file
 
@@ -22,12 +21,10 @@ The `NIP-94` can be used to broadcast the ID of that event, with the ` and ` tag
   "id": <32-bytes lowercase hex-encoded sha256 of the the serialized event data>,
   "pubkey": <32-bytes lowercase hex-encoded public key of the event creator>,
   "created_at": <unix timestamp in seconds>,
-  "kind": 30064,
+  "kind": 1064,
   "tags": [
-    ["d", <string with name of file>],
     ["decrypt",<algorithm>,<Decryption Params>],
     ["p", <32-bytes hex of a pubkey>, <recommended relay URL>],
-    ["hash",< SHA256 hexencoded string of the raw data>],
   ],
   "content": <string with base64 data>,
   "sig": <64-bytes hex of the signature of the sha256 hash of the serialized event data, which is the same as the "id" field>