fix: sign flow
All checks were successful
Release to Production / build_and_release (push) Successful in 29s

This commit is contained in:
_ 2025-03-07 15:17:11 +00:00
parent 5adfd853e7
commit ce92669bc3
3 changed files with 37 additions and 8 deletions

View File

@ -1,3 +1,5 @@
* [Create Flow](/create.md)
* [Sign Flow](/sign.md)
* [Email Flow](/emailflow.md)
* [Offline Flow](/offline.md)
* [Technical Notes](/technical.md)

View File

@ -21,10 +21,6 @@ This event is designed to provide clarity (when signing) about the agreement bei
}
```
## Metadata JSON
This contains the marks that should be applied to the files
## Encrypted Zip File
This file contains the following:

39
sign.md
View File

@ -13,12 +13,43 @@ This event is designed to provide clarity (when signing) about the agreement bei
"created_at": 1716564780,
"id": "...",
"sig": "...",
"pubkey": "pubkey of CREATOR",
"pubkey": "pubkey of SIGNER",
"tags":[
["signers","npub1d0csynr..","npub1nqulz.."],
["viewers","npub1viewer1"], // optional tag, only if there are viewers
["files","hash1:name1.csv","hash2:name2.pdf"], // extension determines the file type. Order determines index.
["prevsig","xxx"], // sig of kind 160300 (create) event
["meta","hash1"] // the hash of the meta.json file
]
}
```
## Encrypted Zip File
This file contains the following:
- "marked" folder (offline only) - containing marked pdfs
- "files" folder (offline only) - containing original pdfs
- "events" folder:
* sign Event (1603)
* create event (160300), for verification
* OTS request event
* OTS response event(s)
- meta.json file - contains the marks information
## Keys
The keys.json looks like this:
```json
{
"kind": 160301,
"content": "",
"created_at": 1716564780,
"id": "...",
"sig": "",
"pubkey": "random pubkey",
"tags":[
["filehash",<optional list of blossom servers>],
["array of decryption keys", "encrypted to each recipient"]
]
}
```