X.KOJIRA.IO
Timeline

SIGit

sigit.io
npub1d0csynrrxcynkcedktdzrdj6gnras2psg48mf46kxjazs8skrjgq9uzhlq
Secure & Private Agreements

An open-source, self-hostable solution for secure document signing and verification.
SIGit
sigit.io ·
Last month we scored a podium finish at the Baltic Honeybadger 2025 Hackathon for nprofile1qqsxhugzf…, sponsored by nprofile1qqs8p3ywf… and with funds distributed through nprofile1qqstdhxam…

Why do you need SIGit? It's simple... legacy providers like docusign store all your files centrally, unencrypted and at risk of being hacked. And to top it off they are advertising the use of AI to scan documents. All this leaves users of centralised contract signing platforms at risk of nefarious actions, of privacy being eroded and of a hostile change in regulatory or government policy leaving you unable to protect your business relationships.

Try us out today at sigit.io

And a huge congrats to the other winners! BlindBit Suite, Receipt Cash and Git Futz

nprofile1qqszw0ncs…

nprofile1qqsy3ka4u…

nprofile1qqszwjruj…
SIGit
sigit.io ·
All counterparty signatures, plus the creation of the SIGit itself, are timestamped (OTS) on the Bitcoin blockchain

Irrefutable proof that an agreement was signed on a particular date

https://sigit.io
SIGit
sigit.io ·
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.

https://git.nostrdev.com/sigit/sigit.io/releases/tag/v2.0.6