store-sigits and update working flow #116

s · 2024-07-05T08:39:37Z

s commented

2024-07-05 08:39:37 +00:00

Updated create flow

The uploaded files are zipped, and this files.zip file is then encrypted and uploaded to Blossom.

The Creator prepares an Agreement by creating and signing (but NOT publishing) a Kind 938 event. The content field contains an object with the following information:

title (string)
signers (array) - list of npubs which can sign the Agreement
viewers (array) - list of npubs which can view the Agreement
filehashes (array) - series of objects containing the file name and file hash
zipUrl (string) - the location of the encrypted zip file (blossom server)

Once the creator has signed, the meta.json file will contain the createObject (above) and a keys object that contains the decryption key for the zip file, NIP-44 encrypted to each counterparty.

This meta.json file is now sealed (using unsigned Kind 938 to differentiate from DMs and speed up decryptions) and gift wrapped (with some PoW) per NIP-59, for each recipient, and the gift wrap is broadcast to each recipients relays.

Storing App Data

App data (list of all sigits) is stored as an encrypted file on Blossom. The file also contains a list of 'processed' id's from Kind 1059 events (to avoid having to continually decrypt when logging in, as well as enabling notifications).

A Kind 30078 is also created, which contains a link to the blossom server, and an ephemeral key pair that can be used to sign the blossom requests.

NIP-78 (event kind 30078) requires a d-tag to provide some application context. To avoid revealing metadata, the d tag will be the sha256 hash of the string "938" plus the users npub.

### Updated create flow The uploaded files are zipped, and this files.zip file is then encrypted and uploaded to Blossom. The Creator prepares an Agreement by creating and signing (but NOT publishing) a Kind 938 event. The content field contains an object with the following information: * title (string) * signers (array) - list of npubs which can sign the Agreement * viewers (array) - list of npubs which can view the Agreement * filehashes (array) - series of objects containing the file name and file hash * zipUrl (string) - the location of the encrypted zip file (blossom server) Once the creator has signed, the meta.json file will contain the createObject (above) and a keys object that contains the decryption key for the zip file, NIP-44 encrypted to each counterparty. This meta.json file is now sealed (using unsigned Kind 938 to differentiate from DMs and speed up decryptions) and gift wrapped (with some PoW) per NIP-59, for each recipient, and the gift wrap is broadcast to each recipients relays. ### Storing App Data App data (list of all sigits) is stored as an encrypted file on Blossom. The file also contains a list of 'processed' id's from Kind 1059 events (to avoid having to continually decrypt when logging in, as well as enabling notifications). A Kind 30078 is also created, which contains a link to the blossom server, and an ephemeral key pair that can be used to sign the blossom requests. NIP-78 (event kind 30078) requires a d-tag to provide some application context. To avoid revealing metadata, the d tag will be the sha256 hash of the string "938" plus the users npub.

s added 4 commits 2024-07-05 08:39:37 +00:00

chore: npm audit fix b91abe1e68

chore: push unfinished changes 5850ef7dce

chore: quick fix 88bdce33c9

chore: update flow for storing sigits d4c50dabaf

s added 4 commits 2024-07-05 09:18:06 +00:00

chore: remove unused npm package uuid 08baf5dedd

fix: navigation to profile page from username component d5024745f1

chore: remove unused code from nostr controller f3b24dee65

chore remove unused code 412da32293

s added 1 commit 2024-07-05 09:19:42 +00:00

chore: quick fix 016ccea74f