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

Merge pull request #1 from leandro21b/leandro21b-patch-1

Browse Source 
NIP-60 - Secure file load from URL
This commit is contained in:
LeandroBitcoiner21 2023-03-21 15:43:38 -03:00 committed by GitHub
commit bd09454f51
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 39 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
60.md Normal file
View File

@ -0,0 +1,39 @@
NIP-60
======
Secure file load from URL
-------------------------
`draft` `optional` `author:leandro21b`
## Description:
A mechanism that allows the client to verify the hash of a file such as image, video, source codes, and others And ensure that the server that hosted the file has not changed any data, in addition that same file can be stored on several servers at the same time, so if one server goes down the file can still be loaded via other servers.
When a user is going to publish a file, the client takes the file type ex: (img), the format ex: (png), and generates a SHA256 hash, then the client sends the file to the servers that the user chooses, then the client takes the urls that carry the file, unites all this data and declares it in the field (tags), several different files can be declared in a post as in the example below:
## Example:
```json
{
"id": <id>,
"pubkey": <pubkey>,
"created_at": <created_at>,
"kind": 1,
"tags": [
["img", "png", <ImgFileSHA256>, <ImgURL1>, <ImgURL2>],
["vid", "mp4", <VidFileSHA256>, <VidURL1>, <VidURL2>],
["aud", "mp3", <AudFileSHA256>, <AudURL1>, <AudURL2>],
["code", "py", <CodeFileSHA256>, <CodeURL1>, <CodeURL2>],
["compressedfile", "zip", <CompFileSHA256>, <CompFileURL1>, <CompFileURL2>]
],
"content": <content>,
"sig": <sig>
}
```
## Hash Check:
Hash checking will be performed according to the setting that a user programs the client to do based on its trust in the server hosting the file or the user who published a post with that file, if the client attempts to hash verify everyone files are being loaded, the client can be very slow depending on the device and the size of the files, so the user must choose when the client will check the hash.
For this to work, the servers that will host the files cannot compress it, otherwise there will be an error in the hash check, if a file has to be compressed, this must be done on the user's device which is where the original hash will be generated.