nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-09 22:09:06 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

change to regular event

Browse Source
This commit is contained in:
frbittencourt 2023-03-17 13:41:46 +00:00 committed by fiatjaf_
parent 40fa44b0fc
commit bd32adfc2a
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
94.md
View File

@ -7,7 +7,7 @@ Also the goal is to create a base on the protocol for this bountsr "Filesharing
Nostr event
------------------
This NIP specifies the use of the `30063` event type (parameterized replaceable event), having in `content` a description of the file content, and a list of tags described below:
This NIP specifies the use of the `1063` event type (parameterized replaceable event), having in `content` a description of the file content, and a list of tags described below:
* `url` the url to download the file
* `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
@ -18,12 +18,12 @@ This NIP specifies the use of the `30063` event type (parameterized replaceable
"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": 30063,
"kind": 1063,
"tags": [
["url",<string with URL of file>],
["decrypt",<algorithm>,<Decryption Params>],
["type", "image/webp"],
["hash", "LKN]Rv%2Tw=w]~RBVZRi};RPxuwH", "blurhash"]
["type", <MIME type>],
["hash", "LKN]Rv%2Tw=w]~RBVZRi};RPxuwH", <"blurhash" or "sha256">]
],
"content": <description>,
"sig": <64-bytes hex of the signature of the sha256 hash of the serialized event data, which is the same as the "id" field>