SIGit v2.0.6 is now released! A SIGit is composed of multiple regular files (e.g. original files, template.json), unpublished nostr events (e.g. signed create and sign events) and published nostr events (e.g. notification gift wraps, app data). For performance and reliability, all these files are zipped, encrypted, and loaded to blossom. For even better performance, to avoid downloading the zip and fetching / processing nostr events each time - the underlying files are also cached in the local browser file cache, the IndexedDB - files repository. Each time SIGit needs one of these building blocks it first checks the local cache. On cache miss, we check the original decrypted source in cache. If we can't find that, then we download the zip from blossom and decrypt the contents. Finally, if the blossom zip is missing on the blossom server(s), we fetch the original app data (30078) event and re-process (and publish) all the source events again. In this release, we improved the stability of the above process.
SIGit v2.0.5 released - fixes an issue where SIGit data (30078) can get caught in a signing loop. Also renames some of the exported files to use bech 32 npubs instead of hex keys to make them easier to (manually) verify
v2.0.4 is now released - mostly minor refactoring, but we also made each sigit id partially visible so you can tell when signing 30078 requests, which sigit they relate to sigit ids are a hash of the create event id and the user npub, so it is not possible to correlate events as an outside observer