The next development chapter for SIGit will be the creation of an NPM module to allow others to build SIGits into their tools and applications As part of this we will be ripping out NDK and replacing with AppleSauce We are also planning to encapsulate all the logic into State Machines - this will significantly improve stability, usability, and maintainability. We'd like to thank all of the donors who have supported us so far!

Last month we scored a podium finish at the Baltic Honeybadger 2025 Hackathon for @SIGit, sponsored by @Angor and with funds distributed through @Geyser 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 @Hodl Hodl @Freedom Tech Co. @Nostr Dev Team

Did you know that almost every commercial document signing solution makes your agreement available to third parties? With records in a database that can be easily modified? With SIGit, your documents are encrypted in the browser, and are only accessible to named counterparties. We use Blossom for data storage, Nostr for secure identity and metadata signing, and OTS for timestamping on Bitcoin. SIGit is available now, and we'd love your feedback!

SIGit

On-boarding to @Angor today, to which we will receive our prize from a podium hackathon finish at #BH2025 Love the fact that a project is created as part of an OP_RETURN code in an actual bitcoin UTXO The prize wil be released to us in tranches, if we don't claim, it's time locked and returnable to the investor Our access key is literally our 12 words Smooth!!! https://hub.angor.io/project/angor1q4heck5tf6svq7x8jp5twak329xtv9805xppvq5

We are participating in the HoneyBadger Hackathon, sponsored by Angor! Below is our first ever demo video #BH2025

PeerTube

SIGit Demo

A simple SIGit with two counterparties

v2.0.7 is now available - this fixes some issues using the offline flow, and makes it possible to verify an unencrypted SIGit from the homepage, without signing in Nostr works great without internet, or relays 😎

Gitea

sigit.io

Secure & Sovereign agreements

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

SIGit

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.

Gitea

sigit.io

Secure & Sovereign agreements

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

Gitea

sigit.io

Secure & Sovereign agreements

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

v2.03 now released with a bunch of improvements to the OTS generation process Timestamps are generated for the create event and each sign event Each timestamp has 3 states - pending, upgraded, verified

SIGit

v2.02 is released - fixes an issue where the last remaining pdf in a draft sigit could not be deleted, and applies some client side logic to handle the case where relays sometimes do not send an EOSE message

SIGit

v02.01 now released - this disables the broadcast button when verifying unencrypted SIGits without signing in

Gitea

sigit.io

Secure & Sovereign agreements

We now have v2 of

SIGit

! It was a complete refactor and breaking change, so if you have sigits from the old version you will need to visit the archive version of the site (in top bar) We'd now like to invite some intrepid users to try the service whilst we smoothen out the rough edges You can send us feedback here on Nostr, or get in touch to join our power users community

Are you interested in helping us test SIGit? Get early acess to new features and help define the feature roadmap? We'd love to hear from / involve you.

Yes we've been quiet lately - with a big refactor in process And we just hit commit #1000 Watch this space

SIGit is a PRIVATE and SECURE document signing service. It uses Nostr and Blossom for comms and (encrypted) file storage The project has progressed at a slow pace due to a shortage of funding, however we do push updates almost every week. You can try it out right now and let us know your feedback:

SIGit

SIGit was officially (BETA) released today at the Nostr Hack day in Berlin!

SIGit

Progress on SIGit continues - we recently dropped the following features: - History (app data, stored on blossom) - Notifications (sent as gift-wrapped DMs) - Encrypted decryption keys - no more copy paste for offline flow We still need to fix the design, the PDF annotations, and some other stability issues - at which point we'll have the MVP

Gitea

store-sigits and update working flow

### Updated create flow The uploaded files are zipped, and this files.zip file is then encrypted and uploaded to Blossom. The Creator prepares a...