## BudaBit Demo Day application ### Title: SIGit CLI Pitch: We are rebuilding SIGit to use state machines, bringing the core logic into a standalone library, such that it can easily be used by other projects and clients. The first client to be released with the new library will be the SIGit CLI, and will be debuted at the Budabit Club event.
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!
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
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 😎
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 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